A
licenseB
qualityD
maintenanceEnables TestRail test management through MCP tools, allowing users to manage projects, test cases, runs, and results via natural language.
25
12 npm
MIT
TestRail MCP Server
by akoehlerbbw
Related Servers
Alternatives to TestRail MCP Server
No user-submitted related servers found.
Related Servers
- 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.421,101 npm44MIT
- AlicenseBqualityCmaintenanceEnables management of TestRail projects, suites, test cases, runs, and results through natural language.421,101 npmMIT
- 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
- 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
- AlicenseAqualityDmaintenanceMCP server for TestRail that enables AI agents to manage test cases, runs, and results, plus a bundled skill to convert Jira tickets into TestRail test cases.15MIT
TDQS
B3.2/5.0
Scored across 44 tools
Disambiguation4/5
Most tools target a distinct resource and action, and the singular/plural get patterns are clear. The main confusion risk is moveSection vs moveToSection, which sound similar but operate on different things, and the several result-fetching variants could be briefly confusing.
Naming Consistency4/5
Tool names mostly follow a consistent verb+resource camelCase pattern such as getCases, addCase, updateCase, deleteSection, and addRun. Minor deviations like addBdd/getBdd and nested names like addRunToPlanEntry are understandable but slightly break the uniform pattern.
Tool Count2/5
44 tools is a very large surface for an MCP server. While TestRail covers many entity types and most tools correspond to real API operations, the count makes selection harder and exceeds the range where a tool set feels tight and easily navigable.
Completeness3/5
Core case, section, run, and result workflows are well covered, including bulk operations and BDD import/export. However, several secondary resources are incomplete: milestones only support get/add, shared steps are read-only, and plans lack update/delete operations.
Maintenance
ActivityMaintained
ResponsivenessNo issues