Skip to main content
Connect Allo to any AI assistant that supports the Model Context Protocol (MCP). Search calls, read transcripts, send SMS, manage tags, analyze team performance, and set up your AI receptionist — directly from your AI tool.

Using Claude.ai instead?

Connecting from Claude.ai web or desktop? See the Claude Connector guide. You don’t need an API key there.

Using Cursor?

Install the Allo plugin from the Cursor Marketplace. You sign in to Allo, so you don’t need an API key.

Prerequisites

1

Get an API key

Go to Settings > API and click Create API Key.Select the scopes your workflow needs. For full MCP access, enable all scopes. For read-only access, select only the READ scopes.Copy the key — it won’t be shown again.
2

Choose your AI client

Follow the setup instructions for your client below.
Only admins and owners can create API keys. Team members cannot generate keys.
The Allo plugin for Cursor and the Claude Connector sign you in to Allo instead. If you use one of them, skip the API key.

Connect your AI client

Claude Code

Run this command in your terminal:
Replace YOUR_API_KEY with your Allo API key.

Claude Desktop

Open Settings > MCP in Claude Desktop and add a new server with this configuration:

Cursor

Install the Allo plugin from the Cursor Marketplace. Type this in Cursor’s agent chat:
The first time Cursor uses Allo, it asks you to sign in to Allo and authorize access. You don’t need an API key. The plugin connects Cursor to the Allo MCP server and teaches it how to use the tools: searching calls and texts, sending SMS, team analytics, the AI receptionist, and call flows. It also adds three commands: The same plugin also works in Grok Bot.

Set up Cursor with an API key

To configure the server yourself, go to Settings > MCP in Cursor, click Add new MCP server, and select Type: HTTP. Alternatively, add this to your ~/.cursor/mcp.json:

VS Code

Add this to your .vscode/mcp.json file (create it if it doesn’t exist):

Windsurf

Open Settings > MCP in Windsurf and add:

Other clients

Any MCP-compatible client can connect to Allo using:
  • Server URL: https://mcp.withallo.com/mcp
  • Transport: HTTP
  • Authentication: Authorization header with your API key
Refer to your client’s documentation for how to configure remote MCP servers with custom headers.

Available tools

Once connected, your AI assistant can use these tools: The server also serves two guides as MCP resources, allo-mcp://guides/ai-receptionist-setup and allo-mcp://guides/ai-receptionist-prompt. The receptionist tools point your assistant at them, so ask it to set a receptionist up rather than to fill fields one at a time.

Everything the receptionist can be configured to do

Business details, voice, prompt, capabilities, business hours, transfer rules, calendars and knowledge. The reference for what the receptionist tools write, and the two merge rules they follow.

Inboxes

Ask your assistant to set up inboxes in plain words. It starts from the inbox suggestions, which already cover your lines and phone-menu options, so you never need menu node IDs. When you name an inbox (“my Sales inbox”), the assistant looks it up and lists that inbox’s conversations, from all of its lines. An inbox can also follow a topic: the assistant saves your call tags (AI or manual) on it, and a conversation shows when any of its calls on the inbox’s lines carries one. Admins and managers can also set up inboxes for a teammate. The inbox belongs to the teammate and shows in the teammate’s inbox switcher. The assistant never deletes an inbox unless you ask for it.
Connected Allo before October 28, 2026? Reconnect to use the inbox tools. In Claude, Grok, ChatGPT or Codex, disconnect the Allo connector and connect it again, then approve the inbox permissions. With an API key, create a new key with the INBOXES_READ and INBOXES_WRITE scopes.

Inboxes API reference

Sources, phone-menu conditions, filters, teammate inboxes, and limits.

Required scopes

Each tool requires specific API key scopes. Select the scopes matching the tools you need:
For full access to every tool, select all scopes when creating your API key.

Report a problem

allo_submit_feedback sends a report about a tool straight to the Allo team, and the team reads every report. Connected assistants use it on their own when a tool fails in a way retrying will not fix. You can also ask for it: “report that to Allo”. It needs no scope, and it is only available through the MCP server, not the REST API. A report is most useful with the tool name, the request_id from the error, and a short description of what was expected and what happened.
Reports should describe the problem, not quote calls or messages. For workspaces with HIPAA enabled, Allo keeps only the category, tool, and request IDs of a report and discards its text.

Example prompts

Once connected, try asking your AI assistant:
  • “Show me all missed calls from this week”
  • “What was my team’s answer rate last month compared to the month before?”
  • “Find all calls tagged ‘demo’ from the past 30 days and summarize the transcripts”
  • “Send an SMS to +33612345678 from my main number saying we’ll call back in 10 minutes”
  • “Who on my team made the most outbound calls this week?”
  • “List all unread conversations and mark them as read”
  • “Tag the last 5 inbound calls as ‘support’”
  • “Show me what’s in my Power Dialer queue right now”
  • “Add these numbers to my Power Dialer queue: +14155551234, +33612345678”
  • “Set up the AI receptionist on my main line, ask me what you need to know”
  • “Add a transfer rule sending billing questions to +14155551234”
  • “Set up a Sales inbox for me”
  • “Create a Support inbox for Lucio with Website FR option 2”
  • “Show my Sales inbox”
  • “Set up a Porting inbox across US Support and FR Support, with only calls tagged porting”
  • “Pin this customer”
  • “Mute my Support inbox”

Troubleshooting

Verify your API key is correct and has not been revoked. Go to Settings > API to check your active keys. If needed, create a new key.
Your API key is missing a required scope. Check the required scopes table above and create a new key with the needed scopes.
Ask your assistant to report it with allo_submit_feedback, including the tool name and the request_id from the error. The report goes straight to the Allo team. See Report a problem.
Make sure the MCP server is connected and active. Restart your AI client and verify the server URL is exactly https://mcp.withallo.com/mcp. Some clients require a restart after adding a new MCP server.

Need help?

API authentication

Full API key and scopes documentation

Contact support

Get help from the Allo team