MCP SERVERKeep TestRail current from wherever the tests run: file and update cases, post a whole run's results in one call, reorganise sections, and move Gherkin .feature files in and out.
No longer maintained. The GitHub repository for this server is archived — no fixes or security updates are expected.
LABSCO SUMMARY
The surface mirrors TestRail's own nouns, with two additions that matter in practice: addResultsForCases posts an entire run's outcome in a single call, and getCases deliberately omits steps and expected results so listing a suite does not fill the context window. Milestones and shared steps are read-only here, and nothing deletes a run or a plan — cases and sections can be removed, but run cleanup still happens in the UI.
A server over the TestRail API covering projects, suites, sections, cases, runs, tests, results, plans, milestones and shared steps.
TESTRAIL_URL, TESTRAIL_USERNAME and TESTRAIL_API_KEY for a TestRail instance that account can reach. Writing customStepsSeparated needs templateId=2, and addBdd creates its case on the BDD template, template_id=4. MIT.
One command plus a key — npx -y @bun913/mcp-testrail, then supply credentials
USE CASES
Find the run, read the tests it contains, then post every result in one call instead of one request per case. Reading the results back afterwards confirms what TestRail actually stored.
Check which case types and fields the instance defines before writing, add the section the feature belongs in, then create the cases with their steps and expected results.
Read the current section tree with pagination, move a section to a new position or parent, and shift the cases themselves — moved when they belong elsewhere, copied when both places need them.
Import a .feature file straight into a section — it lands as a case on the BDD template with the scenario in its own field — and export any BDD case back to Gherkin when the repository needs to be the source again.
Pull the case with its steps, read its change history to see which fields moved and when, then check the results recorded for it in the run where it broke.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
addBddImports/uploads a .feature file (Gherkin BDD scenario) into a TestRail section. Creates a new test case with BDD template (template_id=4) and populates the custom_testrail_bdd_scenario field. REQUIRED: sectionId, featureContent (raw Gherkin text including Feature:, Scenario:, Given/When/Then).
addCaseCreates a new test case in TestRail. REQUIRED: sectionId, title. OPTIONAL: typeId, priorityId, templateId, customSteps, customExpected, customStepsSeparated, customFields, etc. Use getCaseTypes to find valid typeId values. NOTE: templateId=2 is required to use customStepsSeparated (array of step objects with 'content' and 'expected' fields). For simple text steps, use customSteps and customExpected instead. Use customFields for any additional custom fields (e.g., {custom_case_security_score: 'high'}).
addPlanCreates a new test plan in a TestRail project.
addPlanEntryAdds a new test plan entry to an existing test plan.
addResultForCaseAdds a test result for a specific test case in a test run.
addResultsForCasesAdds test results for multiple test cases in a test run.
addRunCreates a new test run in a TestRail project.
addRunToPlanEntryAdds a new test run to an existing plan entry.
addSectionCreates a new section in a TestRail project.
addSuiteCreates a new test suite in the specified project.
copyToSectionCopies specified test cases to a target section while keeping the originals.
deleteCaseDeletes a test case from TestRail.
deleteSectionDeletes a section.
getBddExports a BDD test case as a .feature file in Gherkin format. REQUIRED: caseId.
getCaseRetrieves complete details for a single test case including steps, expected results, and prerequisites. REQUIRED: caseId.
getCaseFieldsRetrieves all available test case fields in TestRail.
getCaseHistoryRetrieves the change history of a test case including updates to fields and custom fields.
getCasesRetrieves test cases list with basic fields only (excludes steps/expected results for performance). REQUIRED: projectId, suiteId. OPTIONAL: createdBy, filter, limit (default 50), milestoneId, offset (default 0), priorityId, refs, sectionId, templateId, typeId, updatedBy, labelId. Use getCase for full details.
getCaseTypesRetrieves all available test case types in TestRail.
getMilestonesRetrieves all milestones for a specified TestRail project.
getPlansRetrieves all test plans for a specified TestRail project.
getProjectRetrieves details of a specific TestRail project by ID.
getProjectsRetrieves all TestRail projects.
getResultsRetrieves test results for a specific test.
getResultsForCaseRetrieves test results for a specific test case in a test run.
getResultsForRunRetrieves all test results for a test run.
getRunRetrieves details of a specific test run by ID.
getRunsRetrieves all test runs for a specified TestRail project.
getSectionRetrieves details of a specific section by ID.
getSectionsRetrieves sections for a specified project and suite. Supports pagination via limit and offset parameters (default: limit=250, offset=0). Use _links.next to determine if more pages are available.
getSharedStepsRetrieves all shared steps for a specified TestRail project.
getSuiteRetrieves details of a specific test suite by ID.
getSuitesRetrieves all test suites for a specified TestRail project.
getTestRetrieves complete details for a single test, including all fields such as status, type, and results.
getTestsRetrieves a list of tests for a test run.
moveSectionMoves a section to a new position in the test hierarchy.
moveToSectionMoves specified test cases to a target section.
updateCaseUpdates an existing test case. REQUIRED: caseId. OPTIONAL: title, typeId, priorityId, templateId, customSteps, customExpected, customStepsSeparated, customFields, etc. Only specified fields will be updated. NOTE: templateId=2 is required to use customStepsSeparated (array of step objects with 'content' and 'expected' fields). For simple text steps, use customSteps and customExpected instead. Use customFields for any additional custom fields (e.g., {custom_case_security_score: 'high'}).
updateCasesUpdates multiple test cases simultaneously with the same field values. NOTE: templateId=2 is required to use customStepsSeparated (array of step objects with 'content' and 'expected' fields). For simple text steps, use customSteps and customExpected instead. Use customFields for any additional custom fields (e.g., {custom_case_security_score: 'high'}).
updateRunUpdates an existing test run.
updateSectionUpdates an existing section.
updateSuiteUpdates an existing test suite.
BEFORE YOU INSTALL
42 tools when we connected. The documentation's table omits addPlan, addPlanEntry and addRunToPlanEntry, so test plans can be written, not just read. Names are camelCase: getCases, not get_cases.
CONTEXT COST
Rated by the size of the 42 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npx -y @bun913/mcp-testrail{
"mcpServers": {
"testrail": {
"command": "npx",
"args": [
"@bun913/mcp-testrail@latest"
],
"env": {
"TESTRAIL_URL": "https://<YOUR_INSTANCE>.testrail.io",
"TESTRAIL_USERNAME": "<YOUR_TESTRAIL_USERNAME>",
"TESTRAIL_API_KEY": "<YOUR_TESTRAIL_API_KEY>"
}
}
}
}Use this only if the first block fails on macOS with spawn npx ENOENT in the client's log (Cursor, Claude Desktop, Claude Code): apps started from the Dock do not see the PATH your shell sets up for nvm or Homebrew. Run which npx in your terminal and put that path in "command"; the one below is an nvm example, and Homebrew installs are usually /opt/homebrew/bin/npx or /usr/local/bin/npx.
{
"mcpServers": {
"testrail": {
"command": "/Users/<YOUR_USERNAME>/.nvm/versions/node/v24.15.0/bin/npx",
"args": [
"@bun913/mcp-testrail@latest"
],
"env": {
"TESTRAIL_URL": "https://<YOUR_INSTANCE>.testrail.io",
"TESTRAIL_USERNAME": "<YOUR_TESTRAIL_USERNAME>",
"TESTRAIL_API_KEY": "<YOUR_TESTRAIL_API_KEY>"
}
}
}
}MCP servers
testdino-hq
SyncTek-LLC
Milo0821
70-10