POST https://mcp.runagain.ai/mcp (Streamable HTTP, JSON-RPC 2.0). It’s also shown,
with copy-paste config, under project Settings → Connect via MCP.
Connect with OAuth (recommended)
OAuth is the preferred flow for IDE/agent clients that can open a browser. There’s no secret to copy — the client opens this workspace in your browser, you approve and pick a project, and the token is captured by the client’s local callback.1
Add the server in your client
Point your MCP client at the endpoint above. Clients that support OAuth discover the flow
automatically via
/.well-known/oauth-protected-resource.2
Approve in the browser
Your client opens RunAgain, you sign in (if needed), choose which workspace to grant, and
approve. The client’s loopback callback captures the token.
Tokens issued via OAuth don’t show up in the API-keys list in Settings — revoke access from
your client’s settings. Access is scoped to the single project you approved.
Connect with an API key
For clients that can’t do OAuth, generate a dedicated read-only MCP key under Settings → Connect via MCP → API key (or the API-keys section). It’s a separate credential from your ingest (write) key — ansk_mcp_… key works for MCP but can’t send traces, and an
ingest key can’t query MCP. The key is shown once at creation.
Tools
Read tools (safe, read-only):- Traces —
list_traces,get_trace,get_trace_io,compare_traces,traces_with_tool_errors - Agents —
previous_agent_run,agent_run_series,agent_run_count - Scores & health —
get_trace_scores,list_run_issues,get_baseline_config - Datasets / experiments / annotations —
list_datasets,list_dataset_items,list_experiments,get_experiment_results,list_annotation_queues,list_queue_items - Drift & overview —
list_drift_monitors,get_drift_series,overview_stats
run_experiment,run_online_scoring,run_drift,run_baselines,run_health