TestRail MCP Server
Related Servers
Alternatives to TestRail MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceAI-native Model Context Protocol (MCP) server for TestRail. Lets Claude, Cursor, Windsurf, and other AI assistants browse projects, create and update test cases, kick off test runs, and record results through natural-language conversation — with strongly-typed tool schemas and per-project custom field validation that helps LLMs generate valid TestRail requests on the first try.281,082 npm39Apache 2.0
- FlicenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol server that provides integration with TestRail, allowing AI assistants to interact with TestRail projects, test cases, test runs, and results.1,138 npm1-
- 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
- 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.544 npm2MIT
- 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
- AlicenseCqualityDmaintenanceModel Context Protocol (MCP) server for Redmine that provides comprehensive access to the Redmine REST API, enabling users to operate Redmine from MCP clients such as Claude Desktop.909 npmMIT
TDQS
Scored across 23 tools
Each tool targets a distinct resource (case, dataset, project, run, result) and action (add, get, update, delete). No overlapping purposes; an agent can easily distinguish them.
All tool names follow a consistent `verb_noun` pattern with underscores (e.g., add_case, get_projects). No mixing of conventions like camelCase or inconsistent verbs.
23 tools is on the higher side but still reasonable for a comprehensive test management API covering projects, cases, runs, results, and datasets. Slightly more than ideal but each tool serves a clear purpose.
The surface covers basic CRUD for projects, cases, runs, and datasets, but lacks operations for suites, sections, and updating results. Notable gaps like missing `update_result` and suite management limit completeness.