TestRail MCP Server
Related Servers
Alternatives to TestRail MCP Server
No user-submitted related servers found.
Related Servers
- 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
- 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
- AlicenseAqualityAmaintenanceConnect your AI coding assistant to TestRail to manage test cases, runs, results, and more directly from VS Code, Cursor, Claude Desktop, or Claude Code.524 npm1MIT
- AlicenseBqualityBmaintenanceEnables management of TestRail projects, suites, test cases, runs, and results through natural language.42743 npmMIT
- AlicenseBqualityDmaintenanceEnables AI assistants to interact directly with TestRail instances for managing test projects, suites, cases, runs, results, plans, milestones, and attachments through the TestRail API with secure authentication.77137 npm1MIT
- 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.42743 npm44MIT
TDQS
Scored across 13 tools
Each tool targets a distinct resource (project, suite, test case, test run, test result) with a clear action (list, get, create, update, close, add). There is no overlap between list/get variants or between action verbs.
Tool names consistently follow a list_/get_ prefix for read operations and specific action verbs (create, add, update, close) for mutations, all in lowercase snake_case. The pattern is uniform and predictable.
13 tools is well within the ideal range for a domain-specific server, covering all major TestRail entities (projects, suites, test cases, runs, results) without unnecessary redundancy or bloat.
The core workflow of creating runs, adding results, and closing runs is covered, but there are notable gaps: no create/delete for test cases or suites, and no generic get_project by ID. This limits full lifecycle management of test assets.