testrails-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TESTRAIL_URL | Yes | Your TestRail instance URL (e.g., https://yourcompany.testrail.io) | |
| TESTRAIL_USER | Yes | Your TestRail email address | |
| TESTRAIL_API_KEY | Yes | Your TestRail API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List all TestRail projects. |
| list_suitesC | List test suites for a project. |
| list_sectionsA | List sections in a project (optionally filtered by suite). |
| list_casesB | List test cases in a project. Filter by suite and/or section. |
| get_caseA | Get a single test case by id. |
| add_caseC | Create a new test case in a section. custom_fields: pass TestRail custom fields like {"custom_steps": "..."} |
| update_caseA | Update an existing test case. Only provided fields are changed. |
| delete_caseC | Delete a test case. soft=True previews the deletion without applying it. |
| list_runsC | List test runs for a project. |
| get_runB | Get a single test run by id. |
| add_runB | Create a test run. If case_ids is provided, include_all defaults to False. |
| close_runA | Close a test run (archives it; cannot be reopened). |
| list_testsC | List tests (case-instances) inside a run. |
| add_result_for_caseC | Add a result for a case within a run. status_id: 1=Passed, 2=Blocked, 3=Untested, 4=Retest, 5=Failed (TestRail defaults). |
| get_results_for_caseC | Get all results recorded for a case in a given run. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
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.
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.
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.
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.