> ## 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.

# Remote MCP Server

> Bring TestDino into ChatGPT, Claude on the web, or other AI assistants. Query test runs and manual cases in chat.

export const HowToSchema = ({name, description, steps = []}) => {
  const schema = {
    "@context": "https://schema.org",
    "@type": "HowTo",
    name,
    ...description ? {
      description
    } : {},
    step: steps.map(({name: stepName, text}, i) => ({
      "@type": "HowToStep",
      position: i + 1,
      name: stepName,
      text
    }))
  };
  return <script type="application/ld+json" dangerouslySetInnerHTML={{
    __html: JSON.stringify(schema)
  }} />;
};

<HowToSchema
  name="Connect TestDino Remote MCP to your AI assistant"
  description="Add the TestDino Remote MCP server to Claude or ChatGPT and authorize access to your Playwright test data with a Personal Access Token."
  steps={[
{ name: "Add TestDino in your AI assistant", text: "In Claude, open Settings then Connectors and click Add custom connector. In ChatGPT, open Settings then Apps and click Create app. Set the name to TestDino and the server URL to https://mcp.testdino.com, then continue to the authorization page." },
{ name: "Confirm your TestDino account", text: "Sign in to TestDino if you aren't already. The dialog confirms which account will authorize the connection." },
{ name: "Choose how to connect", text: "Pick how the AI assistant gets a Personal Access Token: generate a new token (recommended) to select exactly which organizations, projects, and modules it can read, or use an existing td_pat_-prefixed PAT." },
{ name: "Authorize", text: "If generating a new token, select the access scope using the per-project Test Runs and Manual Tests toggles and click Authorize. If using an existing token, paste your td_pat_-prefixed PAT and click Connect." },
{ name: "Connector connected", text: "After TestDino redirects back, your AI assistant flips the connector to Connected. The TestDino tools are available in any new chat." },
]}
/>

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.

<Note>
  Prefer a local CLI install? See [Local MCP Server](/mcp/local) for Claude Code, Cursor, and Claude Desktop.
</Note>

## Quick Reference

