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

# TestDino MCP Server

> Connect AI assistants to TestDino for querying test results and debugging failures via local CLI or remote URL.

export const VideoSchema = ({name, description, thumbnailUrl, uploadDate, duration, contentUrl, embedUrl}) => {
  const schema = {
    "@context": "https://schema.org",
    "@type": "VideoObject",
    name,
    description,
    thumbnailUrl,
    uploadDate,
    ...duration ? {
      duration
    } : {},
    ...contentUrl ? {
      contentUrl
    } : {},
    ...embedUrl ? {
      embedUrl
    } : {},
    publisher: {
      "@type": "Organization",
      name: "TestDino",
      logo: {
        "@type": "ImageObject",
        url: "https://docs.testdino.com/logo/light.svg"
      }
    }
  };
  return <script type="application/ld+json" dangerouslySetInnerHTML={{
    __html: JSON.stringify(schema)
  }} />;
};

<VideoSchema name="TestDino MCP Example" description="Example session using the TestDino MCP server with an AI assistant to debug Playwright test failures." thumbnailUrl="https://i.ytimg.com/vi/Qg4e0kEHVK0/maxresdefault.jpg" uploadDate="2025-12-16T00:00:00+00:00" contentUrl="https://www.youtube.com/watch?v=Qg4e0kEHVK0" embedUrl="https://www.youtube.com/embed/Qg4e0kEHVK0" />

<Callout icon="book-open" color="#3B82F6">
  **What you'll learn**

  * What the TestDino MCP server does and which tools it exposes
  * When to pick the Local vs Remote install path
  * What kinds of prompts work once connected
</Callout>

TestDino MCP Server connects AI assistants to your TestDino workspace to query test run data, artifacts, and manual test cases in natural language.

## Pick a connection method

TestDino offers two ways to connect. Pick whichever fits your client and workflow.

<CardGroup cols={2}>
  <Card title="Local MCP Server" icon="terminal" href="/mcp/local">
    For Claude Code, Cursor, or Claude Desktop. Install on your machine, paste a token, done.
  </Card>

  <Card title="Remote MCP Server" icon="cloud" href="/mcp/remote">
    For ChatGPT, Claude on the web, and other AI tools that support remote MCP. No install.
  </Card>
</CardGroup>

| Path                             | Best for                                       | Auth                           |
| :------------------------------- | :--------------------------------------------- | :----------------------------- |
| [Local MCP Server](/mcp/local)   | Claude Code, Cursor, Claude Desktop            | PAT in client config           |
| [Remote MCP Server](/mcp/remote) | ChatGPT, Claude on the web, other web AI tools | OAuth, scoped through TestDino |

## Example Prompts

<iframe className="w-full rounded-lg" style={{ height:"400px" }} src="https://www.youtube.com/embed/Qg4e0kEHVK0" title="TestDino MCP Example" allow="accelerometer;  clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowFullScreen />

### Test Run Analysis

| Prompt                                                         | What it does                                   |
| :------------------------------------------------------------- | :--------------------------------------------- |
| *Show test runs within the last hour in project xyz*           | Lists recent runs with status and metadata     |
| *Which are the most flaky test cases from the recent 10 runs?* | Ranks tests by flaky rate across runs          |
| *Show me all failed tests from the last run*                   | Filters test cases by failure status           |
| *List flaky tests on main from the last 7 days*                | Flaky tests filtered by branch and time window |
| *Show tests tagged @auth, @smoke that failed in production*    | Filters by tag, status, and environment        |
| *Debug the test case "visual.spec.js" on development*          | Root cause analysis with fix suggestions       |
| *Summarize which test broke in branch "main"*                  | Quick failure summary for a branch             |

### Manual Test Case Management

| Prompt                                                        | What it does                               |
| :------------------------------------------------------------ | :----------------------------------------- |
| *List all critical priority test cases in the checkout suite* | Filters manual cases by priority and suite |
| *Find manual test cases tagged @auth that are not automated*  | Filters by tag and automation status       |
| *Show me the steps for test case TC-456*                      | Full test case details including steps     |
| *Create a new test case for password reset in Authentication* | Creates a case in the specified suite      |
| *Update TC-789 to change its status to deprecated*            | Updates fields on an existing case         |
| *Create a test suite called "Payment Processing"*             | Creates a new suite for organizing cases   |

## 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="Troubleshooting" icon="screwdriver-wrench" href="/mcp/troubleshooting">
    Error messages, fixes, and editor-specific solutions
  </Card>
</CardGroup>