Your own MCP servers
Add private MCP servers that only your agents can use, with headers or OAuth.
You can connect your own MCP servers — a personal automation, a Zapier endpoint, a self-hosted tool — without waiting for an admin. These servers are private to you: only agents acting on your behalf can use them.
Find them under Settings → My MCP servers.
Adding a server
- Click Add server.
- Fill in a display name, a URL, and an optional description. A short slug is suggested automatically (you can edit it).
- Choose how the server authenticates:
- Headers — paste static headers (an API key or bearer token). Good for servers with a secret in a header, or a secret already baked into the URL.
- OAuth — enter the client details and connect with a sign-in flow, the same way you connect Google.
- Save.
Headers
Add one row per header (name + value). They're sent with every request to your server and stored encrypted.
OAuth
Enter the client ID, client secret, authorization URL, token URL, and scopes your provider gave you. You can also add companion headers that go alongside the token (for example Notion's version header), and under Advanced, change where the token is placed or set an audience.
After saving, click Connect on the server's row to sign in. A green Connected badge means your agents can use it. Reconnect needed means you should sign in again.
Managing servers
- Enable / Disable — turn a server off without deleting it.
- Edit — change any detail. For OAuth, leave the client secret blank to keep the current one.
- Delete — removes the server and any stored credentials for good.
Renaming a slug: if you rename a server's slug, the old name is held for 24 hours before it can be reused, so anything still referring to the old name doesn't accidentally point at a different server.
Privacy
Your servers and their credentials are visible only to you. Admins and other members can't see or use them.