testmo-mcp
Related Servers
Alternatives to testmo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for TestRail that enables AI assistants to interact with TestRail's test management platform. It can query and manage projects, test cases, runs, results, plans, milestones, and more.MIT
- AlicenseAqualityCmaintenanceAn MCP server that connects AI agents to TestOps, enabling test case management, launches, defects, and analytics through natural language.4812 npmMIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that exposes Kiwi TCMS as a set of AI-callable tools, enabling assistants to create and manage test plans, test cases, test runs, and executions directly from a conversation.1-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that connects AI assistants to Xray Cloud for Jira test management, enabling natural language interaction with tests, test plans, executions, and CI result imports.MIT
- FlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to programmatically run tests, query results, and receive intelligent recommendations about test execution strategy.-
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with TestOps 5.25 for managing projects, test runs, test plans, and test cases via MCP tools.3139 npmMIT
TDQS
Scored across 15 tools
Each tool targets a distinct resource and action. The only potential overlap is record_result vs record_results_bulk, but they are clearly single vs bulk operations. The escape hatch testmo_get is explicitly for uncovered endpoints, so no confusion.
The testmo_ prefix and verb_noun pattern are consistent across tools (list_projects, create_run, update_cases). The single exception is testmo_get which lacks a noun object, but as a general escape hatch this is a minor deviation.
15 tools is at the upper boundary of the ideal range but each tool serves a clear purpose in the Testmo workflow, covering projects, runs, results, cases, and supporting lookup data (statuses, states, templates).
Core CRUD for runs and cases is covered (create, list/get, update) though delete is missing. Results can be listed and recorded both single and bulk. The escape hatch covers additional GET endpoints but not other HTTP methods. Overall the main workflows are covered.