Skip to main content
Install Allo for Grok Bot, the official plugin, and use Allo from Grok Bot. You sign in to Allo. A custom connector on grok.com is the alternative, further down. Allo plan: Business or Ultra. See Plans and pricing. Allo is not in the grok.com connector catalog. The catalog covers services such as Notion, GitHub, and Linear. The official listing is the Grok Bot plugin below.

Install Allo for Grok Bot

The plugin is named Allo for Grok Bot. Open the listing: Allo for Grok Bot.
1

Add the plugin

On the listing, click Add to Grok Bot.You can also open Connect apps in Grok Bot and add Allo. In Grok Bot’s chat, this command does the same:
2

Sign in to Allo

Sign in to Allo and authorize access. There is no API key to copy. The first time the bot uses Allo, it asks you to sign in if you have not already.Allo never sees your Grok password.
The plugin reads calls and texts with your Allo permissions. It asks before a text goes to a customer. It cannot place a call. Numbers you add go to the Power Dialer, and you start the session in Allo. A call flow change stays a draft until you publish it in Allo. It adds three commands: /allo-briefing, /allo-followups, and /allo-report. The MCP server page explains each one. Allo’s page for this plugin is Allo for Grok Bot.

Add a custom connector on grok.com

Use this when you are in grok.com and you want Allo’s MCP server directly. Grok connects to https://mcp.withallo.com/mcp. That address is public, which is what Grok requires. To pass an Allo API key yourself, use the Grok API or the Grok CLI. Connectors are available to every Grok user. On Grok Business and Enterprise, a team admin adds the connector in the xAI console before teammates can connect it. Adding or removing a connector needs Team Read-Write permission. That permission usually sits with a team admin. These steps follow xAI’s Connectors guide.
1

Open connectors

2

Add a custom connector

Click New Connector, then select Custom.
3

Enter the Allo server

Enter this MCP server URL:https://mcp.withallo.com/mcp
4

Authenticate

Complete the authentication Grok shows.When Grok opens Allo, sign in and approve the permissions. Allo never sees your Grok password. You can remove the connector later in Grok.If Grok asks for an API key instead of a sign-in, create one with the steps in the API section below. Paste the raw key, or Api-Key followed by the key.
On Grok Business and Enterprise, a team admin provisions Allo first. Sign in at console.x.ai, select the team, and open Grok Business → Connectors. Click + Add Connector, select Other, enter https://mcp.withallo.com/mcp, and complete authentication. Teammates then connect their own accounts at grok.com/connectors.

Try one of these

Copy a prompt into Grok after Allo is connected. Change the names, numbers, and dates for your team.

Missed calls

Show me all missed calls from this week

Manager

What was my team's answer rate last month compared to the month before?

Follow-up

Send an SMS to +33612345678 from my main number saying we'll call back in 10 minutes

Ops

List contacts who called 3+ times last week with no owner

What you can do

Once connected, Grok can use the Allo tools your account is allowed to use: search calls, read transcripts, send SMS, manage contacts and tags, and pull team analytics.

Browse the full tools list

Every Allo MCP tool, with the scope it needs.

Using the Grok API or CLI

The Grok API and the grok CLI can call Allo with an Allo API key. xAI documents both. Allo for Grok Bot signs you in instead. The custom connector screen on grok.com does not name an API key field.
1

Create 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. Allo shows it once.
2

Call Allo from the API

Add a remote MCP tool. Put the key in headers. In the xAI SDK, the same map is extra_headers.
Leave allowed_tools empty to expose every tool, or list tool names to limit what Grok can call. xAI supports Streaming HTTP and SSE on this tool.
3

Or add Allo in the Grok CLI

The grok CLI can store the header for you:
grok mcp list shows the server. grok mcp doctor Allo checks the connection.
Only admins and owners can create API keys.Do not put the Allo API key in the authorization field. xAI sends that value as Authorization: Bearer .... Allo reads a Bearer value as a session token, and the request returns 401. Use headers or extra_headers, with Api-Key or the raw key.
Reference: Remote MCP tools and MCP servers in the Grok CLI. Scope names are on the MCP server page. The same Cursor plugin also works in Grok Bot. Setup for that plugin is on the MCP server page.

Troubleshooting

A team admin has to add it in the xAI console before members can connect. The admin needs Team Read-Write permission. After it is listed, each person connects their own account at grok.com/connectors.
Use https://mcp.withallo.com/mcp. Grok rejects localhost and private network addresses. This Allo URL is already public, so Grok can reach it directly.
On grok.com, finish the Allo sign-in with an active Allo account. On the API or the CLI, send the key as Api-Key YOUR_API_KEY or as the raw key. A Bearer prefix is a session token, and Allo returns 401.
Remove the connector in Grok and add it again with the same URL. On the CLI, run grok mcp doctor Allo, then start a new session.

Using another assistant?

Claude connector

Add Allo in Claude.ai. You sign in to Allo, with a Client ID on that screen.

ChatGPT connector

Add Allo in ChatGPT on the web. You sign in to Allo.

Other MCP clients

Cursor, Claude Code, VS Code, and any client that takes an API key.