# Testdino MCP

> Testdino MCP is an MCP server for developer tools. MCP server that lets AI assistants query TestDino test runs, failures and manual test. It runs locally on your machine and is started by your AI client.

- **Kind:** MCP server
- **Platforms:** CLI, API, Web
- **Repository:** https://github.com/testdino-inc/testdino-mcp
- **MCP Registry name:** io.github.testdino-inc/testdino-mcp
- **Categories:** [developer tools](https://ai-powered.com/categories/developer-tools)
- **Listing updated:** 2026-11-18

## About

The README describes this server as a bridge between a TestDino account and an AI assistant, so test data can be read and changed through chat instead of the TestDino dashboard. Once connected, a client can list test runs, pull failure details for individual test cases, and compare retries to separate deterministic failures from flaky ones.

Beyond reading results, the server covers manual testing workflows: creating and updating manual test cases and suites, planning releases, starting manual runs, assigning testers to cases and recording pass, fail or blocked verdicts. It also exposes quarantine and re-run controls, which the README flags as build-affecting actions that clients should confirm first.

The package runs locally via npx with a personal access token set in the MCP client config. It is aimed at QA engineers and developers who already use TestDino and an MCP-compatible editor such as Cursor or Claude Desktop.

## Features

- **Test run inspection:** Lists test runs with filters for branch, time, author, commit and environment, and returns run details.
- **Failure debugging:** Aggregates historical failures, error clusters and retry data to find root causes and flaky behaviour.
- **Manual test case management:** Creates, updates and searches manual test cases and nested suites inside a TestDino project.
- **Release and run planning:** Creates releases, attaches manual runs to them and tracks rolled-up progress from chat.
- **Quarantine and re-run controls:** Quarantines tests, marks them critical and starts CI re-runs, with destructive actions flagged for confirmation.
- **Issue tracker linking:** Connects Jira, Linear, Asana or monday.com and files issues from failing tests or runs.

## Good for

- Asking an assistant which tests failed on a branch and why
- Triaging a failing CI run by grouping failures by error signature
- Assigning manual test cases to testers and recording verdicts inside a run
- Planning a release by creating milestones and attaching test runs to them
- Filing a tracked bug from a failing Playwright test

## Install

### Claude Code (Terminal)

```sh
claude mcp add testdino-mcp --env YOUR_API_KEY='<YOUR_API_KEY>' -- npx -y testdino-mcp
```

### Claude Desktop (claude_desktop_config.json)

```json
{
  "mcpServers": {
    "testdino-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "testdino-mcp"
      ],
      "env": {
        "YOUR_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "testdino-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "testdino-mcp"
      ],
      "env": {
        "YOUR_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "testdino-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "testdino-mcp"
      ],
      "env": {
        "YOUR_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "testdino-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "testdino-mcp"
      ],
      "env": {
        "YOUR_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "testdino-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "testdino-mcp"
      ],
      "env": {
        "YOUR_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}
```

## Tools

- `health`: Verify connection and validate PAT, showing account, organizations and projects.
- `list_testruns`: Browse test runs with filters for branch, time interval, author, commit and environment.
- `get_run_details`: Get statistics, test suites, test cases and metadata for a specific test run.
- `debug_testcase`: Aggregate historical failure data across executions to show failure patterns.
- `get_flake_verdict`: Compare a test's retry attempts within one run and classify the failure as deterministic, flaky or inconclusive.
- `create_manual_test_case`: Create manual test cases with steps, preconditions, postconditions and metadata.
- `update_run_test_case`: Set the assignee and result for one test case inside a manual run.
- `get_run_error_clusters`: Group a run's failing tests by error signature to triage at scale.
- `quarantine_tests`: Quarantine 1 to 100 tests until an end date, with a required reason.
- `rerun_test`: Start a re-run in CI in same-commit or latest mode, after confirmation.

## FAQ

### How is the server authenticated?

It uses a TestDino Personal Access Token set as TESTDINO_PAT in the MCP client configuration. The README says the token grants access to all organizations and projects the user has permissions for.

### Which clients are supported?

The README names Cursor and Claude Desktop and says the server uses the standard MCP protocol, so other MCP-compatible clients should work.

### How many tools does it provide?

The README states 58 tools across twelve domains.

### Does it require Node.js?

Yes, Node.js 20.0.0 or higher is listed as a requirement.

### How do I add Testdino MCP to Claude Code?

Run this command in your terminal: claude mcp add testdino-mcp --env YOUR_API_KEY='<YOUR_API_KEY>' -- npx -y testdino-mcp

### What are the best alternatives to Testdino MCP?

The closest alternatives to Testdino MCP are Testiny Test Management, Qase Test Management, Testing, Mobai MCP and simplify3x-connect.

## Where this comes from

- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.

## Alternatives

- [Testiny Test Management](https://ai-powered.com/mcp/testiny-test-management): Testiny Test Management is a paid MCP server for developer tools.
- [Qase Test Management](https://ai-powered.com/mcp/qase-test-management): Qase Test Management is a freemium MCP server for developer tools.
- [Testing](https://ai-powered.com/mcp/testing): Testing is an open-source MCP server for developer tools.
- [Mobai MCP](https://ai-powered.com/mcp/mobai-mcp): Mobai MCP is an open-source MCP server for developer tools.
- [simplify3x-connect](https://ai-powered.com/mcp/simplify3x-connect): simplify3x-connect is an open-source MCP server for developer tools.
- [Api Test MCP](https://ai-powered.com/mcp/api-test-mcp): Api Test MCP is an open-source MCP server for developer tools.
- [TestMu AI (formerly LambdaTest)](https://ai-powered.com/mcp/testmu-ai-formerly-lambdatest): TestMu AI (formerly LambdaTest) is a freemium MCP server for developer tools.
- [Testera](https://ai-powered.com/mcp/testera): Testera is a freemium MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/testdino-mcp
