TestRail MCP. Query test runs and case data conversationally.

Yo, listen up. This TestRail MCP Server hooks your whole QA process right into your AI client. You don't gotta jump between tabs or mess with that clunky web UI just to check build status or pull test steps. Instead, you ask your agent questions about the test data, and it pulls the exact answers straight out of TestRail.

To start, you first list every active project on your TestRail instance. This gives you all the Project IDs you'll need for everything else. From those projects, you can pull general info using get_test_project_details, giving you a high-level look at what that whole project is about.

When it comes to structure, this server maps out your entire test repository. You can list every available suite of tests within a specific project scope using list_test_suites. Furthermore, if you need to map out the folder hierarchy—the sections—you call list_project_sections, which shows you all those nested folders inside a given project.

If you want a full rundown of test cases, you can use list_test_cases, and you've got the option to filter that list by which suite they belong to.

Need to dig deep on one specific piece? You get detailed info for any single test case ID using get_test_case_details. That pulls out all the metadata, the step-by-step logic, and what preconditions you gotta meet before you even start. If you want a quick overview of the whole project without going deep into sections, you can just call list_test_cases to get all test cases within that scope.

For tracking progress, this is where it shines. You'll first list all historical and active test runs in a specific project using list_test_runs. Once you have a Run ID, you use get_test_run_details for a complete summary. That tells you exactly which tests passed, failed, or are even blocked—you get the pass/fail counts without opening the dashboard.

You can also list every single test case instance that was executed during that specific run using list_run_tests. This lets your agent tell you precisely what happened across all those individual runs.

Finally, for planning and deadlines, it keeps you in sync. The server pulls a complete list of defined QA milestones associated with a project ID via list_project_milestones, showing you the target dates. You can also get general data on projects using get_test_project_details to understand the overall architecture.

You use these tools together: First, grab the Project IDs. Then, map out the sections and suites. Next, find the specific test case details or list all cases. After that, you check the runs—getting the run ID first with list_test_runs, then pulling the summary results using get_test_run_details. You've got everything from project structure to current pass/fail counts, all without touching a single web UI.