A
licenseB
qualityD
maintenanceEnables management of TestRail projects, suites, test cases, runs, and results through natural language.
42
2,408 npm
MIT
TestMu AI Test Manager MCP
Related Servers
Alternatives to TestMu AI Test Manager MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with Testomat.io test management platform, allowing users to search and retrieve tests, test suites, test runs, and test plans using natural language queries with advanced filtering capabilities.454 npm-
- 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
- AlicenseNot gradedqualityBmaintenanceEnables AI-driven management of Zephyr test assets and Jira integrations through natural language, including creating test cases, steps, cycles, and linking tests to issues.1MIT
- 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.1720 npm4MIT
- FlicenseAqualityBmaintenanceEnables AI agents to manage Autotest AI projects, screens, test cases, and test runs through natural language commands.10-
TDQS
A4.1/5.0
Scored across 39 tools
Disambiguation4/5
Tools are mostly distinct with clear resource+action targets. Some potential confusion between 'get_testCaseInstancesByTestRunId' and 'get_testCaseInstanceById' (collection vs single), but descriptions explicitly distinguish IDs and granularity. Overlap is minimal.
Naming Consistency4/5
Predominantly follows 'tm.<verb>_<noun>' pattern (e.g., create_testCases, get_testRunById). Inconsistency with 'bulkUpdate_testCaseInstances' using camelCase for 'bulkUpdate' while others use snake_case (e.g., 'add_testCasesToTestRun'). Overall convention is mostly consistent.
Tool Count3/5
39 tools is high for a single server, covering Test Manager, HyperExecute, and AI RCA. Many are read-only, but the count feels heavy. Tools are scoped to a specific domain, but some granularity could be merged (e.g., multiple get_hyperExecute* tools).
Completeness3/5
Covers main CRUD for test artifacts and execution lifecycle, plus Jira linking and RCA. Notable gaps: no deletion tools for projects/folders/test cases/runs, no listing of all projects (only by ID), and no direct update of existing test steps (only append). Core workflows are present but missing cleanup operations.
Maintenance
ActivityInactive
ResponsivenessNo issues