TestRail MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TESTRAIL_URL | Yes | The full URL to your TestRail instance (e.g., https://example.testrail.io) | |
| TESTRAIL_API_KEY | Yes | Your TestRail API key (not your password), generated from 'My Settings' > 'API Keys' | |
| TESTRAIL_USERNAME | Yes | Your TestRail email address used for login |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_projectB | Get a project by ID |
| get_projectsB | Get all projects |
| add_projectC | Add a new project |
| update_projectC | Update an existing project |
| delete_projectC | Delete a project |
| get_caseA | Get a test case by ID |
| get_casesC | Get all test cases for a project/suite |
| add_caseC | Add a new test case |
| update_caseC | Update an existing test case |
| delete_caseC | Delete a test case |
| get_runA | Get a test run by ID |
| get_runsC | Get all test runs for a project |
| add_runC | Add a new test run |
| update_runC | Update an existing test run |
| close_runC | Close an existing test run |
| delete_runC | Delete a test run |
| get_resultsC | Get all test results for a test |
| add_resultC | Add a new test result |
| get_datasetC | Get a dataset by ID |
| get_datasetsC | Get all datasets for a project |
| add_datasetC | Add a new dataset |
| update_datasetC | Update an existing dataset |
| delete_datasetC | Delete a dataset |
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 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.