TestDino MCP
Related Servers
Alternatives to TestDino MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Testmo test management platform for creating, reading, updating, and deleting test cases, managing folders, and organizing test runs through natural language.4MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with TestRail test management systems through comprehensive API integration. Supports retrieving and updating test cases, projects, suites, runs, and results, plus adding attachments and managing test data through natural language commands.1812 npmMIT
- FlicenseAqualityBmaintenanceEnables AI agents to manage Autotest AI projects, screens, test cases, and test runs through natural language commands.10-
- AlicenseAqualityBmaintenanceConnects AI coding assistants to TestCollab for managing test cases, plans, and suites directly through natural language. It enables users to create, update, and query testing resources within integrated development environments and AI chat clients.1717 npm4MIT

Tesults MCPofficial
AlicenseNot gradedqualityDmaintenanceConnect AI agents to your test results, insights, and targets. Query test runs, failures, flaky tests, and regressions across frameworks including Playwright, Jest, Pytest, Cypress and more.23 npmMIT- AlicenseBqualityDmaintenanceEnables AI assistants to interact with TestRail test management system, supporting full CRUD operations on projects, suites, sections, test cases, runs, results, plans, and milestones.351,504 npm1MIT
TDQS
Scored across 35 tools
Some tools have overlapping purposes or very similar names, such as list_testcase vs list_manual_test_cases and get_testcase_details vs get_manual_test_case, which differ only by 'manual'. Additionally, get_run_details and get_ai_insights both surface AI insights, requiring careful attention to the polling flow. Descriptions are detailed and help differentiate, but the boundaries are not always crisp.
Most tools follow a verb_noun pattern, but object naming is inconsistent: 'testruns' vs 'test_run' vs 'run', and 'testcase' vs 'test_case' (e.g., list_testruns vs list_run_test_cases, list_testcase vs list_manual_test_cases). The tool 'health' breaks the pattern, and pluralization is inconsistent (list_testcase vs list_manual_test_cases). Still, the style is readable and mostly uniform.
35 tools is a very large surface for an MCP server, even for a comprehensive QA platform. While the scope is broad (automated runs, manual cases, releases, sessions, integrations, AI, audit), many tools are CRUD variants that could potentially be combined or streamlined. The count exceeds the threshold for 'too many' and would likely increase selection difficulty.
The tool surface covers CRUD for manual test cases, releases, manual runs, and sessions, but lacks delete operations for these entities (e.g., delete_manual_test_case, delete_release, delete_session). Automated test runs are read-only (list/get) with no way to trigger or modify them. The audit flow and integrations are well covered, but the missing lifecycle operations are notable.