AI Agent | In Call Action | Connecting MCP Servers, Choosing Tools and Setting Tool Overrides

AI Agent | In Call Action | Connecting MCP Servers, Choosing Tools and Setting Tool Overrides

MCP Servers

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.

Two Ways to Connect an MCP Server

  • Ready-made integrations. Popular services (calendars, booking tools, CRMs and so on) each have their own card on the Actions tab. You connect them, sign in, and choose tools.
  • Custom server. If your service offers an MCP address (URL) that has no card of its own, add it with the Custom Server card.

Before You Begin

  • You can open the agent in the AI Agent module.
  • Your agent's plan includes integrations. If you see Your current license does not include this integration. Upgrade your plan to enable it., see Licenses, Plans, Trial Minutes and Upgrading.
  • For a custom server, you need the server URL from your provider. Custom servers connect without authentication, so the server must not need an API key or a sign-in.
  • For a ready-made integration that uses sign-in, you need an account on the other system with permission to authorize the connection.

Security first. Anything you enable, a caller can indirectly trigger. For agents that talk to the public:

  • Do not expose sensitive customer or staff data.
  • Be careful with tools that create, update or change records, and consider read-only access.
  • Never enable tools that delete information.
  • Enable only the tools the agent really needs.
  • Use a dedicated service account with limited permissions where the provider allows it.

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.

Find MCP Integrations on the Actions Tab

  1. Open the agent in the AI Agent module and go to the Actions tab.

  2. MCP integrations carry the MCP tag. Select the MCP filter above the cards to show only those.

  3. Each MCP card has one button at the bottom right:
    • Connect when the integration is not connected yet.
    • Configure when it is connected.
    One click opens that server's settings panel.

Add a Custom MCP Server

  1. On the Custom Server card, select Connect. A panel titled Custom Server opens.

  2. Fill in the two fields:
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.
  1. Select Create server.
  2. Select Test connection to check that the server answers and to discover the tools it offers.

Connect a Ready-made Integration

  1. On the integration's card (for example Google Calendar), select Connect. The integration's settings panel opens.

  2. For an integration that uses sign-in, select Connect at the bottom of the panel. A sign-in window opens. If it does not, your browser blocked it: allow pop-ups for this site and try again.

  3. Sign in to the other system, review the permissions requested, and approve them. If you have more than one workspace or instance, pick the one the agent should use.
  4. When the window closes, the panel confirms the integration is authorized and shows Test connection. The card now reads In use and its button changes to Configure. If the sign-in later expires, open the card with Configure and select Re-authorize.

Understanding the Status

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.

Choose Which Tools the Agent Can Use

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.

  • Each tool has a setting: Allow (the default) lets the agent use it, Ask has the agent ask the caller before using it, and Off stops the agent from using it.
  • Set all changes every tool at once. For example, set all to Off, then allow only the tools you need.
  • Allow on SMS lets the agent use this server's tools in text message conversations. Servers that act as a signed-in user never run over SMS.

Tool Overrides (Pin, Default or Hide Information)

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.


For pinned and default values, where the system can list the choices (for example your calendars), select Fetch to load them and pick from the list.

Select Save server to save.

Test and Maintain the Connection

  • Configure on the card (or under Other MCP servers) opens the server to change its tools, overrides and settings.
  • Test connection checks that the server answers and discovers its tools. If it fails, the server's own error message is shown.
  • Remove server, at the bottom of the server's panel, removes the server and its configuration. You are asked to confirm, and the agent loses every tool the server provided.

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).

Troubleshooting

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.
  • AI Agent | In Call Action | How to Setup and Enable a Zoho MCP Server
  • Building Conversation Flows
  • Comfort Messages
  • Setup AI Agent
  • Licenses, Plans, Trial Minutes and Upgrading