A
licenseNot graded
qualityD
maintenanceMCP 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
testrails-mcp
by adakh3
Related Servers
Alternatives to testrails-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceMCP server for TestRail API, providing AI assistants with 107 tools to manage test cases, runs, results, plans, and more. Supports API key, password, and SSO cookie authentication.549 npm2MIT
- AlicenseBqualityDmaintenanceEnables TestRail test management through MCP tools, allowing users to manage projects, test cases, runs, and results via natural language.2533 npmMIT
- AlicenseAqualityFmaintenanceEnables management of TestRail projects, test cases, runs, and results directly through MCP-supported clients. It provides a comprehensive set of tools to interact with the TestRail API for seamless test cycle management within AI environments.426,164 npm44MIT
- AlicenseBqualityBmaintenanceAn MCP server for TestRail that prepares everything needed to generate test cases from Jira tickets, Confluence pages, or free-form specs and pushes them back to TestRail.312MIT
- AlicenseBqualityBmaintenanceEnables managing TestRail projects, suites, cases, sections, runs, tests, results, plans, milestones, and shared steps directly from MCP-supported AI clients.44MIT
TDQS
A3.5/5.0
Scored across 15 tools
Disambiguation5/5
Each tool targets a distinct TestRail entity or action (project, suite, section, case, run, result, test) with clear boundaries, e.g., add_case vs update_case, list_cases vs get_case, add_result_for_case vs get_results_for_case. No two tools have overlapping purposes.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern using snake_case (e.g., add_case, get_run, list_sections). Verbs are imperative (add, get, list, delete, close, update) and nouns are singular entity names. Minor prepositions like 'for_case' are uniform.
Tool Count5/5
Fifteen tools is well-scoped for a TestRail MCP covering core entities: projects, suites, sections, cases, runs, results, and tests. Each tool serves a clear purpose without unnecessary bloat or missing essentials.
Completeness4/5
The tool set provides full CRUD for test cases and runs, plus read and list operations for most entities. However, missing create/update/delete for sections and suites are notable gaps that agents would need to work around, though core test workflow is covered.
Maintenance
ActivityInactive
ResponsivenessNo issues