MCP Configuration

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

Prerequisites

An Okareo account at app.okareo.com.
An MCP-ready coding agent, or Slack. The hosted endpoint has been tested with Claude Code, Cursor, Claude Desktop, GitHub Copilot (in VS Code 1.101 or later, and in the Copilot CLI), and Slackbot, and works with most agents 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 coding agent does not yet implement MCP OAuth discovery.

Claude Code

Recommended — add it from the CLI:

claude mcp add --transport http okareo https://tools.okareo.com/mcp

Run this from your project root. The --scope flag controls who gets it:

Scope	Flag	Where it lands
This project, just you (default)	(none)	your local Claude Code config
This project, checked in for the team	`--scope project`	`.mcp.json` in the project root
Every project you open	`--scope user`	your user-level Claude Code config

On first use a browser tab opens to Okareo sign-in; after consent the tools appear in the tool list. Check the connection any time with claude mcp list, and remove it with claude mcp remove okareo.

Equivalent .mcp.json, if you would rather write the file yourself or commit it with the repo:

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

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

Cursor reads MCP servers from a JSON file. Use .cursor/mcp.json in the project to scope Okareo to one repo, or ~/.cursor/mcp.json to have it everywhere. Create the file if it does not exist — Cursor does not create it for you.

Recommended (OAuth):

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

Restart Cursor, then reload the workspace. Okareo should appear in Cursor's MCP settings with its tools listed; if the list is empty, the file is in the wrong place or the JSON did not parse.

Fallback (Bearer):

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

GitHub Copilot in VS Code (1.101 or later)

File: .vscode/mcp.json in your project, or your user mcp.json (run MCP: Open User Configuration). VS Code reads servers from a servers key, not mcpServers.

Recommended (OAuth):

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

Start the server from the Command Palette: MCP: List Servers → okareo → Start Server, then sign in to Okareo in your browser. Use Copilot Chat in Agent mode to call the tools.

Fallback (Bearer):

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

GitHub Copilot CLI

Recommended (OAuth):

copilot mcp add --transport http okareo https://tools.okareo.com/mcp

Start copilot. The first time, it opens Okareo's sign-in in your browser. Run /mcp show okareo to see the server and its tools.

Fallback (Bearer):

copilot mcp add --transport http --header 'Authorization: Bearer ${OKAREO_API_KEY}' okareo https://tools.okareo.com/mcp

Set OKAREO_API_KEY in your shell first. The single quotes keep the key itself out of ~/.copilot/mcp-config.json.

To run Okareo's MCP server on your own computer instead, see the local install in the okareo-mcp README.

Copilot Business and Enterprise

An admin must turn on the MCP servers in Copilot policy. If your company limits Copilot to MCP servers from a registry, an admin adds Okareo, listed as com.okareo/okareo.

Slackbot

Slackbot is Slack's built-in AI assistant. Once your workspace has an Okareo app, anyone in it can ask Slackbot about their Okareo projects. Each person signs in with their own Okareo account.

Create the app

Someone who can install apps in your workspace does this once. The app only connects Slackbot to the Okareo MCP server; it asks for no access to channels or messages. Because it belongs to your workspace, Slack allows it without a Slack Marketplace listing.

Go to api.slack.com/apps, click Create New App, and choose From scratch.
Name the app Okareo, pick your workspace, and click Create App.
In the sidebar, under Features, click MCP Servers, then Get Started.
Fill in the form and click Save:
- Name: Okareo
- URL: https://tools.okareo.com/mcp
- Auth Type: Dynamic Client Registration. Leave the optional fields empty.
In the sidebar, click Install App, install the app to your workspace, and click Allow.

Connect

Open Slackbot.
Ask it to connect Okareo, or click Slackbot above the Messages tab, choose Apps, and click Connect next to Okareo.
Sign in to Okareo in your browser. If you belong to more than one organization, pick one.
Try: "List my Okareo projects."

To switch organizations later, disconnect Okareo under Apps → Settings, connect again, and pick the other one.

Good to know

Slackbot works in its own panel. Slackbot in channels is in early pilot at Slack.
Slack keeps each person's Okareo sign-in.

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.

An API key works only in the organization it was made in.

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

On first connect, your agent opens Okareo's login page. If you belong to more than one organization, you pick one. To switch later, disconnect Okareo in your agent, connect again, and pick another.

Network access

Option	Hosts your network must reach
Coding agent	`tools.okareo.com`. For sign-in, also `auth-tools.okareo.com` and your identity provider (for example Google).
Slackbot	Only for sign-in, from each person's browser: `tools.okareo.com`, `auth-tools.okareo.com`, your identity provider, and `oauth2.slack.com`. Slack's servers make the tool calls.
Local version	`api.okareo.com` and `mapi.okareo.com`, plus `pypi.org` and `files.pythonhosted.org` when `uvx` installs the package.

Verifying the Connection

After setup, ask your coding agent to list your Okareo projects to confirm the MCP server is working:

"List my Okareo projects."

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

Prerequisites​

Setup​

Claude Code​

Claude Desktop​

Cursor​

GitHub Copilot in VS Code (1.101 or later)​

GitHub Copilot CLI​

Slackbot​

Create the app​

Connect​

Good to know​

Authentication​

Browser sign-in​

Network access​

Verifying the Connection​

Prerequisites

Setup

Claude Code

Claude Desktop

Cursor

GitHub Copilot in VS Code (1.101 or later)

GitHub Copilot CLI

Slackbot

Create the app

Connect

Good to know

Authentication

Browser sign-in

Network access

Verifying the Connection