8 docs tagged with "mcp"

How TestRelic SDK reporters, the cloud platform, and the MCP server fit together—runs upload from CI and local, while the MCP gives your IDE assistant structured access to that data.

Create a TestRelic MCP personal access token, store it with the login CLI or TESTRELIC_MCP_TOKEN, and align TESTRELIC_CLOUD_URL with your cloud API base when needed.

Enable TestRelic MCP tool groups with --caps—core, coverage, creation, healing, impact, triage, signals, devtools, ai, marketplace, apps, artifacts, and sessions—and pick a bundle that matches your workflow.

Connect to production TestRelic MCP via the hosted URL or stdio with the published npm package, wire mcp.json, set your MCP token, and verify with tr_health.

Curated list of TestRelic MCP tools by capability—core, coverage, creation, healing, impact, triage, signals, and devtools—with links to the full upstream catalog.

The TestRelic Ask AI agent in your terminal — a Claude Code-style interactive CLI with a full MCP host, written in Rust.

Model Context Protocol server that gives AI assistants TestRelic context—repos, runs, coverage gaps, test creation, healing, and impact analysis tied to your cloud data.

Run local MCP servers from the CLI so the cloud Ask AI agent can call your tools during a turn, with Claude-Code-compatible .mcp.json config.