Skip to main content

Connecting apps over MCP

CONNOR has an MCP server. Connect the agent or editor you already work in, and it can use CONNOR for you: chat, memory, runs and grades, and your credit balance.

Clients you can connect​

The MCP page in CONNOR has a tile for each of these, with its own setup steps:

  • Claude Code
  • Claude Desktop
  • Cursor
  • VS Code with GitHub Copilot
  • Codex and ChatGPT
  • Gemini CLI
  • Windsurf
  • Any MCP client: CONNOR’s server uses streamable HTTP
tip

For the exact settings and lines to copy, open MCP in CONNOR and choose your client. This article explains the steps in words.

Connect a client​

Each one takes about a minute.

  1. Add CONNOR to your client. Open MCP in CONNOR and choose your client’s tile. Copy the setup it shows into your client. Or, instead, copy the prompt from the page and paste it into your agent. The prompt asks your agent to add CONNOR and open the Allow page. It tells your agent never to ask you for API keys or passwords.
  2. Allow access. Your client opens CONNOR’s Allow page in your browser. See below.
  3. Test the connection. Ask your client something that uses CONNOR, such as “What’s my CONNOR credit?”. The MCP page ticks this off when the call reaches CONNOR.

CONNOR asks for a recent sign-in before it connects an app. If it asks you to sign in again, do that and carry on.

Clients without a browser​

Some clients can’t open a browser to sign in. Give them an MCP key instead. Create one in API keys and choose basic or full access there. See API keys.

The Allow page​

The Allow page shows the name the app gives itself, where it sends you back to, and when the request expires.

warning

Only allow apps you set up yourself. The name is the app’s own; CONNOR can’t check it.

Choose what the app can do, then choose Allow basic access or Allow full access. Or choose Deny. You can revoke it at any time in Connected apps.

  • Basic (recommended): run evals of your agents and read the results. It can plan, start, follow, read and cancel evals, browse XORCISE’s missions, see your agents and devices and set an agent’s model, read your usage and balance, see your projects and create new ones, see your API keys’ names (never create, reveal or revoke them), and give you a link to add credit in CONNOR.
  • Full: everything in Basic, plus your chats and memory. It can read your chat history, start and continue chats with CONNOR for you, and read, add to and forget what CONNOR remembers about you.

A connected app can never buy credit or see your card, create or revoke API keys, or delete your account. Those stay in CONNOR.

What connected apps cost​

What a connected app does is charged to your credit, and shows in Usage. An eval it starts that would hold more than a set amount (A$10 today) waits for your approval. You’ll find it on the Connected apps page under Waiting for your approval. Choose Approve or Decline. An approval request expires if you don’t answer it.

Manage and revoke connected apps​

The Connected apps page lists every app you’ve allowed, with its access level, when it was last used, and what it spent this month.

To stop an app using CONNOR, choose Revoke. Its next call to CONNOR fails, and it can’t refresh its access. To use it again, connect it again and choose Allow. If the app used an MCP key, the key stays until you revoke it in API keys.

Sign out everywhere (in Account) also revokes every connected app.