TestRail MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TESTRAIL_API_KEY | Yes | Your TestRail API key. | |
| TESTRAIL_BASE_URL | Yes | The base URL of your TestRail instance (e.g., https://your-instance.testrail.io). | |
| TESTRAIL_USERNAME | Yes | Your TestRail username (email). | |
| TESTRAIL_PROJECT_ID | Yes | The TestRail project ID to work with (required). |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | Get all TestRail projects |
| get_projectB | Get the configured TestRail project details |
| list_suitesA | Get all test suites for the configured project |
| get_suiteA | Get a specific test suite by ID |
| list_test_casesA | Get test cases for the configured project. Optionally filter by suite_id. |
| get_test_caseA | Get a specific test case by ID |
| create_test_runB | Create a new test run in the configured TestRail project |
| list_test_runsA | Get test runs for the configured project. Optionally filter by suite_id. |
| get_test_runB | Get a specific test run by ID |
| add_test_resultsA | Add test results for multiple test cases in a test run. Status IDs: 1=Passed, 2=Blocked, 3=Untested, 4=Retest, 5=Failed |
| get_test_resultsA | Get all test results for a test run |
| close_test_runA | Close a test run (marks it as completed) |
| update_test_caseD | Update a test case with new information |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/yshpyluk/mcp-testrail'
If you have feedback or need assistance with the MCP directory API, please join our Discord server