An MCP server (Model Context Protocol server) lets your AI Agent use tools and data from another system during a call or chat, for example looking up a ticket, checking a calendar, or creating a lead. This guide covers what is the same for every MCP server: connecting one, signing in, choosing which tools the agent may use, and controlling the information the agent is allowed to fill in.
If you are setting up a Zoho MCP server specifically, follow AI Agent | In Call Action | How to Setup and Enable a Zoho MCP Server for the Zoho-side steps, then come back here for tools and overrides.
Security first. Anything you enable, a caller can indirectly trigger. For agents that talk to the public:
Each server's settings panel shows this guidance at the top. Select Got it, don't show again to hide it, or Show MCP security guidance to bring it back.
| Field | What to enter |
|---|---|
| Server name | A name you will recognize, for example "Acme Dental Scheduling". |
| Server URL | The MCP endpoint from your provider, for example https://mcp.example.com/sse. It cannot be changed after you save. |
Once a server exists, its status is shown at the top of its settings panel:
| Status | Meaning |
|---|---|
| Connected | Signed in and ready. |
| Not responding | The connection is not working. Select Test connection to check it. |
| Token expired | The sign-in has expired or was revoked. Select Re-authorize. |
| Not configured | Setup is not finished (for example, sign-in has not been completed). |
| Off | The server is switched off, so the agent does not use it. |
If a server is switched on but cannot be reached, the panel also says Switched on, but not reachable. If the agent seems to ignore a tool, check the status first.
Servers without a card. A server whose integration is no longer offered still works for the agent. It is listed under Other MCP servers below the cards, with its status and a Configure button.
Every MCP server offers a list of tools. Open the server with Configure and select Test connection so its tools are discovered. They appear under Tools found, with a count such as 12 allowed, 1 ask first, 1 off.
Overrides let you control, tool by tool, what the agent decides for itself. This is especially useful to keep the agent inside one calendar, one booking business, or one department.
For a tool that is not Off, its arguments (the pieces of information the tool needs) are listed. For each one, choose how it is handled:
| Option | What it does | Example |
|---|---|---|
| Agent decides | The agent fills this in from the conversation. | The appointment date the caller asks for. |
| Default | A starting value the agent can change. | A default appointment length. |
| Pinned | A fixed value the agent cannot change. A tag such as 1 pinned appears on the tool. | Always use the "Front Desk" calendar. |
| Hidden | The agent never sees this argument. | An internal reference field. |
Select Save server to save.
After setup, place a test call or chat and ask for something that needs the tool. Check the transcript to confirm the tool ran. Add a comfort message if the tool takes a moment (see Comfort Messages).
| Problem | What to try |
|---|---|
| Sign-in window does not open | Allow pop-ups for this site and select Connect again. |
| Agent ignores the integration | Open it with Configure and check that the status is Connected (not Token expired or Off), that the tool is not Off, and that the tool is mentioned in a flow state where the agent can use it (see Building Conversation Flows). |
| Test connection fails | Recheck the Server URL and confirm the provider's service is available. |
| Agent chooses the wrong calendar or account | Open the server with Configure and set the calendar or account argument to Pinned on each tool. |
| A server is missing from the cards | Look under Other MCP servers below the cards. Servers whose integration is no longer offered are listed there. |
| Integration is greyed out or asks you to upgrade | Your plan's integration allowance or license does not include it. See the licensing article below. |