What MCP Enables
| Capability | Description |
|---|---|
| Run inspection | Query runs by branch, environment, time window, author, or commit |
| Failure analysis | Pull failure stats, error categories, and raw run JSON |
| Test case filtering | List failed, flaky, slow, or tagged test cases across runs |
| Debug context | Fetch logs, traces, screenshots, and video for any test case |
| Root cause analysis | Analyze historical execution data to identify failure patterns and causes |
| Fix recommendations | Get targeted fixes based on past failures and error patterns |
| Manual test management | Search, create, update, and organize manual test cases and suites |
How It Works
The MCP server runs as a local process started by your AI client. It authenticates with a Personal Access Token and communicates with TestDino APIs on behalf of your assistant.Example Prompts
Test run analysis
- Which are the most flaky test cases from the recent 10 test runs in TestDino?
- Show me all failed tests from the last run in TestDino.
- Debug the failing tests from the last run and provide fix suggestions in TestDino.
- List flaky tests on main from the last 7 days in TestDino.
- Can you explain the likely root cause of the test case “visual.spec.js” on the development branch in TestDino?
Manual test case management
- List all critical priority test cases in the checkout suite.
- Find manual test cases tagged with @auth that are not yet automated.
- Create a new test case for the password reset flow in the Authentication suite.
- What test suites exist in project X?
AI Debugging with debug_testcase
The debug_testcase tool aggregates historical execution data for a specific test case across multiple runs.
| Analysis | What it provides |
|---|---|
| Root cause | Analyzes past error messages, artifacts, stack traces, and error categories |
| Failure patterns | Identifies common error categories, messages, and failure locations |
| Fix recommendations | Suggests fixes based on historical analysis and pattern matching |
Available Tools
| Tool | Description |
|---|---|
health | Confirms server is running and token has access |
list_testruns | Lists test runs with filters (branch, environment, author, time) |
get_run_details | Returns full report for a run or batch of runs |
list_testcase | Lists test cases across runs with status and tag filters |
get_testcase_details | Retrieves full debug details for a specific test case |
debug_testcase | Root cause analysis with failure patterns and fix recommendations |
list_manual_test_cases | Searches manual test cases with filters |
get_manual_test_case | Retrieves a manual test case with steps and custom fields |
create_manual_test_case | Creates a manual test case in a suite |
update_manual_test_case | Updates fields on a manual test case |
list_manual_test_suites | Lists the suite hierarchy and suite IDs |
create_manual_test_suite | Creates a suite (top-level or nested) |
Get Started
Generate a Personal Access Token
Go to User Settings → Personal Access Tokens in TestDino. Grant access to the projects and modules you want your assistant to query.See Generate API Keys for details.
Configure your MCP client
Add TestDino as an MCP server in Cursor or Claude Desktop.See MCP Setup for client-specific instructions.