Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.testdino.com/llms.txt

Use this file to discover all available pages before exploring further.

What you’ll learn
  • How to install testdino-mcp locally via npx or a global install
  • How to generate a Personal Access Token and configure it per AI assistant
  • How to wire up Claude Code, Cursor, and Claude Desktop, then validate
Run the TestDino MCP server as a local process started by your AI assistant. It launches testdino-mcp over stdio.
Using Claude on the web? Skip the install and connect via the hosted MCP at mcp.testdino.com. See Remote MCP Server.

​
Prerequisites

  • Sign in to TestDino
  • Node.js installed (so npx works)
  • An MCP client: Claude Code, Cursor, or Claude Desktop

​
Quick Start

1

Install the MCP server

Try without installing:
npx -y testdino-mcp
Or install globally:
npm install -g testdino-mcp
NoteYour MCP client starts the server as a local process. npx is easiest for evaluation, and a global install is convenient for daily use.
2

Create a Personal Access Token

You will paste this token into your MCP client config as TESTDINO_PAT.
  1. Sign in to app.testdino.com
  2. Click your profile → User settings
User settings navigation showing profile menu and settings link
  1. Go to Personal access tokens → Generate new token
  2. Set a Token Name (e.g., mcp server) and Expiration (30 to 365 days)
Generate new token form with name and expiration fields
  1. Grant access to at least one project with Test runs, Manual tests, or both
  2. Click Generate token and copy it immediately
WarningThe token is shown once and cannot be retrieved later. Store it in a password manager. Never commit tokens to Git. Use separate tokens for separate contexts (local MCP, CI, scripts). Revoke tokens you no longer use.
3

Configure your MCP client

Pick your client and add the server entry.
Run in your terminal:
claude mcp add testdino -- npx -y testdino-mcp --pat your-token
No restart needed. Verify with:
claude mcp list
You should see testdino in the output.
4

Validate the connection

Ask your assistant:“Run health and confirm it can see my organisations and projects.”health verifies three things: the server is running, the token is loaded, and TestDino is reachable. See Troubleshooting if it fails.

​
Next Steps

Tools Reference

Full parameters, input schemas, and video demos for every tool

Troubleshooting

Error messages, fixes, and editor-specific solutions