TestRelic MCP

The TestRelic MCP server speaks the Model Context Protocol so coding assistants (Cursor, Claude Desktop, VS Code, and others) can use your TestRelic data: projects, recent runs, user journeys, coverage gaps, and suggested tests—without pasting screenshots or logs into chat.

It complements the SDK reporters: reporters send run data to the cloud; the MCP lets an agent query and act on that context while you write or fix tests.

Cursor Marketplace plugin

The fastest way to try the MCP in Cursor:

1. Open Cursor and search Settings → Plugins for testrelic-mcp.
2. Click Install. Cursor wires up the MCP server automatically.
3. Open the agent and ask something like "list my TestRelic projects".

The marketplace default boots in mock mode so you can explore every tool without an account or token. To connect real org data, see Authentication.

Mock mode is the default

The zero-config / marketplace install runs with --mock-mode: no network calls and no token. To connect live data, create a personal access token (tr_mcp_*) at platform.testrelic.ai/settings/mcp-tokens, run npx @testrelic/mcp login (or set TESTRELIC_MCP_TOKEN=tr_mcp_…), and drop --mock-mode. See Quickstart and Authentication.

Tool namespace (tr_*)

v2 tools are exposed with the tr_* prefix (for example tr_list_repos, tr_coverage_report, tr_heal_run, tr_analyze_diff). The older testrelic_* names are kept as deprecated aliases for backward compatibility. See the Tools reference.

Purpose

Use this overview to understand how the MCP server sits between your IDE and the TestRelic cloud, and where to go next for install, auth, and capabilities.

Architecture: MCP host and TestRelic

Tool traffic path (conceptual)

Sankey view of how a tool call moves from your MCP host through stdio into the MCP server and out to TestRelic cloud APIs. Link widths are symbolic, not measured throughput.

Loading chart…

One token

You authenticate with a single MCP personal access token. Jira, Amplitude, Grafana Loki, TestMu AI, BrowserStack, and similar integrations are configured in the TestRelic cloud for your organization—not as extra secrets in MCP config.

Authenticate →

Install & connect

Hosted MCP at mcp.testrelic.ai, stdio via npx @testrelic/mcp, or the Cursor marketplace plugin. Production uses your MCP token; mock mode is sandbox-only.

→

Authenticate

Create an MCP token in Settings, then save it with the login command or an environment variable.

→

Capabilities

Enable tool groups with --caps: core, coverage, creation, healing, impact, triage, signals, devtools.

→

Use with your suite

End-to-end flow: SDK → cloud data → MCP in your IDE while you author, triage, or refactor tests.

→

Troubleshooting

Symptom	What to try
Tool errors mentioning auth	Follow Authentication — MCP personal access token and mock mode.
Only mock or empty results	Disable --mock-mode when you expect live cloud data, and verify the token is set in the environment your MCP host uses.

FAQ

Do I configure Jira or Grafana secrets in mcp.json?

No for those integrations — they are configured in the TestRelic cloud for your organization. The MCP uses your TestRelic MCP token only.

Does the MCP replace the Playwright or Appium reporter?

No. Reporters capture test output; the MCP exposes cloud-side context to your assistant while you work in the IDE.

Which clients are supported?

Any MCP-compatible host (Cursor, Claude Desktop, VS Code extensions, and others) can run the server over stdio as described in the quickstart.

What is the cloud URL the MCP talks to?

The TestRelic cloud is at https://platform.testrelic.ai (API base https://platform.testrelic.ai/api/v1). Personal access tokens are created at platform.testrelic.ai/settings/mcp-tokens.

Source repository

Implementation and issue tracker: github.com/testrelic-ai/testrelic-mcp-server.

Next steps

→ Quickstart: install the MCP server