MCP servers
Connect Claude Code, Cursor, VS Code, the Claude API or any MCP client to the Ostra MCP server from the TestRelic Console, choose which tools to expose, and monitor clients and tool calls.
MCP servers (console.testrelic.ai/mcp-servers) connects AI agents to the Ostra models. The Ostra MCP server is remote: there's nothing to install, only a URL and a key.
The server
The strip at the top shows:
| Name | ostra, Remote |
| Status | Healthy or Degraded (Ostra Decision can't be reached right now) |
| URL | https://ostra.testrelic.ai/mcp (Copy URL) |
| Transport | Streamable HTTP |
| Auth | API key (Bearer) |
| Protocol | 2025-06-18 (2025-03-26 also accepted) |
Test connection runs initialize, tools/list and a model check against the server. It's free: "Free check: no tool is called and nothing is billed."
Connect a client
Until a client has connected, the setup steps show on the page under Connect your first client; afterwards, open them with Set up a client.
Get an API key with full access. Create a key for MCP makes a full-access key named mcp-<client>, following your workspace's key policy, and puts it straight into the command. "Read-only keys can list tools but not call them."
Pick your client: Claude Code, Cursor, VS Code, Claude API or Other.
Add the config the page shows for that client. For Claude Code, choose macOS / Linux or Windows PowerShell and run the one-line command. The exact configs for every client are in MCP server.
"The client appears under Clients within a minute."
Connect the Ostra MCP server to this coding agent.
- URL: https://ostra.testrelic.ai/mcp (Streamable HTTP)
- Auth header: Authorization: Bearer <key>, with the key read from the OSTRA_API_KEY environment variable (never paste it into a committed file).
- Server name: ostra
Then list its tools and call ostra_list_models to confirm it works. Report the tool names.Troubleshooting
- "Dynamic Client Registration" or "needs authentication" in Claude Code: the header didn't reach the client, usually because the command was split across lines. Run
claude mcp remove ostra, then the one-line command again. - Empty replies or dropped connections: antivirus HTTPS scanning can break streamed responses. Exclude
ostra.testrelic.aifrom HTTPS scanning.
Overview tab
- Tool calls · 7d, Active clients · 24h, MCP spend · 7d and Tools exposed.
- Recent tool calls: time, tool, client, key, result, latency, cost and request ID. Filter by field (Tool, Client, Key, Request ID), result (All results, Success, Errors), client, and date (Today, Yesterday, Last 7 days, Last 14 days, Last 30 days or a custom range). All MCP logs opens Logs filtered to MCP.
Tools tab
| Tool | Card | Price |
|---|---|---|
ostra_triage_failure | Triage failure | $0.50 / 1M failures in · $0.00 out |
ostra_select_impacted_tests | Select impacted tests | $2.00 / 1M diffs in · $0.00 out |
ostra_check_selector | Check selector | $0.25 / 1M selectors in · $0.00 out |
ostra_pro_chat | Ask Ostra Pro | Per token |
ostra_list_models | List models | Free |
Each card has an Expose <tool> switch (owners, admins, developers). A tool you turn off disappears from tools/list for every client in the workspace, and calls to it fail with permission_error; the same model stays available over REST. Details shows the tool's description and an example tools/call.
Clients tab
Every client that has connected: name and version, the key it used, first and last seen, number of tool calls, and the last tool it called. Empty until the first connection: "No MCP clients yet".
Billing and limits
"MCP calls are billed and rate-limited exactly like REST": the same prices, the same per-workspace requests-per-minute limit, and the same balance and spend limits. Listing tools and ostra_list_models are free. See Rate limits and Billing and credits.
For how to use the tools from an agent day to day, see Ostra in your coding agent.
Playground
Try Ostra Pro and Ostra Decision in the TestRelic Console — chat, presets, thinking, tools, attachments, Compare, history, model status, and copying the request as code.
Usage & logs
Track Ostra requests, tokens, cache hits and spend by model, task, channel and key on the Usage page, export it as CSV, and inspect individual requests on the Logs page.