Testrail MCP Server

A Model Context Protocol (MCP) server for TestRail that allows interaction with TestRail's core entities through a standardized protocol.

Local serverstdioPython

What is the Testrail MCP MCP server?

If you want an AI assistant working directly with Testrail MCP, the testrail mcp mcp server is the bridge. A Model Context Protocol (MCP) server for TestRail that allows interaction with TestRail's core entities through a standardized protocol.

What Testrail MCP does

A Model Context Protocol (MCP) server for TestRail that allows interaction with TestRail's core entities through a standardized protocol.

Key capabilities

  • Authentication with TestRail API
  • Access to TestRail entities:
  • Full support for the Model Context Protocol
  • Compatible with any MCP client (Claude Desktop, Cursor, Windsurf, etc.)

Tools it exposes

Once connected, the assistant can call these 2 tools directly:

  • Cursor — In Cursor, add a new custom tool with the following configuration:
  • Windsurf — In Windsurf, add a new tool with the following configuration:

Installing the testrail mcp mcp server

The server is distributed via npm as @smithery/cli, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 3 environment variables: TESTRAIL_URL, TESTRAIL_USERNAME, TESTRAIL_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Testrail MCP sits in that group, and the shape of its toolset — Cursor, Windsurf — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Maintained by sker65, written in Python.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the testrail mcp mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
CursorIn Cursor, add a new custom tool with the following configuration:
WindsurfIn Windsurf, add a new tool with the following configuration:

How to install the Testrail MCP MCP server

{
  "mcpServers": {
    "testrail": {
      "command": "npx",
      "args": ["-y", "@smithery/cli"],
      "env": {
        "TESTRAIL_URL": "your-value",
        "TESTRAIL_USERNAME": "your-value",
        "TESTRAIL_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
TESTRAIL_URLEndpoint or connection string the server talks to.Yes
TESTRAIL_USERNAMEConfiguration value read at startup.Optional
TESTRAIL_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Testrail MCP to Cursor.
  • Use Testrail MCP to Windsurf.

Frequently asked questions

It connects Testrail MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Cursor, Windsurf) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Testrail MCP directly.