Skip to main content
The Comp AI MCP Connector is our hosted MCP server at mcp.trycomp.ai. You connect an AI assistant — Claude, Cursor, ChatGPT, VS Code — by pasting one URL and signing in. There is nothing to install and no API key to manage: access is granted through OAuth, scoped to your own Comp AI permissions, and revocable at any time.
This is the recommended way to connect. If you’d rather run the server yourself from an API key (for a script, a CI job, or a client that can’t use a remote connector), see MCP Server — the self-managed option.

​
Why the connector

Nothing to install

No npm package, no config file. Paste a URL; the assistant handles the rest.

Sign in, don't copy a key

OAuth in your browser. No API key to generate, paste, or rotate.

Your own permissions

The connection can only do what your Comp AI role can do — per user, not a shared key.

Revoke in one click

Turn off a connection from Settings whenever you want; it stops working immediately.

​
The one thing you need

Paste that into any client’s custom / remote MCP connector setup. Everything else — discovery, sign-in, approval — happens automatically.
The assistant connects to mcp.trycomp.ai from the vendor’s cloud (this is true even for desktop apps), so nothing runs on your machine and the server must simply be reachable over the internet — which it is.

​
Connect your assistant

Custom connectors work on Free, Pro, Max, Team, and Enterprise plans.
1

Open connector settings

Go to Customize → Connectors.
2

Add a custom connector

Click “+” → Add custom connector, then enter:
  • Name: Comp AI
  • URL: https://mcp.trycomp.ai/mcp
Click Add. Leave Advanced settings empty — no client ID or secret is needed.
3

Sign in

Follow the sign-in and approval screen (see What approval looks like).
4

Enable it in a chat

In a conversation, click the “+” button, choose Connectors, and enable Comp AI.
On Team / Enterprise, an organization Owner adds it once under Organization settings → Connectors → Add → Custom → Web; members then Connect it from Customize → Connectors.

​
What approval looks like

The first time you connect, you’ll see an approval screen. It’s built to make one thing obvious: where your access is going.
  • The destination host is shown large — for the real connector it reads mcp.trycomp.ai. This is the field that matters; an app’s name is chosen by whoever registered it, so the host is what to check.
  • Choose your organization. If you belong to more than one, pick which one the connection acts on. (You can change it later in Settings.)
  • Tick to acknowledge, then Allow access. The grant matches your own permissions — there is no read-only mode.
You may see “Comp AI has not reviewed this app.” That’s expected for connectors we haven’t formally vetted, and it isn’t a failure — only continue if you started the connection yourself.

​
Manage or disconnect

Open Settings → your profile → Connected apps. Each connected assistant is listed with the host it sends tokens to and a Revoke button. Revoking deletes the grant and its tokens, so that assistant stops working immediately — reconnect from the assistant to use it again.

​
Connector vs. self-managed

MCP Connector (this page)

Hosted by Comp AI. One URL, OAuth sign-in, per-user permissions, revoke in Settings. Best for people using an AI assistant day to day.

MCP Server (self-managed)

You run it from a Comp AI API key via npx. Best for scripts, CI, or clients that can’t use a remote connector.

​
Resources