Model Context Protocol · Live
Okareo in your editor.
Connect Claude Code, Cursor, or your editor to the hosted Okareo MCP. Run simulations, author checks, and evaluate voice and text agents — in natural language, without leaving the agent loop. Nothing to install, nothing to run locally.
Point your editor at the URL, sign in through your browser once, and the tools appear in the picker.
{
"mcpServers": {
"okareo": {
"type": "http",
"url": "https://tools.okareo.com/mcp"
}
}
}Connect
Install. Just point and sign in.
The Okareo MCP is hosted at tools.okareo.com/mcp. Three steps, no local runtime.
Point your editor
Add the config above to your client. The endpoint speaks streamable-HTTP — no install, no process to keep running.
Sign in once
Browser sign-in opens on first tool use. Your copilot stores the token. No secrets in your config.
Just ask
Ask your copilot "List my Okareo scenarios." If it answers, you're connected.
Per-editor config
Where the config goes.
Same JSON, different file. Reload the client after editing.
Claude Code
.mcp.json (project) · ~/.claude.json (global)
{
"mcpServers": {
"okareo": {
"type": "http",
"url": "https://tools.okareo.com/mcp"
}
}
}Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.json · %APPDATA%\Claude\claude_desktop_config.json
Use the same JSON, then restart the application.
Cursor
~/.cursor/mcp.json (global) · .cursor/mcp.json (workspace)
Same JSON. Restart Cursor and reload the workspace.
VS Code (1.101+)
~/.config/Code/User/mcp.json · .vscode/mcp.json (workspace)
Same JSON. Reload the window.
Auth
Two ways to sign in.
OAuth — browser sign-in
Browser sign-in happens automatically on first use. The copilot stores the token thereafter. No API key in your config.
Bearer API key
For headless or CI clients without OAuth, set an Authorization: Bearer <okareo-api-key> header. Get the key from app.okareo.com under Profile → API Keys.
In the agent loop
What the tools do.
The full Okareo evaluation surface, callable in natural language.
Build test data
Save, version, and manage scenarios of input/result rows straight from your project.
Run synthetic users
Drivers run multi-turn voice and text conversations against your Target — dozens in parallel.
Find edges, not just bugs
Author judge, code, and audio checks; run tests and re-score completed runs.
Register & evaluate
Browse the LLM registry, register generation models, and run them against scenarios.
Monitor production
Ingest live conversations and wire Retell, Twilio, VAPI, or ElevenLabs into monitoring.
Query the trend
Pull evaluation analytics and manage dashboards without leaving the editor.
Common questions
What teams ask before they install.
Do I need to install anything?+
No. The remote endpoint at tools.okareo.com/mcp speaks streamable-HTTP — point your editor at the URL and sign in. A local stdio install (uvx okareo-mcp) is also available for offline or airgapped use.
What data leaves my repo?+
Only the arguments your copilot passes to a tool call — the scenario rows, prompts, or names you ask it to send. The MCP is stateless; your Okareo project on the backend is the source of truth.
Which editors are supported?+
Any MCP client that supports streamable-HTTP: Claude Code, Claude Desktop, Cursor, and VS Code (1.101+) are documented above. Others that speak the protocol work the same way.
How do I verify it's connected?+
Ask your copilot "List my Okareo scenarios." A successful connection returns your existing scenarios. If you see an auth prompt instead, complete the browser sign-in.
What if my client doesn't support OAuth?+
Use the Bearer fallback: set an Authorization: Bearer <okareo-api-key> header with a key from app.okareo.com (Profile → API Keys).
Get started
Wire Okareo into your editor.
Point your client at tools.okareo.com/mcp, sign in once, and start evaluating.