Connect / MCP

Give Claude or Codex access to your Reliability Studio evidence.

The hosted MCP endpoint exposes authenticated discovery and evidence tools for the caller's workspace. Use OAuth when available or a narrowly scoped Studio API key stored outside the repository.

Before you connect

Use the identity and scope you intend.

01
Choose workspace
Sign in to Studio and confirm the workspace whose evidence the agent should access.
02
Choose auth
Prefer browser-based OAuth. For automation, create a dedicated API key with only the required scopes.
03
Connect
Add the streamable HTTP endpoint to the client you use.
04
Verify
List the server and ask the client to enumerate available tools before attempting a write.

OpenAI Codex

Store the bearer token in an environment variable.

Codex CLI, the IDE extension, and the desktop app share the same MCP configuration. The CLI writes the server definition while reading the token from ISO_OBS_API_KEY at runtime.

terminalShell

export ISO_OBS_API_KEY="iso_..."

codex mcp add iso-obs \
  --url https://api.iso-obs.com/mcp/ \
  --bearer-token-env-var ISO_OBS_API_KEY

codex mcp list

Claude Code

Connect with OAuth or a local API-key configuration.

The OAuth flow keeps the credential out of the command and lets the hosted authorization server manage sign-in.

terminal / preferredShell

claude mcp add --transport http --scope user \
  iso-obs https://api.iso-obs.com/mcp/

# In Claude Code, open the MCP menu and complete sign-in:
/mcp

Use the API-key alternative only when OAuth is unavailable. Local scope keeps the configuration private to the current project.

terminal / API-key alternativeShell

# API-key alternative. Keep the key out of .mcp.json and source control.
export ISO_OBS_API_KEY="iso_..."

claude mcp add --transport http --scope local \
  --header "Authorization: Bearer $ISO_OBS_API_KEY" \
  iso-obs https://api.iso-obs.com/mcp/

claude mcp get iso-obs

DO NOT COMMIT CREDENTIALS

Never place an iso_... key directly in a shared .mcp.json, .codex/config.toml, example, issue, or screenshot. Revoke exposed keys immediately in Studio Settings.

Verification

Start read-only and confirm the workspace.

Ask the client to list the Iso MCP tools and read a known discovery manifest before submitting anything. If authentication fails, confirm the endpoint ends in /mcp/, the key is active, and its workspace and scopes match the intended action.