Connect

Connect Grok to WhatsApp

WhatsMCP exposes a real WhatsApp account as a remote MCP server over Streamable HTTP. Any Grok-powered agent or client that can add a remote MCP server reaches it the same way — point it at the endpoint, authenticate, and it can send and read WhatsApp on a live number.

endpoint
https://api.whatsmcp.com/mcp
Auth: OAuth (recommended) or API key
Setup

Add WhatsApp to Grok in 4 steps.

1

Add WhatsMCP as a remote MCP server

In your Grok client or agent framework, add a remote (HTTP / Streamable-HTTP) MCP server — not a stdio command — and give it the endpoint below. A client that supports OAuth discovers the sign-in flow from the URL alone; one that does not takes an API key in a header.

mcp server
URL   : https://api.whatsmcp.com/mcp
Type  : remote / HTTP
Auth  : OAuth  —  or  Authorization: Bearer wamcp_live_…
2

Driving Grok through the xAI API?

If you are building the agent yourself on the xAI API rather than using a packaged client, wire an MCP client into your tool-calling loop and register this endpoint on it. The server is stateless, so it needs no sticky routing and is safe to call from anywhere.

3

Connect a WhatsApp number

Create a free workspace, then connect a number. A Personal number pairs by QR: open Pair device in the console and scan the code with your phone (WhatsApp → Settings → Linked devices). WhatsMCP joins as a linked device — your phone stays primary. A Business (official) Cloud API number connects from the console instead; one connector serves both.

console
Register  →  https://console.whatsmcp.com/register
Personal  →  Console → Pair device → scan the QR
Business  →  Console → Add a number → Connect with Facebook

Send your first message

Ask the agent in plain language — "list my WhatsApp accounts and send a hello to +44 7700 900111". It calls wa_list_accounts for the account id, then wa_send_message, and you are live.

agent
> wa_send_message({ "account_id": "acct_…", "to": "447700900111", "text": "Hello from WhatsMCP!" })
{ "status": "sent", "message_id": "3EB0…" }
Capabilities

What Grok can do once it is connected.

The connection exposes one toolbelt for the whole account. Ask Grok in plain language and it calls the right tool — starting with wa_list_accounts for the account id every other tool takes.

Send and reply

Send and answer messages as the connected number — text, images, documents and voice notes — in direct chats, groups and channels, with edits and reactions.

Read and search

Page message history by cursor with no gaps or duplicates, catch up on a chat, and resolve "message Alice" against the synced address book.

Handle media

Download received images, documents and audio by message id, and attach files on the way out.

Manage groups

Create groups, add and remove members, promote and demote admins, join by invite link and follow channels.

Inspect calls

Export call history — direction, peer, duration, answered state and codec — for logging or follow-up.

Receive webhooks

Push each inbound message to your own HTTPS endpoint, signed with HMAC-SHA256, instead of polling for it (paid plans).

Trial & limits

Free to start, honest about the rest.

  • Free Personal plan — self-serve, no card, one linked number. Enough to connect a number and drive it from Grok.
  • Business (official) runs on Meta's WhatsApp Cloud API with message templates and the 24-hour window, on a 7-day free trial — same endpoint, same Grok setup.
  • Plan-scoped tools — which tools appear in the client depends on your plan; an excluded tool is absent, not present-and-refusing. Webhooks and higher send caps are on paid plans.
  • Independent integration — not affiliated with or endorsed by Meta. Automating a Personal number carries the usual WhatsApp terms-of-service risk; the number can be rate-limited or blocked. Remove WhatsMCP any time with wa_unpair_account .
FAQ

Connecting Grok to WhatsApp.

Can a Grok bot connect to WhatsApp?

Yes, through WhatsMCP. Add it as a remote MCP server at https://api.whatsmcp.com/mcp in any Grok-powered agent or MCP-capable client, authenticate with OAuth or an API key, and the agent can send and read WhatsApp on a real number.

Does Grok need WhatsApp Business API to send messages?

Not for a Personal number — WhatsMCP links it as a linked device, the same mechanism as WhatsApp Web, with no Business API application. If you want the official path (templates, the 24-hour window), connect a Business Cloud API number instead; the same endpoint and the same Grok setup serve both.

What is the WhatsMCP endpoint URL?

The full URL https://api.whatsmcp.com/mcp — the api. host and the /mcp path both matter. Giving a client the bare host (whatsmcp.com, or whatsmcp.com/mcp) is the most common setup failure; it is a remote Streamable-HTTP MCP server, not a stdio command.

Do I need an API key, or is OAuth enough?

OAuth is recommended and is what every supported client does by default — you approve the connection in the browser and nothing is pasted or stored. An API key (wamcp_live_…) over Authorization: Bearer, or x-api-key where a client reserves Authorization for its own token, is the fallback for CLIs, CI and clients that cannot sign in.

Does this use a Personal or a Business WhatsApp number?

Either, through the same endpoint. A Personal number pairs by QR as a linked device (free plan, one number). A Business (official) number runs on Meta's WhatsApp Cloud API, connects from the console, and adds message templates and the 24-hour window on a 7-day free trial. See /whatsapp-business-api for the official path.

Is this an official WhatsApp or Meta product?

No. WhatsMCP is an independent integration, not affiliated with or endorsed by Meta. A Personal number connects as a linked device, the same mechanism as WhatsApp Web, and you can remove it any time from the handset or with wa_unpair_account.

Give Grok a number.

Get an API key Open console

Free Personal plan · 7-day free trial for Business (official).