Give an AI assistanta real WhatsApp number.

What the connector actually connects to

One remote server, reached over OAuth, calling Meta's documented Cloud API on a number that is still live in the WhatsApp Business app. There is no session held anywhere and nothing runs on your machine.

1. 1
   Your assistantClaude, ChatGPT, Cursor or Claude Code, over MCP
2. 2
   easycoexistence.com/api/mcpRemote, authorised by OAuth. No key is pasted anywhere
3. 3
   Meta Cloud APIThe documented Graph endpoints, with the account's own token
4. 4
   The business numberConnected through Coexistence, app still working on the phone

The alternative most WhatsApp automation takes is to sign in as a linked device and drive the WhatsApp Web session. That is against WhatsApp's terms and Meta detects it from the shape of the traffic rather than the code sending it, which is why an anti-ban claim describes something the vendor cannot control. Nothing here uses that mechanism.

How to install it

One remote endpoint, the same for every number on the account. There is no package to install and no key to generate: each client signs in with OAuth the first time it calls a tool.

https://easycoexistence.com/api/mcp

https://easycoexistence.com/api/mcp

claude mcp add --transport http easycoexistence https://easycoexistence.com/api/mcp

{
  "mcpServers": {
    "easycoexistence": {
      "url": "https://easycoexistence.com/api/mcp"
    }
  }
}

Connecting a number is a separate, one time step that needs a browser, because Meta's onboarding uses its own popup and a QR scan. get_connect_link returns that link if you would rather the assistant hand it to you.

Rules the tools enforce, so the assistant does not learn them the hard way

Eleven tools, and what each one is actually for

One connector exposes all of them across every number on the account. list_numbers comes first because every other tool takes a connection_id from it.

What still works when billing lapses

Only the tools that act on the outside world are gated. Reading stays open, on purpose.

An account that cannot see why it is blocked, or cannot check whether its numbers are healthy, has no way back except a support ticket. Those two reads are also what the health monitoring itself depends on.

The pair that matters if you serve other businesses

get_connect_link returns the link a client opens to attach their own number, and set_webhook_destination points that number at your system the moment it connects. Together they mean an agent can onboard a client end to end without anyone opening a dashboard.

One account holds as many numbers as you need, each billed on its own, and list_numbers returns all of them with the connection_id every other tool takes.

常見問題