Testrail MCP Server runs on your own machine — the client starts it, so there is no endpoint to ping. 1 973 installs a week from npm. Last commit 23 Oct 2026.
Connect AI assistants to TestRail: manage test cases, suites, runs, results, and attachments.
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
await fs.promises.writeFile(path.join(targetDir, docFilename), markdownContent, "utf-8");
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add testrail-mcp-server -e 'TESTRAIL_INSTANCE_URL=<TESTRAIL_INSTANCE_URL>' -e 'TESTRAIL_USERNAME=<TESTRAIL_USERNAME>' -e 'TESTRAIL_API_KEY=<TESTRAIL_API_KEY>' -- npx -y @uarlouski/testrail-mcp-server
{
"mcpServers": {
"testrail-mcp-server": {
"command": "npx",
"args": [
"-y",
"@uarlouski/testrail-mcp-server"
],
"env": {
"TESTRAIL_API_KEY": "<TESTRAIL_API_KEY>",
"TESTRAIL_INSTANCE_URL": "<TESTRAIL_INSTANCE_URL>",
"TESTRAIL_USERNAME": "<TESTRAIL_USERNAME>"
}
}
}
}
[mcp_servers.testrail-mcp-server]
command = "npx"
args = ["-y", "@uarlouski/testrail-mcp-server"]
env = { TESTRAIL_INSTANCE_URL = "<TESTRAIL_INSTANCE_URL>", TESTRAIL_USERNAME = "<TESTRAIL_USERNAME>", TESTRAIL_API_KEY = "<TESTRAIL_API_KEY>" }
{
"mcpServers": {
"testrail-mcp-server": {
"command": "npx",
"args": [
"-y",
"@uarlouski/testrail-mcp-server"
],
"env": {
"TESTRAIL_API_KEY": "<TESTRAIL_API_KEY>",
"TESTRAIL_INSTANCE_URL": "<TESTRAIL_INSTANCE_URL>",
"TESTRAIL_USERNAME": "<TESTRAIL_USERNAME>"
}
}
}
}
{
"servers": {
"testrail-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@uarlouski/testrail-mcp-server"
],
"env": {
"TESTRAIL_API_KEY": "<TESTRAIL_API_KEY>",
"TESTRAIL_INSTANCE_URL": "<TESTRAIL_INSTANCE_URL>",
"TESTRAIL_USERNAME": "<TESTRAIL_USERNAME>"
}
}
}
}
Put your own values in place of
<TESTRAIL_INSTANCE_URL> (Base URL of your TestRail instance (e.g. https://example.testrail.io)), <TESTRAIL_USERNAME> (Email address used to authenticate with TestRail), <TESTRAIL_API_KEY> (API key for authenticating with the TestRail API).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
TESTRAIL_ENABLE_SHARED_STEPS (Enable shared steps management), TESTRAIL_ENABLE_CASE_HISTORY (Enable test case history management), TESTRAIL_ENABLE_RAG_TOOLS (Enable Knowledge Base and RAG export tools), TESTRAIL_ALLOW_WRITE_OPERATIONS (Allow write operations on TestRail (defaults to true)), TESTRAIL_ALLOW_READ_OPERATIONS (Allow read operations on TestRail (defaults to true)), TESTRAIL_ALLOW_DELETE_OPERATIONS (Allow delete operations on TestRail (defaults to false)), TESTRAIL_ENABLE_DEPRECATED_TOOLS (Enable deprecated tools for backward compatibility (defaults to true)), TESTRAIL_DISABLED_TOOLS (Comma-separated list of tool names to disable), TESTRAIL_REQUEST_TIMEOUT_MS (Timeout in milliseconds for TestRail HTTP requests (defaults to 30000ms)).
Create and manage test cases, test runs and results in Testiny from your AI assistant.
Manage test suites, run tests, view results, and automate QA workflows via AI with testRigor.
Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.
Connect AI coding agents to MATLAB. Run code, tests, and analysis via MCP.
Bug tracking and test management: issues, test cases, sprints, runs, requirements and KB.
Release management and QA for custom AI assistants: RAG, releases, scored QA, signed TrustBench runs
Email A/B tests for AI agents: subject lines, managed sends, open/click tracking, and results.
Free test management over MCP: projects, test cases, plans, runs, environments and tasks.
Answers built from our own checks of this server.