Testrail Mcp Server — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Testrail Mcp Server (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
A Model Context Protocol (MCP) server for TestRail integration, providing comprehensive access to TestRail's test management functionality through MCP tools.
This MCP server provides tools for:
npm installnpm run build.env file in the project root with your TestRail credentials:cp .env.example .envEdit .env with your credentials:
TESTRAIL_URL=https://your-instance.testrail.io
[email protected]
TESTRAIL_API_KEY=your-api-keyTo use this MCP server with Claude Code, add it to your MCP settings file:
macOS/Linux: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"testrail": {
"command": "node",
"args": ["/absolute/path/to/testrail-mcp-server/dist/index.js"],
"env": {
"TESTRAIL_URL": "https://your-instance.testrail.io",
"TESTRAIL_USERNAME": "[email protected]",
"TESTRAIL_API_KEY": "your-api-key"
}
}
}
}Or if you prefer to use the .env file:
{
"mcpServers": {
"testrail": {
"command": "node",
"args": ["/absolute/path/to/testrail-mcp-server/dist/index.js"]
}
}
}testrail_get_projects - Get all projectstestrail_get_project - Get a specific project by IDtestrail_get_cases - Get test cases from a project (optionally filtered by suite)testrail_get_case - Get a specific test case by IDtestrail_add_case - Create a new test case in a sectiontestrail_update_case - Update an existing test casetestrail_delete_case - Delete a test casetestrail_get_runs - Get all test runs in a projecttestrail_get_run - Get a specific test run by IDtestrail_add_run - Create a new test runtestrail_update_run - Update an existing test runtestrail_close_run - Close a test runtestrail_delete_run - Delete a test runtestrail_get_results - Get test results for a specific testtestrail_get_results_for_case - Get test results for a test case in a runtestrail_get_results_for_run - Get all test results for a test runtestrail_add_result - Add a test result for a specific testtestrail_add_result_for_case - Add a test result for a case in a test runtestrail_add_results - Add multiple test results (bulk operation)testrail_add_results_for_cases - Add multiple test results for cases (bulk operation)testrail_get_sections - Get sections from a project (optionally filtered by suite)testrail_get_section - Get a specific section by IDtestrail_add_section - Create a new sectiontestrail_update_section - Update an existing sectiontestrail_delete_section - Delete a sectionOnce configured, you can use these tools through Claude Code. Here are some example prompts:
List all TestRail projectsCreate a new test case in section 123 with title "Test user login" and priority HighAdd a passed test result for test case 456 in run 789 with comment "All checks passed"Create a new test run called "Sprint 24 Testing" for project 1When adding test results, use these status IDs:
1 - Passed2 - Blocked3 - Untested (retest)4 - Retest5 - FailedWhen creating or updating test cases, use these priority IDs:
1 - Low2 - Medium3 - High4 - Criticaltestrail-mcp-server/
├── src/
│ ├── index.ts # Main MCP server implementation
│ └── testrail-client.ts # TestRail API client
├── dist/ # Compiled JavaScript output
├── package.json
├── tsconfig.json
├── .env.example
└── README.mdnpm run buildnpm run watchnpm startFor more details on TestRail's API, see the official TestRail API documentation.
MIT
Contributions are welcome! Please feel free to submit issues or pull requests.
Never commit your .env file or expose your TestRail API credentials. Always use environment variables or secure credential storage.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.