🛠️ How-to guide · Last updated: October 1, 2026

<aside> 🔌

WHAT IT DOES

MCP Connections give your agent new tools from the services you already use — book an appointment in Cal.com, look something up in Notion, check an order in Stripe. Pick a service from the built-in library, sign in once, and the agent can use that service's tools in conversations.

</aside>

When to use it

Use it when a service your team relies on offers an MCP server — a standard way for an AI agent to use another product's tools (MCP stands for Model Context Protocol; see the Glossary). If the system you want to reach only has a regular REST API, use an API Connection instead (see Advanced Configuration).

Before you start

• A role that can edit agents — Editor, Publisher, or Admin (see Roles & Permissions).
• An account with the service you are connecting. Everyone who chats with the agent uses that account's access, so sign in with an account meant for the agent, not your personal one.
• MCP Connections is marked Beta in the app.

Add a server from the library

1. Open the agent, go to Advanced → MCP Connections, and select Add. Open the New MCP card.
2. Search the library — for example, type cal — and pick the service. Zammo fills in the address and runs Check, which confirms the server works and works out how it signs in.
3. If the service uses Provider sign-in, select Connect. The service opens in a new tab — sign in there, approve access, then come back. The Access row turns green.
4. Select Test connection. Zammo connects the way the agent will and lists the tools it gets. No tool is run.
5. Select Save Changes at the bottom of the page.

Adding Cal.com from the library: Advanced → MCP Connections → Add, search for cal, pick Cal.com, select Connect to sign in, then Test connection lists the five tools the agent gets.

Not in the library? Choose Custom URL… and paste the server address your provider gives you — it often ends in /mcp. Check works out the rest.

Choose how it signs in

Check picks the method for you, and you can change it under Sign in → Method:

• Open — for servers anyone can call. Nothing is sent with each request.
• Key or token — for servers that gave you a key. It is sent with every request the agent makes, as Authorization: Bearer <key> unless you change the Header name or Prefix.