TestRail MCP Server

by bun913

Not rated
GitHub

About

Interact with TestRail to manage test cases, projects, suites, and runs directly from your AI chat client.

Details

Author
bun913
Categories
Developer Tools

Setup

Install TestRail MCP Server in your MCP client (Claude Desktop, Cursor, Windsurf, and others).

Repository: https://github.com/bun913/mcp-testrail

Follow the installation instructions in the repository README, then restart your MCP client.

This Model Context Protocol (MCP) server provides tools for interacting with TestRail directly from Claude AI and other MCP-supported clients like Cursor. It allows you to manage test cases, projects, suites, runs, and more without leaving your conversation with the AI.

The TestRail MCP server provides the following tools:

You can connect this MCP server by setting like the below. This method usesnpxto automatically download and run the latest version of the package, eliminating the need for local installation.

// Example configuration using npx { "mcpServers": { "testrail": { "command": "npx", "args": ["@bun913/mcp-testrail@latest"], "env": { "TESTRAIL_URL": "https://your-instance.testrail.io", // Replace with your TestRail URL "TESTRAIL_USERNAME": "your-email@example.com", // Replace with your TestRail username "TESTRAIL_API_KEY": "YOUR_API_KEY" // Replace with your TestRail API key } } } }

-

spawn npx ENOENT/spawn node ENOENT(commonly on macOS): your MCP host (Cursor, Claude Code, Claude Desktop, …) cannot findnpxornodeat process-spawn time. The chat UI usually surfaces this as a generic "MCP server doesn't work" with no useful detail; the per-server log is the diagnostic source of truth.

Why it happens on macOS:GUI apps launched from the Dock, Spotlight, or Finder inherit launchd's minimalPATH(/usr/bin:/bin:/usr/sbin:/sbin). If you installed Node via a version manager (nvm,asdf,mise,fnm,Volta) or Apple Silicon Homebrew (/opt/homebrew/bin/),npxlives outside that PATH — only your shell startup file (~/.zshrc/~/.bashrc) adds it. Your terminal works because the shell ran the startup file; the GUI-app process never did.

Diagnoseby checking the per-server log forspawn npx ENOENT:

- Cursor:~/Library/Application Support/Cursor/logs/<session>/window<N>/exthost/anysphere.cursor-mcp/MCP <server>.log
- Claude Code / Claude Desktop:~/Library/Logs/Claude/

Fixby replacing"npx"in your MCP config with its absolute path. Runwhich npxin your normal terminal:

/Users/you/.nvm/versions/node/v24.15.0/bin/npx # nvm /opt/homebrew/bin/npx # Apple Silicon Homebrew /usr/local/bin/npx # Intel Homebrew / system Node
{ "mcpServers": { "testrail": { "command": "/Users/you/.nvm/versions/node/v24.15.0/bin/npx", "args": ["@bun913/mcp-testrail@latest"], "env": { "TESTRAIL_URL": "https://your-instance.testrail.io", "TESTRAIL_USERNAME": "your-email@example.com", "TESTRAIL_API_KEY": "YOUR_API_KEY" } } } }

Restart your MCP client after the change. The same fix applies to everynpx-launched MCP server — ifmcp-testrailis failing for this reason, your othernpx-launched servers are likely failing too.

Authentication issues: Check your TestRail API credentials.

Your conversation is too long: Uselimitandoffsetparameters for test cases and sections to paginate results.

HTTP 400 errors when creating/updating test cases: TestRail projects have different templates, custom fields, and required fields. This MCP server passes your parameters directly to the TestRail API — it does not validate or transform them. If you encounter 400 errors, define your project's rules inCLAUDE.mdorAGENTS.mdso the LLM sends the correct parameters. For example:

# TestRail Rules for This Project - Project ID: 1 - Always use template 2 (Separated Steps) when creating test cases - Use customStepsSeparated (array of step objects) - Do NOT send customSteps or customExpected with template 2 - Required custom fields: custom_automation_type (default: 0) - Call getCaseFields at the start of a session to check available fields

Contributions are welcome! Please feel free to submit a Pull Request.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Create crafted UI components inspired by the best 21st.dev design engineers.

Bring agent evaluations, observability, and synthetic test set generation directly into your IDE for free with Galileo's new MCP server

An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .

MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent

ALAPI MCP Tools,Call hundreds of API interfaces via MCP

AI-powered SVG animation generator that transforms static files into animated SVG components using the Allyson platform

MCP server that gives AI assistants on-demand access to 1,500+ amCharts docs, ~300 code examples, and 1000+ class API references.

APIMatic MCP Server is used to validate OpenAPI specifications using APIMatic. The server processes OpenAPI files and returns validation summaries by leveraging APIMatic’s API.

One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.

Build and deploy full-stack Next.js apps with 98 tools for React, AWS, and MongoDB

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.