Your own MCP servers
If you run your own MCP server (Model Context Protocol), for example one that sits in front of the apps you built or your own email system, you can connect it to your workspace. Your Chief of Staff then sees that server's tools next to its built-in ones and uses them in chat, in routines, and in skills.
This is the opposite direction from connecting Claude or ChatGPT to your Brain. That page lets another AI read your Brain. This page lets your Chief of Staff call your server.
If the Your own MCP servers section isn't on your Integrations page, it isn't turned on for your workspace yet.
Add a server
- Open Integrations and scroll to Your own MCP servers.
- Click Add MCP server.
- Give it a name you'll recognise, like "My apps". Your Chief of Staff uses this name when it talks about the server.
- Paste the server's https address. This is the MCP endpoint itself, which often ends in
/mcp. - If the server needs a key, paste it under Key or token. A token on its own is sent as
Authorization: Bearer <token>. If your server expects a different header, such asX-API-Key, type that name under Header name. - Click Connect.
We connect to the server and list its tools before saving anything, so a wrong address or key shows an error right away instead of failing later in a chat. When it works, you'll see how many tools it offers.
The address and key are stored encrypted. Nobody in the workspace can see them again, including you. To change either one, remove the server and add it again.
Use it
Ask in plain words, the way you would for any other integration: "check my bookkeeping app for unpaid invoices" or "send that summary from my own email system". Your Chief of Staff picks the right tool from your server.
Every member of the workspace can use a server once it's added, and so can routines that run in the workspace.
What's supported
- Servers that speak MCP over Streamable HTTP at an https address.
- No key, or one header with a key or token.
- Up to 5 servers per workspace. Each server can offer up to 25 tools to your Chief of Staff; if yours has more, the first 25 it lists are used.
Not supported yet:
- Servers that make you sign in through a browser (OAuth). Use a server or gateway that accepts an API key or token instead.
- Servers on a private network or
localhost. The server must be reachable from the internet. - Older servers that only speak the SSE transport.
If something goes wrong
- "The server refused the key": check the header name and the key, then try again.
- "Answered, but not as an MCP server": check you pasted the MCP endpoint, not the app's home page.
- The server shows a warning on the Integrations page: it refused the saved key during a chat, so your Chief of Staff stopped using it. Remove it and add it again with a working key.
- Your Chief of Staff says the server didn't respond: it waits a few seconds for each server at the start of every message. If yours is slow to wake up, try the message again.
Tool calls to your server don't cost extra credits. Each message is charged as usual.