Connect

Connect Cursor to WhatsApp

WhatsMCP is a remote MCP server, and Cursor 1.0+ speaks to it over Streamable HTTP with native OAuth — no API key to copy. Add it once and Cursor's Agent can read, summarize, search and reply to your WhatsApp chats from the editor.

~/.cursor/mcp.json
{
  "mcpServers": {
    "whatsmcp": {
      "url": "https://api.whatsmcp.com/mcp"
    }
  }
}
Setup

Add WhatsApp to Cursor in 4 steps.

1

Option A — one click

Open the deep link below (or put it behind an "Add to Cursor" button). Cursor opens, adds the server, and prompts you to sign in — skip to the sign-in step.

deep link
cursor://anysphere.cursor-deeplink/mcp/install?name=whatsmcp&config=eyJ1cmwiOiJodHRwczovL2FwaS53aGF0c21jcC5jb20vbWNwIn0=
2

Option B — add it yourself

Open Cursor Settings → Tools & Integrations (older builds: Settings → MCP) → New MCP Server, or edit mcp.json directly: ~/.cursor/mcp.json is global, <project>/.cursor/mcp.json is per-project and shareable. Add the whatsmcp entry and reload. If your build does not pick it up, add "type": "http" next to the url.

~/.cursor/mcp.json
{
  "mcpServers": {
    "whatsmcp": {
      "url": "https://api.whatsmcp.com/mcp"
    }
  }
}
3

Sign in and verify

On first connect a browser tab opens on the WhatsMCP sign-in page — log in and approve, and it hands control back to Cursor. Under Tools & Integrations, whatsmcp should show a green dot and a list of tools (wa_list_messages, wa_send_message, wa_get_chat, …); toggle the server and the tools you want on.

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
Capabilities

What Cursor can do once it is connected.

The connection exposes one toolbelt for the whole account. Ask Cursor 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 Cursor.
  • 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 Cursor 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 Cursor to WhatsApp.

How do I add WhatsMCP to Cursor?

Use the one-click deep link, or add a whatsmcp entry to ~/.cursor/mcp.json (global) or <project>/.cursor/mcp.json (per-project) with "url": "https://api.whatsmcp.com/mcp", then reload Cursor and finish the OAuth sign-in in the browser. Native remote-MCP OAuth needs Cursor 1.0 or newer.

Cursor connects but lists no tools, or shows 401 — why?

The sign-in did not reach the server. Re-add the server (or re-trigger the OAuth prompt) and finish the browser login. Also confirm the endpoint is exactly https://api.whatsmcp.com/mcp — both the api. host and the /mcp path matter — and that a WhatsApp number is actually connected and live in the console.

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 Cursor a number.

Get an API key Open console

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