Testdino MCP

What testdino-mcp MCP server does

testdino-mcp MCP server gives AI agents access to TestDino through the Model Context Protocol. It covers both automated test execution data and manual test management, so an assistant can inspect failures, retrieve execution evidence, create or update cases, and organize suites through natural-language requests.

The server can check TestDino connectivity, list organizations and projects available to the authenticated account, and browse test runs using filters such as branch, time range, author, commit, and environment. Detailed test-case responses can include errors, stack traces, steps, console logs, and stored artifacts such as screenshots, videos, and traces.

For debugging, it aggregates historical executions, compares retry attempts, identifies recurring error signatures, and helps distinguish deterministic failures from flaky or inconclusive results. It also supports fix verification against later runs and can group failures by likely root cause.

How it works

The server runs as an MCP process and communicates with an MCP client such as Cursor or Claude Desktop. The client starts it with npx -y @testdino/mcp, while authentication is supplied through the TESTDINO_PAT environment variable. After connection, the assistant can invoke the available tools and present their results in conversation.

A single personal access token provides access to the TestDino organizations and projects for which that token has permission. The server does not require raw test source files for its quality-audit workflow: it can retrieve a server-curated audit prompt and branch signals, then accept the completed report for storage in TestDino.

Setup and configuration

Create a TestDino personal access token under TestDino User Settings and add the server to the MCP client configuration. A typical stdio configuration uses:

{
  "mcpServers": {
    "TestDino": {
      "command": "npx",
      "args": ["-y", "@testdino/mcp"],
      "env": {
        "TESTDINO_PAT": "your-pat-here"
      }
    }
  }
}

For Cursor, the README places this configuration in ~/.cursor/mcp.json; Claude Desktop is also named as a supported integration. Restart the client after saving the configuration, then use the health check to confirm the token and view accessible organizations and projects.

Tools and capabilities

'testdino-mcp MCP server' exposes 43 tools covering the documented TestDino workflows. Capabilities include:

• Listing and inspecting automated test runs and individual test cases.
• Investigating failures with historical patterns, retry analysis, artifacts, and fix verification.
• Fetching and submitting test-quality audit reports.
• Searching, creating, and updating manual test cases.
• Listing and creating nested manual test suites.
• Creating and updating releases, with nesting up to three levels.
• Starting manual runs, assigning testers, and recording passed, failed, blocked, skipped, or retest verdicts.
• Creating exploratory sessions and tracking their state.
• Filing issues from failing tests or runs through connected Jira, Linear, Asana, or monday.com integrations.

Limitations and notes

Access depends on the permissions attached to the supplied TestDino PAT. Release hierarchies can be nested up to three levels. Artifact links returned during failure investigation are short-lived, so clients should use them while they are available. The server requires an MCP-compatible client and a Node.js environment capable of running the npm package through npx.