MCP

The Inspect MCP server is available at https://your-org.inspect.com/mcp. It authenticates with a user API key sent as a bearer token. The examples below read the key from the INSPECT_API_KEY environment variable.

Connect the serverCopy Anchor Link

CodexCopy Anchor Link

Add this server to ~/.codex/config.toml.

[mcp_servers.inspect]enabled = trueurl = "https://your-org.inspect.com/mcp"bearer_token_env_var = "INSPECT_API_KEY"

Claude CodeCopy Anchor Link

Run this command in your terminal to add Inspect for your user.

claude mcp add inspect \  --scope user \  --transport http https://your-org.inspect.com/mcp \  --header "Authorization: Bearer $INSPECT_API_KEY"

OpenCodeCopy Anchor Link

Add this remote server to the mcp section of opencode.json or opencode.jsonc.

"inspect": {  "type": "remote",  "url": "https://your-org.inspect.com/mcp",  "enabled": true,  "oauth": false,  "headers": {    "Authorization": "Bearer {env:INSPECT_API_KEY}"  }}

Other clientsCopy Anchor Link

Use the server URL with bearer-token authentication in any HTTP MCP client.

Authorization: Bearer $INSPECT_API_KEY

The available tools let clients launch sessions, read related work, and send focused follow-ups.

Choose the right sessionCopy Anchor Link

Create a session for new independent work. Continue an existing related session when you need its repository state and conversation context rather than starting over.

Keep requests focusedCopy Anchor Link

Pass a clear objective and the minimum context needed to act. Use attached files for large structured inputs instead of copying them into prompts.