| Topic                                           | Best for                                                     |
| :---------------------------------------------- | :----------------------------------------------------------- |
| [Prerequisites](#prerequisites)                 | What you need before starting                                |
| [Quick Start](#quick-start)                     | Add TestDino in Claude on the web or ChatGPT, then authorize |
| [Verify the connection](#verify-the-connection) | First `health` prompt and expected output                    |
| [Troubleshooting](#troubleshooting)             | OAuth, scope, and connector errors                           |
| [Tools Reference](/mcp/tools-reference)         | All 33 tools with parameters and video demos                 |

## Prerequisites

* Sign in to [TestDino](https://app.testdino.com)
* 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).

<Warning>
  **Warning**

  Treat 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.
</Warning>

## 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.

<Steps>
  <Step title="Add TestDino in your AI assistant">
    <Tabs>
      <Tab title="Claude on the web">
        Go to [claude.ai](https://claude.ai) and open **Settings → Connectors** (or **Profile → Connectors**, depending on plan).

        <img src="https://tdstorageus.blob.core.windows.net/public/docs/ai-and-automation/testdino-mcp/remote/claude-connector-settings.webp" alt="Claude.ai Settings Connectors page with the GitHub Integration entry, a Discovery toggle, and the Add custom connector button" className="max-w-2xl rounded-lg" />

        Click **Add custom connector** and fill in:

        * **Name**: `TestDino`
        * **Server URL**: `https://mcp.testdino.com`

        <img src="https://tdstorageus.blob.core.windows.net/public/docs/ai-and-automation/testdino-mcp/remote/claude-add-custom-connector.webp" alt="Claude.ai Add custom connector dialog with Name set to TestDino and Server URL set to https://mcp.testdino.com" className="max-w-2xl rounded-lg" />

        Click **Add**. Claude redirects you to TestDino's authorization page.
      </Tab>

      <Tab title="ChatGPT">
        In ChatGPT, open **Settings → Apps**. Scroll to **Advanced settings** and click **Create app**.

        <img src="https://tdstorageus.blob.core.windows.net/public/docs/ai-and-automation/testdino-mcp/remote/chatgpt-create-app.webp" alt="ChatGPT Settings Apps page listing connected apps with an Advanced settings row and a Create app button" className="max-w-2xl rounded-lg" />

        In the **New App** dialog, set:

        * **Name**: `TestDino`
        * **MCP Server URL**: `https://mcp.testdino.com`
        * **Authentication**: `OAuth` (default)

        Check **I understand and want to continue**, then click **Create**.

        <img src="https://tdstorageus.blob.core.windows.net/public/docs/ai-and-automation/testdino-mcp/remote/chatgpt-new-app.webp" alt="ChatGPT New App dialog with Name TestDino, MCP Server URL mcp.testdino.com, OAuth authentication, and the I understand checkbox" className="max-w-2xl rounded-lg" />

        ChatGPT redirects you to TestDino's authorization page.
      </Tab>
    </Tabs>
  </Step>

  <Step title="Confirm your TestDino account">
    Sign in to TestDino if you aren't already. The dialog confirms which account will authorize the connection.

    <img src="https://tdstorageus.blob.core.windows.net/public/docs/ai-and-automation/testdino-mcp/remote/oauth-sign-in.webp" alt="TestDino OAuth Step 1 of 3 Sign in to continue dialog with the active account selected and a Continue as button" className="max-w-2xl rounded-lg" />
  </Step>

  <Step title="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 `td_pat_`-prefixed PAT you already created in TestDino settings.

    <img src="https://tdstorageus.blob.core.windows.net/public/docs/ai-and-automation/testdino-mcp/remote/oauth-choose-pat-method.webp" alt="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" className="max-w-2xl rounded-lg" />
  </Step>

  <Step title="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**.

    <img src="https://tdstorageus.blob.core.windows.net/public/docs/ai-and-automation/testdino-mcp/remote/oauth-select-scope.webp" alt="TestDino OAuth Step 3 of 3 Select access scope picker showing organizations and projects with Test Runs and Manual Tests checkboxes and an Authorize button" className="max-w-2xl rounded-lg" />

    **If you chose Use an existing token**: paste your `td_pat_`-prefixed PAT. Click **Connect**.

    <img src="https://tdstorageus.blob.core.windows.net/public/docs/ai-and-automation/testdino-mcp/remote/oauth-paste-token.webp" alt="TestDino OAuth Step 3 of 3 Paste your token dialog with a Personal Access Token input prefilled with td_pat_ and a Connect button" className="max-w-2xl rounded-lg" />
  </Step>

  <Step title="Connector connected">
    After TestDino redirects back, your AI assistant flips the connector to **Connected**. The TestDino tools are available in any new chat.
  </Step>
</Steps>

## 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

<AccordionGroup>
  <Accordion title="Authorization header missing or Invalid User PAT">
    The PAT is missing, expired, or scoped to the wrong environment. Open **Profile → My Account → Personal Access Tokens** and confirm:

    * The token starts with `td_pat_`
    * 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.
  </Accordion>

  <Accordion title="Project access denied on a specific project">
    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.
  </Accordion>

  <Accordion title="Authorization failed during the connect flow">
    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.
  </Accordion>

  <Accordion title="Connector shows Connected but no tools appear in chat">
    * 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).
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup cols={2}>
  <Card title="Tools Reference" icon="wrench" href="/mcp/tools-reference">
    Full parameters, input schemas, and video demos for every tool
  </Card>

  <Card title="MCP Troubleshooting" icon="screwdriver-wrench" href="/mcp/troubleshooting">
    Error messages, fixes, and editor-specific solutions
  </Card>

  <Card title="AI Test Audit" icon="brain" href="/platform/playwright-ai-test-audit">
    Run an AI audit of a Playwright suite via `get_audit_report` and `submit_audit_report`
  </Card>

  <Card title="Playwright CLI" icon="terminal" href="/cli/testdino-playwright-nodejs">
    Stream Playwright runs to TestDino with `@testdino/playwright`
  </Card>
</CardGroup>