#test-management

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.

A Model Context Protocol server for the QA Sphere test management system. This integration enables Large Language Models (LLMs) to interact directly with QA Sphere test cases, allowing you to discover, summarize, and chat about test cases. In AI-powered IDEs that support MCP, you can reference specific QA Sphere test cases within your development workflow.

MCP Server for QA Sphere TMS