Testdino Mcp

@testdino-hq

Visit Server

11 days ago

TestDino MCP is a Model Context Protocol server that lets AI agents work directly with your Playwright test data, without leaving your editor or opening a browser. Once connected, your AI assistant can browse TestDino runs, inspect failing tests, and manage manual cases using plain language. Ask it to “show the last 5 failed runs in production,” “debug the checkout flow test,” or “list all critical manual test cases in project X,” and it will call the right tools behind the scenes. The server exposes 12 focused tools for CI runs, debugging, and manual test management. You can: Check account health and validate your PAT Filter runs by branch, commit, author, time window, or environment Drill into a single test case, including errors, logs, steps, screenshots, and traces Run debug_testcase to aggregate historical failures, classify patterns, and get AI‑ready prompts for root‑cause analysis and flakiness Create, update, and organize manual test cases and suites (status, severity, tags, layers, behaviors) TestDino MCP is MCP‑compatible and works with clients like Cursor and Claude Desktop. Configure it via mcp.json using either npx testdino-mcp (no install) or a global install (npm install -g testdino-mcp), and provide a TESTDINO_PAT from your TestDino account. Typical use cases include: speeding up Playwright failure triage from within your IDE, giving AI agents structured access to real test history, and keeping manual test management in sync with how your team actually debugs CI.

Overview Tools Comments

Overview

TestDino MCP

A Model Context Protocol (MCP) server that connects TestDino to AI agents. This server enables you to interact with your TestDino test data directly through natural language commands.

What is This?

This MCP server bridges the gap between your TestDino test management platform and AI agents. Instead of manually navigating the TestDino dashboard, you can ask your AI assistant to:

Check test run results
Analyze test failures
Get detailed test case information
Manage manual test cases and suites

All through simple conversational commands.

Features

🔍 Health Check: Verify your connection and validate your TestDino PAT. Get account information and list all available organizations and projects.

📊 Test Run Management: List and retrieve detailed information about your test runs with powerful filtering options (branch, time, author, commit, environment).

🧪 Test Case Analysis: Get comprehensive details about individual test cases, including errors, logs, execution steps, and artifacts (screenshots, videos, traces).

🐛 AI-Assisted Debugging: Debug test case failures with historical data aggregation, failure pattern analysis, and AI-friendly debugging prompts. Analyze patterns across multiple executions to identify root causes.

📝 Test Case Management: Create, update, list, and retrieve manual test cases with comprehensive filtering and organization (status, priority, severity, type, layer, behavior, tags).

📁 Test Suite Organization: Create and manage test suite hierarchies to organize your manual test cases.

🔌 MCP Compatible: Built on the Model Context Protocol standard. You can configure TestDino MCP with any MCP-compatible IDEs or AI agents (Cursor, Claude Desktop, etc.).

⚡ Easy Setup: Install and configure in minutes with npx. No installation required!

🔐 Secure: PAT stored securely in your local configuration. One PAT provides access to all organizations and projects you have permissions for.

Available Tools

The server provides 12 powerful tools:

Test Execution & Results:

1. health - Verify your connection and validate your PAT. Shows account information, available organizations, and projects with access permissions.

2. list_testruns - Browse test runs with powerful filters (branch, time interval, author, commit, environment). Supports pagination and batch operations.

3. get_run_details - Get comprehensive details about a specific test run including statistics, test suites, test cases, and metadata. Supports batch operations (comma-separated IDs, max 20).

**4. list_testcase **- List test cases with comprehensive filtering (by test run, status, browser, error category, branch, environment, commit, author, spec file, tags, runtime, artifacts, and more). Can filter by test run criteria or directly by test case properties.

5. get_testcase_details - Get detailed information about a specific test case including error messages, stack traces, test steps, console logs, and artifacts. Can identify by testcase_id alone or by testcase_name with testrun_id/counter.

6. debug_testcase - Debug a test case by aggregating historical failure data across multiple executions. Returns failure patterns, error categories, common error messages, error locations, browser-specific issues, and a pre-formatted debugging prompt for AI analysis. Perfect for root-cause analysis and identifying flaky test behavior.

Test Case Management:

7. list_manual_test_cases- Search and list manual test cases with comprehensive filtering (project, suite, status, priority, severity, type, layer, behavior, automation status, tags, flaky status).

8. get_manual_test_case - Get detailed information about a specific manual test case including steps, custom fields, preconditions, postconditions, and all metadata.

9. create_manual_test_case - Create new manual test cases with steps, preconditions, postconditions, and metadata (priority, severity, type, layer, behavior).

10. update_manual_test_case - Update existing manual test cases (title, descripton, steps, status, priority, severity, type, layer, behavior, preconditions, postconditions).

11. list_manual_test_suites - List test suite hierarchy to find suite IDs for organization. Supports filtering by parent suite.

12. create_manual_test_suite - Create new test suite folders to organize test cases. Supports nested suites by providing parentSuiteId.

Try in Playground

Server Config

{
  "mcpServers": {
    "TestDino": {
      "command": "npx",
      "args": [
        "-y",
        "testdino-mcp"
      ],
      "env": {
        "TESTDINO_PAT": "Your PAT here"
      }
    }
  }
}

Build with ShipAny.