Okareo

Okareo MCP Server

The Okareo MCP server exposes Okareo's evaluation capabilities as MCP tools, allowing AI coding assistants to create and manage scenarios, register models, run evaluations, and execute multi-turn simulations directly from your editor.

For detailed documentation, see the Okareo MCP docs.

Prerequisites

• An Okareo account at app.okareo.com
• A copilot that supports MCP servers (Claude Code, Cursor, VS Code, or GitHub Copilot), or Slackbot in Slack
• Python 3.10–3.12 (only for the local install modes; not needed for remote)

---

Remote MCP (hosted) — recommended

The fastest way to get started. No local install, no Python, no API key in .mcp.json. Browser sign-in handles auth on first connect.

Recommended (OAuth — Claude Code, Claude Desktop, Cursor, VS Code 1.101+)

Add to your copilot's MCP config (typically .mcp.json):

{

"mcpServers": { "okareo": { "type": "http", "url": "https://tools.okareo.com/mcp" } } }

Reload the copilot. It will open a browser to Okareo sign-in once; thereafter the copilot stores the token itself. Your .mcp.json contains no secrets.

Fallback (Bearer header — older clients or headless / CI)

For clients that haven't shipped the MCP OAuth flow yet, paste your API key as a bearer header. Prefer the env-var form over an inline literal:

{

"mcpServers": { "okareo": { "type": "http", "url": "https://tools.okareo.com/mcp", "headers": { "Authorization": "Bearer ${env:OKAREO_API_KEY}" } } } }

GitHub Copilot (in VS Code and the Copilot CLI), Slackbot and every other client are set up at docs.okareo.com/mcp/configuration.

Working across multiple Okareo organizations

If you have access to more than one Okareo account, simply Clear Authentication and then re-authenticate with the account you want to work in. You can always ask which account your are in and have acccess to.

---

Local install (alternative)

Run the MCP server on your own machine. Useful for offline / airgapped environments and for development.

Prefer the [Remote MCP](#remote-mcp-hosted--recommended) section above unless you have a specific reason to install locally (airgapped, custom build, development on this repo). The remote endpoint requires no install and stays current automatically.

For multi-org users, the remote endpoint also exposes tenant management tools (list_tenants, switch_tenant).

Step 1: Set Your API Key

export OKAREO_API_KEY="your-api-key"

Add this to your ~/.zshrc or ~/.bash_profile for persistence.

Step 2: Configure Your Copilot

Claude Code

Add to .mcp.json:

{

"mcpServers": { "okareo": { "command": "uvx", "args": ["okareo-mcp"], "env": { "OKAREO_API_KEY": "${OKAREO_API_KEY}" } } } }

No pre-install needed — uvx handles it automatically.

Cursor

Add to .cursor/mcp.json:

{

"mcpServers": { "okareo": { "command": "uvx", "args": ["okareo-mcp"] } } }

Cursor inherits OKAREO_API_KEY from your shell environment.

Alternative: pip install

If you don't have uv installed:

pip install okareo-mcp

Then use "command": "okareo-mcp" instead of "command": "uvx" with "args": ["okareo-mcp"].

---

Configuration Reference

---

Available Tools

Scenarios

Generation Models

Tests & Checks

Simulations (Multi-Turn)

Voice Monitoring

Projects

Okareo has no project delete — in the app, the API, or here. Archiving is

the removal, and it only hides the project from the picker: its scenarios,

runs, and dashboards stay intact and every tool still works against it.

Analytics & Dashboards

Tenant Management (remote MCP only)

Documentation & Templates

---

Troubleshooting

---

Contributing

This repository is a curated public mirror; the canonical source is maintained by Okareo. We welcome issues and consider community pull requests — see CONTRIBUTING.md for how proposed changes are reviewed and ported.

License & Trademarks

The Okareo MCP server source code is licensed under the Apache License 2.0 (see also NOTICE).

"Okareo", the Okareo logo, and Okareo product names are trademarks of Okareo, Inc. and are not covered by the Apache 2.0 license. See TRADEMARK.md for permitted use.