Skip to main content

MCP Configuration

The Okareo MCP server is hosted at https://tools.okareo.com/mcp. You connect your AI copilot to it directly — no install, no Python, no container. Sign-in happens through your browser on first connect; the copilot stores the OAuth token from then on.

Prerequisites​

  • An Okareo account at app.okareo.com.
  • An MCP-ready editor. The hosted endpoint has been tested with Claude Code, Claude Desktop, Cursor, and VS Code (1.101 or later), and works with most copilots that implement the MCP streamable-HTTP transport.

Setup​

Each section below shows the recommended OAuth configuration first and the Bearer-token fallback second. Use the fallback only if your copilot does not yet implement MCP OAuth discovery.

Claude Code​

File: .mcp.json in your project root (or ~/.claude.json for a global config).

Recommended (OAuth):

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

Reload Claude Code. A browser tab opens to Okareo sign-in on first connect; after consent, the tools appear in the tool list.

Fallback (Bearer):

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

Set OKAREO_API_KEY in your shell environment. Prefer the env-var form over an inline literal.

Claude Desktop​

File: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows).

Recommended (OAuth):

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

Restart Claude Desktop. Sign-in is browser-based.

Cursor​

File: ~/.cursor/mcp.json (global) or .cursor/mcp.json (workspace).

Recommended (OAuth):

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

Restart Cursor and reload the workspace.

Fallback (Bearer):

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

VS Code (1.101 or later)​

File: ~/.config/Code/User/mcp.json (Linux/macOS) or per-workspace .vscode/mcp.json.

Recommended (OAuth):

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

Reload the window. The first tool invocation kicks off the OAuth flow.

Fallback (Bearer):

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

Authentication​

The hosted endpoint supports two auth paths:

  • OAuth (recommended). Browser sign-in to Okareo on first connect.
  • Bearer fallback. Set the Authorization: Bearer <OKAREO_API_KEY> header.

Get an Okareo API token from app.okareo.com under Profile → API Keys, or see the API Token reference.

Provider Keys for Models Under Test​

Provider API keys (OpenAI, Anthropic, Cohere, etc.) are managed inside Okareo. Use list_available_llms from your copilot to see which LLMs your organization has configured, and register_generation_model to wire one up as a Model Under Test. There is no need to set provider keys as local environment variables.

Verifying the Connection​

After setup, ask your copilot to list your Okareo scenarios to confirm the MCP server is working:

"List my Okareo scenarios."

If the server is configured correctly, you'll see your existing scenarios. If not, check the Troubleshooting section in the MCP reference.