Log inStart Free Trial
Meta Tech Provider

MCP tools reference

The connector exposes more than 30 tools across every connection on an account. list_numbers comes first for WhatsApp, whose tools take its connection_id, and list_social_accounts for the other channels, whose tools take an account_id. Six are gated when billing lapses: the four WhatsApp tools that act on the outside world, get_api_credentials, which returns the access token, and create_connect_link. The rest stay open.

easyCoexistence's MCP connector signs in with OAuth, with no API key to paste, and a single connector covers every number and social channel connected to the account.

30+

Tools the connector exposes.

6

Tools gated when billing lapses, including get_api_credentials, which returns the access token.

1

OAuth sign in, covering every number on the account.

What does each tool do?

Reading: list_numbers returns the connected numbers with status, quality rating and messaging tier, and is where every other call starts. get_number_health returns a live Meta snapshot plus the recent monitoring timeline, webhook events and poller checks together. get_api_credentials returns the Graph API base URL, WABA id, phone number id and, where available, the account's own access token.

Sending: send_message sends free text inside the 24 hour window, where replies are free up to 1,000 a month per number. send_template sends an approved template, which is how a conversation is started with someone who has not written. list_templates, create_template and get_template_status cover the template lifecycle.

Wiring: set_webhook_destination routes incoming messages and app echoes to your system, and passing null resets it. get_connect_link returns the dashboard link and steps for connecting a new number. get_docs returns the product documentation as markdown.

Partner API, for software or agencies whose own customers connect numbers: get_partner_setup reports billing, API key, events URL and the next step. create_api_key issues the Partner API key and shows it once, and will not replace an existing key without explicit confirmation. revoke_api_key revokes it, also after confirmation. set_partner_events_url sets where status events go and returns the signing secret once. create_connect_link creates a hosted connect link for one customer, valid 1 hour, the same as POST /api/v1/connect-sessions.

Why does connection_id matter?

Because it is what ties an instruction to a specific number, and an assistant cannot guess it.

Every tool that acts on a number takes a connection_id, and list_numbers is the only place one comes from. In practice this means an assistant asked to send a message will call list_numbers first, which is why the first request in a session is often slower than the rest.

It also means an account with several numbers is unambiguous by construction. There is no default number and no implicit selection, so an instruction that does not identify which number is asked about rather than guessed at.

What happens when billing lapses?

Six tools are gated: send_message, send_template, create_template and set_webhook_destination, which act on the outside world; get_api_credentials, because it returns the account's access token, which would let a blocked account send directly against the Graph API; and create_connect_link, which connects a new number. Every other read stays available, and so does the Partner API setup: get_partner_setup, create_api_key, revoke_api_key and set_partner_events_url.

This is deliberate rather than an oversight. An account that cannot see why it is blocked, or cannot check whether its numbers are healthy, has no route back except a support ticket. Those same reads are also what the health monitoring depends on, so gating them would switch off the monitoring at the moment somebody most needs it.

The practical effect is that a lapsed account still answers questions about its own state and is still monitored. What stops is anything that reaches a customer.

Common mistakes

  • Expecting the connector to receive messages. MCP is request and response; incoming traffic needs a webhook.
  • Hardcoding a connection_id. It comes from list_numbers and is not a value to write down.
  • Assuming a lapsed account is fully offline. Reads and monitoring continue on purpose, except the credentials, which carry the sending token.
Doing this with EasyCoexistence

One connector covers every number on an account, authorised over OAuth with no key to paste. From US$ 9 per number per month, falling to US$ 0.75 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

Do I choose which tool to call?

No. You ask in plain language and the assistant picks, which is what the tool descriptions are written for.

Can it read my conversations?

Not your WhatsApp messages: they route to the webhook destination you nominate. On other channels it reads posts, comments and analytics.

Is get_docs useful?

More than it sounds. It hands the assistant our documentation as markdown, so answers about Coexistence rules come from our docs rather than from recall.

Does one connector cover several clients?

Yes. One account holds as many numbers as you need and list_numbers returns all of them.

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