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.
To bring your own apps and MCP servers into Allo instead, see AI Connectors.
Add Allo in Claude.ai. You sign in to Allo, so you skip the API key.
Install the Allo plugin in ChatGPT. You sign in to Allo. A custom MCP server is the alternative.
Install Allo for Grok Bot. You sign in to Allo. A custom connector on grok.com is the alternative.
Install the Allo plugin from the Cursor Marketplace. You sign in to Allo, so you skip the API key.
Prerequisites
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.
Choose your AI client
Follow the setup instructions for your client below.
Connect your AI client
Claude Code
Run this command in your terminal:
claude mcp add Allo --transport http https://mcp.withallo.com/mcp \
--header "Authorization: YOUR_API_KEY"
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:
{
"mcpServers": {
"Allo": {
"url": "https://mcp.withallo.com/mcp",
"headers": {
"Authorization": "YOUR_API_KEY"
}
}
}
}
Cursor
Install the Allo plugin from the Cursor Marketplace. Type this in Cursor's agent chat:
/add-plugin allo
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:
| Command | What it does |
|---|---|
/allo-briefing | Daily briefing: call volume, what needs attention, and follow-ups |
/allo-followups | Finds the calls that still need a follow-up |
/allo-report | Team phone performance report, compared with the previous period |
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:
{
"mcpServers": {
"Allo": {
"url": "https://mcp.withallo.com/mcp",
"headers": {
"Authorization": "YOUR_API_KEY"
}
}
}
}
VS Code
Add this to your .vscode/mcp.json file (create it if it doesn't exist):
{
"servers": {
"Allo": {
"type": "http",
"url": "https://mcp.withallo.com/mcp",
"headers": {
"Authorization": "YOUR_API_KEY"
}
}
}
}
Windsurf
Open Settings > MCP in Windsurf and add:
{
"mcpServers": {
"Allo": {
"serverUrl": "https://mcp.withallo.com/mcp",
"headers": {
"Authorization": "YOUR_API_KEY"
}
}
}
}
Other clients
Any MCP-compatible client can connect to Allo using:
- Server URL:
https://mcp.withallo.com/mcp - Transport: HTTP
- Authentication:
Authorizationheader 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:
| Tool | What it does |
|---|---|
allo_get_me | Discover your API key's scopes, available endpoints, and team info |
allo_list_users | List team members with roles and status |
allo_list_numbers | List phone numbers with capabilities (voice, SMS) |
allo_list_tags | List all tags configured on your team |
allo_list_conversations | List conversations grouped by contact, sorted by recent activity, for one line or one inbox; filter pinned conversations |
allo_search_conversation_items | Search calls and SMS with filters: keyword, type, direction, tags, date range |
allo_get_conversation_item | Get full details of a call or SMS, including transcript |
allo_batch_get_conversation_items | Fetch up to 100 items in a single request |
allo_mark_conversation | Mark conversations as read, unread, archived, or unarchived |
allo_add_call_tags | Add tags to a call |
allo_remove_call_tag | Remove a tag from a call |
allo_send_sms | Send an SMS from one of your Allo numbers |
allo_get_team_analytics | Get team KPIs: total calls, talk time, answer rate, per-user breakdown |
allo_get_team_outbound_analytics | Get outbound metrics: dial funnel, time series, heatmap, leaderboard |
allo_get_dialing_queue | Read the user's Power Dialer queue: settings, ordered numbers, and per-entry call state |
allo_add_to_dialing_queue | Append numbers to the user's Power Dialer queue (creates the queue on first call); accepts optional contact metadata |
allo_get_agent | Read a line's whole AI receptionist configuration in one call |
allo_update_agent | Configure the AI receptionist: business details, voice, capabilities, hours, transfer rules, calendars, knowledge text |
allo_set_agent_prompt | Write the AI receptionist's prompt, section by section |
allo_set_agent_status | Turn the AI receptionist on or off for a line |
allo_add_agent_knowledge_website | Give the receptionist a web page to answer callers from |
allo_set_agent_knowledge_website_status | Take a knowledge website out of use without deleting it |
allo_delete_agent_knowledge | Delete a knowledge website or an uploaded document |
allo_list_calendars | List the calendars connected to your workspace |
allo_get_calendar | Get one calendar with the event types its provider offers |
allo_list_voices | List the voices an AI receptionist can speak with |
allo_list_inboxes | List your inboxes, or a teammate's |
allo_get_inbox_suggestions | Get ready-made inbox sources ranked from recent calls and texts, phone-menu options included |
allo_list_menu_options | List a line's phone-menu options, for a custom inbox branch |
allo_create_inbox | Create an inbox for yourself or a teammate |
allo_update_inbox | Rename an inbox, change its sources or filters, mute or unmute it |
allo_delete_inbox | Delete an inbox. Only used when you ask for it |
allo_pin_conversation | Pin a conversation (up to 10) |
allo_unpin_conversation | Unpin a conversation |
allo_submit_feedback | Report a bug, misleading doc, or missing capability to the Allo team. Needs no scope |
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.
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.
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:
| Scope | Tools |
|---|---|
CONVERSATIONS_READ | List conversations, search, get item, batch get |
CONVERSATIONS_WRITE | Mark conversation, pin and unpin |
USERS_READ | List users, get me |
PHONE_NUMBERS_READ | List numbers |
TAGS_READ | List tags |
TAGS_WRITE | Add tags, remove tag |
SMS_SEND | Send SMS |
FAX_SEND | Send faxes |
DIALING_QUEUE_READ_WRITE | Read and append to the Power Dialer queue |
AGENTS_READ | Read the AI receptionist configuration, calendars, voices |
AGENTS_WRITE | Configure the AI receptionist, its prompt and its status |
INBOXES_READ | List inboxes, inbox suggestions, menu options |
INBOXES_WRITE | Create, update, mute, and delete inboxes |
| None | Submit feedback |
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.
| Category | Use it when |
|---|---|
BUG | A tool failed with an error that should not happen |
UNEXPECTED_RESULT | A tool succeeded but the data looks wrong, such as a filter that was ignored |
DOCS | A tool description or doc page was wrong or misleading |
MISSING_CAPABILITY | You asked for something no tool can do |
OTHER | Anything else worth telling the Allo team |
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.
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
Connection failed or unauthorized
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.
Tool returns a permission error
Your API key is missing a required scope. Check the required scopes table above and create a new key with the needed scopes.
A tool returns wrong data or an unexpected error
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.
Need help?
Full API key and scopes documentation
Get help from the Allo team