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.1820 npmMIT
- FlicenseAqualityDmaintenanceEnables 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.17106 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.28 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.35154 npm1MIT
TDQS
Scored across 43 tools
Several tools have overlapping boundaries: list_testcase, list_run_test_cases, list_manual_test_cases, and list_automated_tests all return test-case-like records, and get_debug_evidence duplicates get_flake_verdict while get_run_details/debug_testcase overlap with get_ai_insights. The descriptions are detailed, but an agent could easily select the wrong listing or debugging tool.
Most tools follow a verb_noun snake_case pattern, but there are pervasive inconsistencies: list_testcase is singular while other list_* tools are plural, and testcase appears both as testcase (list_testcase, get_testcase_details, debug_testcase) and test_case (get_test_case_links, update_run_test_case). The pattern is readable but not uniform.
43 tools is well above the comfortable range and includes redundant debugging/insights entry points. The broad domain (manual testing, automation linking, releases, sessions, integrations, audit) justifies some size, but the count feels heavy and could be consolidated.
The surface covers most core workflows across runs, cases, releases, sessions, integrations, and AI insights, but there are notable gaps: no delete operations for any resource, no update/close for external issues, and session findings cannot be created. These are workable for many tasks but will cause dead ends for cleanup or issue-management requests.