Connect a client

There are two ways to authenticate, and every client below supports at least one:

• Sign in (OAuth). The client only needs the URL. It opens Oleon in your browser, you press Connect, and it receives a credential. Use this whenever your client offers it.
• Connector token. You create a token in Oleon and paste it into the client's configuration as a header. Use this for clients without OAuth support, and for scripts.

Both are described in Authentication. The server URL is the same either way:

https://api.olee.ai/mcp

Claude

Works in claude.ai and Claude Desktop, which share their connectors.

1. Add a custom connector

   Open Settings, then Connectors, and choose Add custom connector.

2. Enter the server

   Name it Oleon and set the URL to https://api.olee.ai/mcp. Leave the OAuth client ID and secret empty: the server registers Claude automatically.

3. Connect

   Press Connect. Claude opens Oleon in your browser. Sign in if asked, check the account shown, and press Connect again to approve.

4. Turn it on in a chat

   In a conversation, open the tools menu and make sure Oleon is enabled.

Claude Code

claude mcp add --transport http oleon https://api.olee.ai/mcp

claude mcp add --transport http oleon https://api.olee.ai/mcp \
  --header "Authorization: Bearer mcp_sk_your_token"

If you added the server without a token, start Claude Code, run /mcp, select oleon and choose Authenticate. Add --scope user to make the server available in every project on your machine rather than only the current one.

Cursor

Add the server to ~/.cursor/mcp.json for every workspace, or to .cursor/mcp.json in one project.

{
  "mcpServers": {
    "oleon": {
      "url": "https://api.olee.ai/mcp"
    }
  }
}

{
  "mcpServers": {
    "oleon": {
      "url": "https://api.olee.ai/mcp",
      "headers": {
        "Authorization": "Bearer mcp_sk_your_token"
      }
    }
  }
}

Then open Cursor Settings, then MCP. With the sign-in configuration, press Connect beside oleon to approve it in the browser.

Windsurf

Add the server to ~/.codeium/windsurf/mcp_config.json, then refresh the MCP servers list in Cascade.

{
  "mcpServers": {
    "oleon": {
      "serverUrl": "https://api.olee.ai/mcp",
      "headers": {
        "Authorization": "Bearer mcp_sk_your_token"
      }
    }
  }
}

VS Code

Add the server to .vscode/mcp.json in your workspace, or run MCP: Add Server from the command palette. It is available to GitHub Copilot in agent mode.

{
  "servers": {
    "oleon": {
      "type": "http",
      "url": "https://api.olee.ai/mcp"
    }
  }
}

{
  "inputs": [
    {
      "type": "promptString",
      "id": "oleon-token",
      "description": "Oleon connector token",
      "password": true
    }
  ],
  "servers": {
    "oleon": {
      "type": "http",
      "url": "https://api.olee.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${input:oleon-token}"
      }
    }
  }
}

The token version asks for the token once and stores it securely, so it never sits in a file you might commit.

Other clients

Most clients that support remote servers accept this shape. It is also what Oleon shows you when you create a connector token:

{
  "mcpServers": {
    "oleon": {
      "type": "http",
      "url": "https://api.olee.ai/mcp",
      "headers": {
        "Authorization": "Bearer mcp_sk_your_token"
      }
    }
  }
}

A client that can only start local servers can use mcp-remote as a bridge. It runs on your machine, speaks to the client locally and to Oleon over HTTP, and handles the browser sign-in itself:

{
  "mcpServers": {
    "oleon": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.olee.ai/mcp"]
    }
  }
}

Building your own client? The protocol reference covers discovery, registration and the token exchange.

Check the connection

Ask your assistant:

Use Oleon to tell me who I am signed in as.

It should call whoami and answer with your email and the projects you can reach. If it cannot, see Errors and troubleshooting.