# AI Connectors

> Connect your apps and MCP servers to your AI agents, so your AI receptionist and Allo AI can look things up and act in them.

Connect your apps and MCP servers to your AI agents. MCP (Model Context Protocol) is the open standard that lets AI agents use other software. Connect an app or MCP server once for the whole workspace, choose which of its tools the AI may use, then turn it on for each AI receptionist. During a call, your agent can then check an order, find a customer, or update a record without a teammate stepping in.

**Available on:** web and desktop. Included in every plan. Agents need the [AI receptionist add-on](/help/billing/add-ons) to use connectors during calls.

<Note>
  This page is about bringing your apps into Allo. To use Allo from Claude or ChatGPT, see [MCP Server](/help/integrations/mcp).
</Note>

## What your agents can do during calls

Once a connector is on for an agent, your AI receptionist can use its tools while it talks to a caller or answers a text. It can look up a customer, check the status of an order or a ticket, or create and update a record, depending on the tools you turned on. The agent only uses the tools you allowed, and a read-only tool never changes your data.

After the call, the call's record shows each connector the agent used. To choose the connectors and tools for each agent, see [let your AI receptionist use your apps](/help/features/ai-receptionist-connectors).

## Who can set up AI Connectors

The workspace owner and admins manage AI Connectors in **Settings** → **AI Connectors**. Other team members don't see this page. On an agent's **AI Connectors** tab, they can see which connectors the agent uses, but they can't change anything.

A workspace holds up to 10 connectors.

## How to connect an MCP server

You can connect any app that offers an MCP server. The app's provider or your developer gives you the server's address.

<Steps>
  <Step title="Add the server">
    In **Settings** → **AI Connectors**, click **Add custom MCP server**.
  </Step>
  <Step title="Fill in the details">
    - **Name**: what agents see next to the server's tools, for example `Linear`
    - **Description** (optional): what the server is for, so your team knows why it's there
    - **Server URL**: a public `https` address
    - **API key** (optional): sent to the server as a Bearer token
    - **HTTP headers** (optional): for servers that expect a key in their own header, such as `x-api-key`

    Allo stores the API key and header values encrypted. Nobody can read them again in Allo, admins included.
  </Step>
  <Step title="Confirm you trust the server">
    Tick **I trust this server**. Agents send the server details from your calls and messages when they use its tools, and its answers can change what agents say. Allo does not review third-party servers.
  </Step>
  <Step title="Test the connection">
    Click **Test connection**. Allo shows how many tools the server offers.
  </Step>
  <Step title="Choose the tools">
    Turn on the tools the AI may use, then click **Save**.
  </Step>
</Steps>

## HubSpot

HubSpot has a ready-made connector under **Apps**, so you don't need a server address. Click **Connect with OAuth**, then finish signing in to HubSpot in the window that opens. Then turn on the tools the AI may use and click **Save**, or click **Choose later**.

Today the HubSpot connector works in Allo AI only, not for agents during calls. See [HubSpot as a connector and as a CRM integration](#hubspot-as-a-connector-and-as-a-crm-integration).

## How tool access works

Each tool has three access levels:

| Level | What the AI can do |
| --- | --- |
| **Read and write** | Look things up, and create, change, or delete data |
| **Read only** | Look things up, never change anything |
| **No access** | Nothing, the AI never sees the tool |

The server decides whether a tool reads or writes. A tool that changes data can't be held to reads, so for that tool you choose between **Read and write** and **No access**. Allo marks these tools **Changes data**.

You can turn on up to 100 tools per connector.

## How to change a connector

Click **Manage tools** next to the connector to change its tools, name, or description.

- **Refresh tools** asks the server for its latest tools. New tools stay off until you turn them on.
- **Advanced settings** → **Bind parameters** lets Allo fill a tool's input itself, from a value like the **Caller phone number**, the **Contact email**, or the **Contact CRM ID**. The AI can't see or change a bound value. If the value isn't there (for example, no caller in an Allo AI chat), the tool doesn't run.

To remove a connector, open its menu and click **Remove**. Every agent loses its tools right away and Allo deletes the key. Past calls and messages keep their record of what the agents did.

## Where Allo uses your connectors

- **AI receptionist**: an agent only uses a connector you turned on in its **AI Connectors** tab. See [let your AI receptionist use your apps](/help/features/ai-receptionist-connectors).
- **Allo AI**: [Allo AI](/help/features/ai-assistant) can use your connectors in chat. Each answer shows the connectors and tools it used.

## HubSpot as a connector and as a CRM integration

You can connect HubSpot in two places, and each one signs in on its own:

- The [HubSpot CRM integration](/help/integrations/hubspot), in **Settings** → **Integrations**, syncs your calls, SMS, and contacts.
- The HubSpot connector, in **Settings** → **AI Connectors**, lets the AI look up and update HubSpot records.

Connecting one doesn't connect the other. Today the HubSpot connector works in Allo AI only. On an agent's **AI Connectors** tab, it shows as **Coming soon**.

## Troubleshooting

<AccordionGroup>
  <Accordion title="I don't see AI Connectors in Settings">
    Only the workspace owner and admins see **AI Connectors**. Ask one of them to set it up, or to change your role in [team settings](/help/team/manage-members). If you are an admin and still don't see it, [contact support](/help/support/contact).
  </Accordion>

  <Accordion title="&quot;Only workspace admins can change connectors.&quot;">
    Your role can view connectors but not change them. Ask the workspace owner or an admin.
  </Accordion>

  <Accordion title="&quot;Sign-in not completed. Try again.&quot;">
    The sign-in window closed or timed out before you finished. Click **Finish connecting** next to the app and sign in again. You can run one sign-in at a time.
  </Accordion>

  <Accordion title="&quot;Couldn't reach this server.&quot;">
    Check the **Server URL** and that the server is online. Allo only accepts a public `https` address, not a private or internal one.
  </Accordion>

  <Accordion title="&quot;The server refused this API key.&quot;">
    The key is wrong, expired, or missing a permission. Create a new key in the app, then paste it again.
  </Accordion>

  <Accordion title="&quot;This address doesn't answer as an MCP server.&quot;">
    The URL points to a website or an API, not to an MCP server. Ask the provider for the MCP server address. It often ends in `/mcp`.
  </Accordion>

  <Accordion title="The server offers too many tools">
    Allo can't list a server that offers more tools than its limit. Ask the provider to expose fewer tools, or to filter them before you connect.
  </Accordion>

  <Accordion title="&quot;Your workspace already has 10 connectors.&quot;">
    A workspace holds up to 10 connectors. Remove one you no longer use to add another.
  </Accordion>

  <Accordion title="&quot;Some tools are no longer offered by this server.&quot;">
    The server removed or renamed some tools. Open **Manage tools** and click **Refresh tools** to update the list.
  </Accordion>
</AccordionGroup>

## Need help?

<CardGroup cols={2}>
  <Card title="AI receptionist and your apps" icon="/media/allo-icons/AI.svg" href="/help/features/ai-receptionist-connectors">
    Choose which connectors and tools each agent can use during calls.
  </Card>
  <Card title="Contact support" icon="/media/allo-icons/CircleQuestion.svg" href="/help/support/contact">
    Write to us if something doesn't work as described here.
  </Card>
</CardGroup>
