Log inStart Free Trial
Meta Tech Provider

WhatsApp in any MCP client: Gemini CLI, VS Code, Cursor, Devin Desktop (Windsurf) and more

Any MCP client that supports remote servers over Streamable HTTP with OAuth can work on a WhatsApp Business number: add the server's URL, sign in once in the browser, and the WhatsApp tools appear. Only the configuration differs. Cursor and Zed take url, Gemini CLI takes httpUrl, Antigravity takes serverUrl, and VS Code and Cline need the transport set to HTTP.

easyCoexistence runs one remote MCP server, https://easycoexistence.com/api/mcp, with OAuth sign-in and more than 30 tools for the WhatsApp Business numbers you connect through Coexistence: health, messages, templates, routing and automations, from any client that speaks Streamable HTTP.

httpUrl

The Gemini CLI settings key for a Streamable HTTP server; url there means an SSE endpoint.

serverUrl

Antigravity's key for a remote server; url also works, while httpUrl and the legacy SSE transport are not supported.

18 June 2026

When Gemini CLI was replaced by Antigravity CLI for unpaid tier and Google One users.

streamableHttp

The type to set for a remote server in Cline; left out, Cline defaults to the legacy SSE transport.

Devin Desktop

The new name for Windsurf; its FAQ says only the name and branding are changing.

POST only

easyCoexistence's MCP server runs Streamable HTTP in stateless mode and opens no SSE stream.

What does a client need to connect to a remote WhatsApp MCP server?

Three things, and most current clients have all of them. Streamable HTTP, the MCP transport where the client POSTs to one URL; the server here runs it in stateless mode and opens no SSE stream, so a client set to SSE fails. OAuth discovery: on the first call the server answers 401 with a pointer to its metadata, the client registers itself through dynamic client registration and opens your browser, and the sign-in uses PKCE. And a browser on the machine where the client runs.

No header, API key or token goes in the config. The server accepts protocol versions 2025-06-18, 2025-03-26 and 2024-11-05, and a client that supports only local servers started on your machine cannot reach it.

Which configuration does each client use?

Each of these was checked in the client's own documentation on 11 November 2026. The pattern is the same everywhere, a name and the URL https://easycoexistence.com/api/mcp, but the key that holds the URL and the place the entry lives differ, and a wrong key fails quietly in some clients. Each entry needs only a name and the URL, with no header and no token:

Cursor~/.cursor/mcp.json or .cursor/mcp.json, under mcpServers, with url
VS Code (Copilot)MCP: Add Server, then HTTP; or ~/.copilot/mcp-config.json with type http and url
Gemini CLIgemini mcp add --transport http, or httpUrl in settings.json
Antigravity~/.gemini/config/mcp_config.json or .agents/mcp_config.json, with serverUrl
ZedSettings > AI > MCP Servers, Add Remote Server; context_servers with url
ClineRemote Servers tab with Streamable HTTP, or type streamableHttp with url
Devin CLIdevin mcp add with the URL, then devin mcp login

What do the configuration files look like?

These are the entries for the clients that keep servers in a file, as their documentation shows them. Paste the one for your client into the file named above it, merging it with any servers already there, then reload the client and complete the sign-in it opens. Where a client also offers a command or a form, that path writes the same entry for you:

One entry per client
// Cursor: ~/.cursor/mcp.json
{ "mcpServers": { "easycoexistence": { "url": "https://easycoexistence.com/api/mcp" } } }

// VS Code with Copilot: ~/.copilot/mcp-config.json
{ "mcpServers": { "easycoexistence": { "type": "http", "url": "https://easycoexistence.com/api/mcp" } } }

// Gemini CLI: ~/.gemini/settings.json
{ "mcpServers": { "easycoexistence": { "httpUrl": "https://easycoexistence.com/api/mcp" } } }

// Antigravity: ~/.gemini/config/mcp_config.json
{ "mcpServers": { "easycoexistence": { "serverUrl": "https://easycoexistence.com/api/mcp" } } }

// Zed: settings.json
{ "context_servers": { "easycoexistence": { "url": "https://easycoexistence.com/api/mcp" } } }

// Cline: cline_mcp_settings.json
{ "mcpServers": { "easycoexistence": { "type": "streamableHttp", "url": "https://easycoexistence.com/api/mcp" } } }

How do you add it in VS Code?

With Copilot selected, run Chat: Open Customizations, choose MCP Servers and select Add Server (+) in the User group, or run MCP: Add Server from the Command Palette for the same guided flow. Pick HTTP (HTTP or Server-Sent Events), paste the URL, enter easycoexistence as the server ID, then choose Global and Copilot Global for a personal setup shared across your workspaces on that machine. Complete the authorization when VS Code prompts for it.

