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 add TestDino’s Remote MCP to your AI assistant
  • How to authorize access with a Personal Access Token
  • How to verify the connection and run your first prompts
TestDino’s Remote MCP server at https://mcp.testdino.com connects to ChatGPT, Claude on the web, and other AI assistants that support remote MCP.
Prefer a local CLI install? See Local MCP Server for Claude Code, Cursor, and Claude Desktop.

​
Quick Reference

TopicBest for
PrerequisitesWhat you need before starting
Quick StartAdd TestDino in Claude on the web or ChatGPT, then authorize
Verify the connectionFirst health prompt and expected output
TroubleshootingOAuth, scope, and connector errors
Tools ReferenceAll 12 tools with parameters and video demos

​
Prerequisites

  • Sign in to TestDino
  • An AI assistant that supports remote MCP (ChatGPT, Claude on the web, others)
  • A Personal Access Token from TestDino (generate one inline, or paste an existing token).
WarningTreat the PAT like a password. Anyone holding it can act on your behalf within its granted scope. Revoke and regenerate from Profile → My Account → Personal Access Tokens if it leaks.

​
Quick Start

Walkthrough below covers Claude on the web and ChatGPT. The TestDino OAuth flow at the end is the same for any AI assistant that supports remote MCP.
1

Add TestDino in your AI assistant

Go to claude.ai and open Settings → Connectors (or Profile → Connectors, depending on plan).Claude.ai Settings Connectors page with the GitHub Integration entry, a Discovery toggle, and the Add custom connector buttonClick Add custom connector and fill in:
  • Name: TestDino
  • Server URL: https://mcp.testdino.com
Claude.ai Add custom connector dialog with Name set to TestDino and Server URL set to https://mcp.testdino.comClick Add. Claude redirects you to TestDino’s authorization page.
2

Confirm your TestDino account

Sign in to TestDino if you aren’t already. The dialog confirms which account will authorize the connection.TestDino OAuth Step 1 of 3 Sign in to continue dialog with the active account selected and a Continue as button
3

Choose how to connect

Pick how your AI assistant gets a PAT.
  • Generate a new token (recommended): TestDino opens a scope picker where you select exactly which organizations, projects, and modules the AI assistant can read.
  • Use an existing token: paste a tpu_-prefixed PAT you already created in TestDino settings.
TestDino OAuth Step 2 of 3 How would you like to connect dialog with Generate a new token (recommended) and Use an existing token options
4

Authorize

Complete the path you picked.If you chose Generate a new token: select the access scope. Each project has separate Test Runs and Manual Tests toggles. Click Authorize.TestDino OAuth Step 3 of 3 Select access scope picker showing organizations and projects with Test Runs and Manual Tests checkboxes and an Authorize buttonIf you chose Use an existing token: paste your tpu_-prefixed PAT. Click Connect.TestDino OAuth Step 3 of 3 Paste your token dialog with a Personal Access Token input prefilled with tpu_ and a Connect button
5

Connector connected

After TestDino redirects back, your AI assistant flips the connector to Connected. The TestDino tools are available in any new chat.

​
Verify the connection

Open a new chat and ask:
Use the TestDino connector. Call health and tell me which projects I have access to.
Your AI assistant calls health and returns:
  • Your user identity
  • The connector’s granted scope
  • A tree of every organization and project the PAT can reach, each with a projectId
Save one projectId. Most prompts that follow need it. If health returns an empty list, the PAT has no project access. Adjust its scope in TestDino, then disconnect and reconnect the connector in your AI assistant to refresh granted access.

​
Troubleshooting

The PAT is missing, expired, or scoped to the wrong environment. Open Profile → My Account → Personal Access Tokens and confirm:
  • The token starts with tpu_
  • It hasn’t been revoked
  • It includes the projects and modules you’re trying to use
Generate a new token and reconnect the TestDino connector in your AI assistant if anything is off.
The PAT doesn’t include that project in its scope. Either:
  • Edit the PAT to add the project and module, or
  • Generate a new PAT with broader scope, then disconnect and reconnect the connector in your AI assistant so it picks up the new token.
Common causes:
  • You signed in to a different TestDino account than the one that owns the project you want to use.
  • Your browser blocked the authorization redirect, typically due to third-party cookies or strict tracking protection. Allow cookies for app.testdino.com and mcp.testdino.com and try again.
  • A stale popup window from a previous attempt. Close any open TestDino tabs, refresh your AI assistant, and start the connect flow again.
  • Start a new chat. Most clients attach connectors at chat creation, not retroactively.
  • Make sure the TestDino toggle is on for that chat (look for the icon next to the message input).

​
Next Steps

Tools Reference

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

MCP Troubleshooting

Error messages, fixes, and editor-specific solutions

AI Test Audit

Run an AI audit of a Playwright suite via test_audit

Playwright CLI

Stream Playwright runs to TestDino with @testdino/playwright