The TestRelic MCP server started as a way to give AI coding assistants real testing context — projects, coverage, healing, impact analysis. With 3.1, it grows into a full AI-workflow surface: five new capability sets, a one-click Cursor Marketplace install, and a cleaner tool namespace. It's published as @testrelic/mcp v3.1.2.
Coding assistants are only as good as the context they see. Pasting stack traces into chat scales poorly; re-fetching structured run history from your org is better. The TestRelic MCP server implements the Model Context Protocol so compatible hosts—Cursor, Claude Desktop, VS Code MCP clients, and others—can call tools that read your TestRelic cloud projects, runs, coverage signals, and related data. The MCP overview positions MCP alongside the SDK reporters: reporters write run data from CI and laptops; MCP reads and acts on that data inside the IDE loop.