Connecting an assistant

Sign in, open your project, and go to AI → MCP in the left sidebar.

Create a key

Click Create key.

Key name. Something that tells you where it will live, like "my laptop" or "team workspace".

Expires after. 30, 90, 180 or 365 days, or never. If you are not sure, 90 days is a sensible default.

Any member of the project can create a key, and the key carries that person's own permissions. See Permissions.

A key belongs to one project. If you work across several projects, create a key in each.

🔑

The key is shown once

Copy it before closing the dialog. It is stored in a form we cannot reverse, so if you lose it you will need to create a new one.

Connect your assistant

The dialog that shows your new key gives you three things to copy. Which one you need depends on your assistant.

Key. The password an assistant uses to reach this project. Some clients ask for the server URL and the key separately.

Custom connector URL. The same key inside a URL. Paste it into any assistant that connects to a remote MCP server by URL.

Add to Claude Code. One command that registers this project with Claude Code on your machine. Run it in your terminal.

Claude, in the browser or desktop app

Copy the custom connector URL, then in Claude go to Settings → Connectors → Add custom connector and paste it in.

ChatGPT

Copy the custom connector URL and add it as a connector in ChatGPT's settings.

Claude Code

Copy the Add to Claude Code command and run it in your terminal, in any directory. Then ask Claude Code about your cookies, scans or usage.

Anything else

Any client that speaks MCP over HTTP works. Point it at the server URL and send the key as a bearer token, or use the connector URL if the client only takes a URL.

⚠️

Treat the connector URL like a password

The key is part of that URL, and the key is the entire login. Anyone who has it can act on your project with the same permissions you have. Keep it in a password manager, and never paste it into a shared document or a public channel.

Check that it worked

Ask the assistant something read only, like "what plan is this project on, and is the domain verified?". If it answers with your real domain and plan, you are connected.

Then head to the setup prompt and let it do the rest.

Managing your keys

The MCP page lists your keys with:

Created and Created by. When it was made, and by whom.

Last used. When an assistant last used it, or Never.

Expires. The expiry date, or Never.

Ends with. The last few characters of the key, so you can tell two keys apart without seeing either in full.

Status. Active, Expired once the expiry date passes, or Revoked.

Owners and Admins see every key on the project. Users see the keys they created.

Revoking a key

Click Revoke on any key. Clients using it stop working straight away.

Revoked keys stay in the list rather than disappearing, so that the cookies they changed keep showing where that change came from. Revoke a key whenever you are done with it, when the device holding it is lost, or when someone leaves your team.

What's next

Send the setup prompt.

See what an assistant can do.