Microsoft's reference calls the older .vscode/mcp.json file, with its servers key, the deprecated editor-managed format and points new setups to the Copilot files. A workspace-root .mcp.json shares a server with teammates; since the entry holds no secret, it is safe to commit.

How do you add it in Gemini CLI and Antigravity?

In Gemini CLI, run gemini mcp add --transport http easycoexistence https://easycoexistence.com/api/mcp -s user. Without -s user the server is saved to the project, in .gemini/settings.json. Then run /mcp auth easycoexistence to sign in; the same command signs in again when tokens expire. Google notes that Gemini CLI was replaced by Antigravity CLI on 18 June 2026 for unpaid tier and Google One users.

In Antigravity, put the entry with serverUrl in ~/.gemini/config/mcp_config.json for every project, or in .agents/mcp_config.json for one workspace. In the CLI, /mcp opens the MCP Manager with each server's status; in the IDE, select … in the agent panel, then MCP Servers, Manage MCP Servers and View raw config. Because this server supports dynamic client registration, no client ID is needed.

How do you add it in Zed, Cline and Devin?

In Zed, open Settings > AI > MCP Servers, click Add Server and choose Add Remote Server; with no Authorization header in the entry, Zed runs the standard MCP OAuth flow. In Cline, open the MCP Servers icon, then the Remote Servers tab, enter a name and the URL, choose Streamable HTTP and click Add Server; from the Cline CLI, cline mcp add easycoexistence with the URL and --transport http, then the wizard's Authorize OAuth action.

Devin Desktop, the new name for Windsurf, manages servers under Customize > MCPs in the Agents window and keeps them in ~/.config/devin/mcp_config.json or the project's .devin folder; when stored credentials expire, the server shows Needs authentication and Authenticate signs in again. In the Devin CLI, run devin mcp add easycoexistence with the URL and -s user, since the default is local scope, then devin mcp login easycoexistence.

What works the same in every client?

Everything behind the URL. Each client signs in to the same easyCoexistence account, sees the same numbers through list_numbers and gets the same more than 30 tools. Meta's rules come with them: a typed message reaches only someone who wrote in the last 24 hours, templates go out through the API only, and a Coexistence number sends at most 20 messages per second. Send tools need an active plan in every client, while read tools keep working.

What differs is the client's own control over tool calls, such as Cursor asking for approval before it uses an MCP tool by default. The server sends its tool list when a client connects and does not announce changes, so reload or reconnect the client after your account gains a feature.

How to set it up

  1. Connect your numberSign up at easycoexistence.com and connect the number through Meta's Embedded Signup; the WhatsApp Business app keeps working on the phone.
  2. Add the serverUse your client's command or form, or paste its entry into the right file, with https://easycoexistence.com/api/mcp as the URL.
  3. Reload and sign inReload the client, then approve the browser sign-in it opens with your easyCoexistence account.
  4. Try a requestAsk "Which WhatsApp numbers do I have, and are they healthy?" and check that the client calls list_numbers.

Common mistakes

  • Writing url in Gemini CLI's settings.json. There it means an SSE endpoint, which this server does not open; use httpUrl, or gemini mcp add --transport http.
  • Leaving type out of a Cline entry. Cline then uses the legacy SSE transport and the connection fails, so set type to streamableHttp.
  • Adding the server in Gemini CLI or the Devin CLI without a scope, then missing it in another folder. Gemini defaults to project scope and Devin to local; pass -s user.
  • Signing in from a headless server or an SSH session. Gemini CLI documents that its OAuth flow needs a local browser and a localhost callback, so run the sign-in on your own machine.
Doing this with EasyCoexistence

The app stays on your phone, and every number is monitored 24/7 with alerts. US$ 9 down to US$ 0.75 per number per month, falling as you add numbers, with the first 3 days free.

easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.

Frequently asked questions

Is there a local version to install?

No. The server is remote only, so there is no package, npx command or process to keep running. Closing the client changes nothing on the connected number.

Can I put an API key in a header instead of signing in?

No. The MCP server accepts only OAuth tokens from easyCoexistence's own sign-in. The ec_live_ key from create_api_key belongs to the Partner API, the REST API for software that connects its customers' numbers, and does not open the MCP server.

How long does the sign-in last?

Access tokens last 1 hour and the client renews them by itself with a refresh token; each renewal brings a new one, and a refresh token expires after 60 days without use. After that gap the client asks you to sign in again.

Can several clients use the same account at once?

Yes. Each client signs in on its own, so Cursor, VS Code and a terminal agent can work side by side on the same numbers, and removing one leaves the others connected.

Keep reading

Ready to get started?

Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.

Start Free Trial

Verified on