Testdino MCP
@testdino-hq
关于 Testdino MCP
A MCP server that bridges TestDino with AI agents such as Cursor and Claude. Navigate test results, analyze failures, and manage test cases through conversational commands.
基本信息
配置
使用下面的配置,将此服务器添加到你的 MCP 客户端。
{
"mcpServers": {
"TestDino": {
"command": "npx",
"args": [
"-y",
"testdino-mcp"
],
"env": {
"TESTDINO_PAT": "Your PAT here"
}
}
}
}工具
12Check if your TestDino connection is working. Verifies your PAT, shows your account information, and lists available organizations and projects. Use this first to make sure everything is set up correctly and to get organization/project IDs for other tools.
Browse and filter your test runs to find specific test executions. Filter by git branch (e.g., 'develop', 'main'), time interval ('Latest', '1h', '2h', '5h', '1d', '3d', '5d', 'weekly', 'monthly', or custom date ranges), commit author, or environment (e.g., 'production', 'staging', 'development'). Supports efficient pagination using page/limit or offset/limit, or use get_all=true to fetch all results (up to 1000). Returns test run summaries with statistics (total, passed, failed, skipped, flaky counts), duration, status, branch, author, and PR information when available. Perfect for answering questions like 'What tests ran on the develop branch?' or 'Show me all test runs from last hour.' The PAT should be configured in mcp.json as TESTDINO_PAT environment variable.
Get detailed information about test runs. Shows test statistics (passed, failed, skipped, flaky), all test suites and cases, git metadata, and error details. Supports batch operations (comma-separated IDs, max 20). Use this to analyze test execution health or debug specific failures.
List test cases with comprehensive filtering options. You can filter by test run (ID or counter), status, spec file, error category, browser, tags, runtime, artifacts, error messages, attempt number, branch, time interval, environment, author, or commit hash. When using test run filters (by_branch, by_commit, by_author, by_environment, by_time_interval, by_pages, page, limit, get_all), the tool first lists test runs matching those criteria, then returns test cases from those filtered test runs. Use this to find specific test cases across your test runs.
Get detailed information about a specific test case. You can identify the test case in two ways: 1) By testcase_id (can be used alone), or 2) By testcase_name combined with testrun_id or counter (required because test cases can have the same name across different test runs). Shows error messages, stack traces, test steps, console logs, and optional artifacts (screenshots, videos, traces). Use this to debug why a test failed or understand how it executed. Example: 'Get test case details for "Verify user can logout and login" in testrun #43'.
Fetch historical execution and failure data for a specific test case. Returns raw historical data with test run details (ID, counter, branch), test runs summary, and a debugging prompt from the API. Each execution includes its associated test run information (testRunId, testRunCounter, branch) to help correlate failures across different test runs and branches. The AI client will analyze the data to identify failure patterns, find root causes, and provide fix suggestions. Use this when you need to debug a failing test case. Example: 'Debug test case "Verify user login"'.
Search and list manual test cases with filtering capabilities. Use this to find specific manual test cases for QA testing, auditing, or test case management. Supports filtering by project, time, suite, status, priority, severity, type, layer, behavior, automation status, and tags.
Retrieve detailed information of a single manual test case, including steps, custom fields, preconditions, and all metadata. Use this to get comprehensive details about a specific test case for execution or review.
Create a new manual test case. Use this to document new test scenarios, features, or requirements. Supports adding test steps, preconditions, postconditions, and metadata like priority, severity, and type.
Update an existing manual test case. Use this to modify test case details, steps, status, priority, or any other fields. Provide only the fields you want to update in the updates object.
List the test suite hierarchy to help users find suiteIds for test case creation. Use this to navigate the test suite structure and understand test organization.
Create a new test suite folder to organize test cases. Use this to create a logical grouping for related test cases. Suites can be nested by providing a parentSuiteId.
概览
What is Testdino MCP?
Testdino MCP is a Model Context Protocol (MCP) server that connects TestDino to AI agents, enabling natural language interaction with test management data. It bridges the TestDino test management platform and AI assistants, allowing users to check test runs, analyze failures, manage test cases, plan releases, and more via conversational commands.
How to use Testdino MCP?
Add the server to your MCP client configuration (e.g., ~/.cursor/mcp.json for Cursor) with npx -y testdino-mcp and the environment variable TESTDINO_PAT set to your Personal Access Token from TestDino User Settings. Then restart the client and ask your assistant to "Check TestDino health" to verify.
Key features of Testdino MCP
- Health check to verify connection and PAT validity
- Test run management with filtering (branch, time, author, commit, environment)
- Test case analysis including errors, logs, execution steps, and artifacts
- AI-assisted debugging with historical failure pattern analysis
- Test quality audit with local analysis and report storage
- Manual test case and suite management (create, update, list, filter)
- Release planning with nested milestones and progress stats
- Manual test runs with assignment and per-case verdicts
- Exploratory session creation and tracking
- 27 tools across six domains (test execution, case management, releases, runs, sessions, audit)
Use cases of Testdino MCP
- Check test run results and analyze failures directly from chat
- Manage manual test cases and organize them into test suites
- Plan releases, create manual test runs, and assign testers without leaving the IDE
- Run exploratory testing sessions and record per-case verdicts (passed, failed, blocked, etc.)
- Debug flaky tests or root-cause failures with aggregated historical data
FAQ from Testdino MCP
What is the Testdino MCP server and what does it do?
It is an MCP server that connects TestDino to AI agents, allowing you to interact with your test data (test runs, test cases, releases, exploratory sessions) through natural language commands.
How do I configure Testdino MCP with Cursor?
Add the server definition to ~/.cursor/mcp.json (macOS/Linux) or %APPDATA%\Cursor\mcp.json (Windows) with command: "npx", args: ["-y", "testdino-mcp"], and env: { "TESTDINO_PAT": "your-pat" }. Restart Cursor, then verify with "Check TestDino health".
What are the installation options?
Three options: (1) via npx (recommended – no installation, always latest), (2) global npm install (npm install -g testdino-mcp, requires Node.js 20+), (3) project-level installation (npm install testdino-mcp).
What tools does Testdino MCP provide?
The server provides 27 tools across six domains: test execution and results (health, list_testruns, get_run_details, etc.), test case management (list_manual_test_cases, create, update), releases (list_releases, create, update), manual test runs (create, update, assign and verdict), exploratory sessions (create, update), and test audit.
Is my authentication token secure?
Yes. Your TestDino PAT is
浏览器自动化 分类下的更多 MCP 服务器
Fetch MCP
jae-jaeMCP server for fetch web page content using Playwright headless browser.
BrowserTools MCP
AgentDeskAIMonitor browser logs directly from Cursor and other MCP compatible IDEs.
Webpage Screenshot MCP Server
ananddtyagiAn MCP that gives your agent the ability to snap a screenshot of webpages. Useful when you want your agent to check its progress during development.
Fastcrw
usFast, lightweight Firecrawl/Tavily alternative in Rust. Web scraper, crawler & search API with MCP server for AI agents. Drop-in Firecrawl-compatible API (/scrape, /crawl, /search). 2.3x faster than Tavily, 1.5x faster than Firecrawl in 1K-URL benchmarks. 6 MB RAM, single binary.
Yoyo
firecrawl🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
评论