easyCoexistence MCP server: every tool, by network
The easyCoexistence MCP server gives Claude, ChatGPT and other MCP clients 72 tools across WhatsApp, Instagram, Facebook, TikTok, YouTube, LinkedIn and more channels: publishing and scheduling, comments, DMs, insights, comment-to-DM rules, automations and any other endpoint of each network's official API, behind one connector with OAuth sign-in.
Add it in Claude as a custom connector or in ChatGPT as a custom MCP server, then sign in: how to add the connector. The tools a session sees follow what the account has connected.
WhatsApp 12
A number connected through Coexistence: health, messages inside the 24-hour window, templates, and where its messages go.
WhatsApp MCP server for Claude, ChatGPT and Cursor
list_numbers- List the user's connected business phone numbers with connection status, quality rating and messaging tier. Start here: other tools take a connection_id from this list.
get_number_health- Full health picture of one number: live Meta snapshot (quality, coexistence link state) plus the recent monitoring timeline (webhooks + poller checks).
get_api_credentials- Credentials for integrating this number with an external system (n8n, CRM, custom code): Graph API base URL, WABA ID, phone number ID and — when available — the user's own access token. These are for sending. To receive, use set_webhook_destination with a generic webhook (n8n: Webhook node, not WhatsApp Trigger); there is no app secret to fetch, see get_docs 'Securing the webhook'.
send_message- Send a free-form text message from the user's business number via the official API. Only works within a customer-service window: the recipient must have messaged this number in the last 24 hours (those replies are free). To start a conversation with someone who hasn't written, use send_template with an approved template instead.
list_templates- List the message templates on this number's WhatsApp Business Account with their review status. In coexistence, templates can ONLY be sent via the API — the phone app cannot send them.
create_template- Create a message template and submit it for Meta review (approval usually takes minutes, up to ~24h). Categories: UTILITY (transactional), MARKETING (promotional — requires a payment method on the user's WhatsApp Business Account), AUTHENTICATION. Components follow Meta's template format, e.g. [{type:'BODY', text:'Hello {{1}}, your order shipped.'}]. Variables are {{1}}, {{2}}… and need example values: {type:'BODY', text:'…', example:{body_text:[['Ana']]}}.
get_template_status- Check the review status of a template by name (APPROVED / PENDING / REJECTED).
send_template- Send an APPROVED template message. This is how you start a conversation with someone who hasn't messaged first. Marketing sends are billed by Meta to the user's own WhatsApp Business Account payment method (set up in WhatsApp Manager — we can't add cards via API).
set_webhook_destination- Route this number's incoming messages (and echoes of messages sent from the phone app) directly from Meta to the user's own system — easyCoexistence never stores or relays the content. The destination must be an HTTPS endpoint implementing Meta's webhook handshake: on GET with hub.mode=subscribe & hub.verify_token=<verify_token>, echo back hub.challenge. Meta signs each POST (X-Hub-Signature-256) with easyCoexistence's app secret, which is never shared, so the destination cannot validate that header: do not enable signature validation there, and use a generic webhook receiver (in n8n the plain Webhook node, not the WhatsApp Trigger node, which expects the user's own Meta app). Authenticate deliveries with a long random secret inside callback_url itself (path or query string) that the endpoint checks on every request; get_docs, section 'Securing the webhook', has the details. Saved within 24 hours of the number connecting, it also gets Meta's one-time import of the number's contacts and up to 6 months of chats (history webhooks, done when metadata.progress is 100), so set it right after connecting when past chats matter. Call with callback_url=null to reset routing.
remove_number- Remove a number from easyCoexistence (the dashboard's Remove, DELETE /api/v1/connections/:id): our access at Meta is revoked, monitoring stops, billing stops at the end of the cycle, and its automations stop. The number keeps working on the Cloud API until the business disconnects it in the WhatsApp Business app. Requires confirm=true, only after the user explicitly asks to remove that number.
get_connect_link- How to connect a new number. Onboarding needs a browser (Meta popup + QR code scan), so this returns the dashboard URL and the steps, plus where to start when the user wants their own customers to connect numbers from inside the user's software (the Partner API).
get_docs- The easyCoexistence product documentation (markdown): what Coexistence is, how connecting works, number eligibility rules and common onboarding blocks, sending rules (24h window, templates), webhook routing, monitoring and the 14-day rule, and the Partner API step by step (for a SaaS or agency connecting its own customers' numbers). Use it to answer any question about how easyCoexistence works.
Instagram and Facebook 12
Posts, comments, private replies, DMs inside the 24-hour window, insights and comment-to-DM rules, on Instagram accounts and Facebook Pages.
Instagram MCP server for Claude and ChatGPT · Facebook MCP server for Claude and ChatGPT
publish_instagram_post- Publish to Instagram now: IMAGE (image_url), CAROUSEL (items, 2 to 10), REELS (video_url) or STORIES (image_url or video_url). Media must be at a public HTTPS URL Meta can download (JPEG for images). Videos can take minutes to process: a result with status processing is finished by easyCoexistence on its own. Meta caps API publishing at about 100 posts per 24h per account. To post later, pass scheduled_at. Every post gets a post_id (list_scheduled_posts).
publish_facebook_post- Publish to a Facebook Page now, or later with scheduled_at: text (message), a link, a photo (image_url) or a video (video_url).
list_social_posts- Recent posts of the account (Instagram media, Page posts or TikTok videos) with ids, captions and counts.
list_social_comments- Comments on one post (post_id from list_social_posts).
reply_to_comment- Reply to a comment publicly, or with private=true send the commenter a DM (Meta allows one private reply per comment, within 7 days of it).
hide_comment- Hide (or with hide=false, unhide) a comment on the account's post.
send_social_dm- Send a DM (Instagram Direct or Messenger) to someone who messaged the account in the last 24 hours. recipient_id is their id from the message event (relayed to the webhook destination).
get_social_insights- Insights for the account (default) or one post (object_id). Instagram account example: metrics ['reach','views','accounts_engaged','follows_and_unfollows'], period 'day', params {metric_type:'total_value'}. Post example: metrics ['reach','likes','comments','saved','shares','views'], no period. Pages: e.g. ['page_impressions_unique','page_post_engagements'], period 'day'. Meta renames metrics between versions: if one is rejected, the error lists the valid ones. TikTok account: e.g. ['followers_count','video_views','likes'], one row per day; one video (object_id = its item_id): e.g. ['video_views','likes','comments','shares'].
create_comment_rule- Comment-to-DM: when someone comments on the account's posts (or only post_id) with any of the keywords (empty = every comment), they automatically get dm_text as a DM, plus public_reply under their comment if set. Runs 24/7 on easyCoexistence, no agent needed. TikTok has no DMs: for TikTok accounts pass only public_reply. Confirm the wording with the user before creating.
list_comment_rules- The account's comment-to-DM rules with how many comments each has answered.
update_comment_rule- Pause or resume a comment-to-DM rule (active), or delete it (delete=true, after the user confirms).
remove_social_account- Remove a channel from easyCoexistence (the dashboard's Remove this channel, DELETE /api/v1/channels/:id): access is revoked at the network, the token is forgotten, its scheduled posts are canceled, its automations stop and billing stops at the end of the cycle. Coming back means connecting it again. Requires confirm=true, only after the user explicitly asks to remove that channel.
TikTok 3
Videos and photo posts, their publishing status, and the account's own comments.
TikTok MCP server for Claude and ChatGPT
publish_tiktok_post- Publish to a connected TikTok account: a video (video_url: MP4/MOV/WebM, 3 to 600 s, up to 1 GB, at least 360 px) or a photo post (image_urls: 1 to 35 JPEG or WebP; TikTok refuses PNG). Media must be at a public HTTPS URL. TikTok processes the post asynchronously: the result has a share_id, pass it to get_tiktok_publish_status. TikTok caps API posting at about 15 posts per day per account. To post later, pass scheduled_at. Every post gets a post_id (list_scheduled_posts).
get_tiktok_publish_status- Status of a TikTok post started with publish_tiktok_post (share_id from its result).
delete_tiktok_comment- Delete a comment on one of the TikTok account's videos (after the user confirms).
YouTube 6
Uploads with YouTube's scheduling, comments and their moderation, and YouTube Analytics.
upload_youtube_video- Upload a video to the connected YouTube channel from a public HTTPS URL. made_for_kids is required by YouTube. Default privacy is private. YouTube schedules natively: pass publish_at (ISO 8601) and the video goes public then. Note: until easyCoexistence's Google project passes YouTube's API audit, YouTube keeps API uploads private.
list_youtube_videos- The channel's uploads, newest first, with privacy, views, likes and comment counts.
list_youtube_comments- Comment threads on one video (video_id) or across the whole channel, newest first, with replies. moderation_status heldForReview or likelySpam lists comments waiting for the owner's review.
reply_to_youtube_comment- Reply publicly to a top-level comment as the channel.
moderate_youtube_comment- Approve (published), hold (heldForReview) or hide (rejected) a comment on the channel's videos. ban_author with rejected also hides that person's future comments.
get_youtube_analytics- YouTube Analytics for the channel or one video (video_id). Defaults: last 28 days; views, watch time, average view duration, likes, comments, subscribers gained and lost. dimensions e.g. 'day', 'video' (with sort '-views' and max_results), 'country'.
LinkedIn 7
Posts as a company Page or a member, comments, and Page statistics.
publish_linkedin_post- Publish a post on a LinkedIn Page or the member's own profile (account_id decides which). Text up to 3000 characters; optionally one image from a public HTTPS URL (JPG, PNG or GIF), or a link with its title (LinkedIn does not build previews for API posts). Hashtags work as plain #words. Confirm the wording with the user before publishing. To post later, pass scheduled_at. Every post gets a post_id (list_scheduled_posts).
list_linkedin_posts- A LinkedIn Page's posts, newest first (Page accounts only: LinkedIn does not let apps list a personal profile's posts). Paginate with start = next_start.
list_linkedin_comments- Comments on a LinkedIn post (post_id), or replies to one comment (comment_urn). Authors come back as URNs (urn:li:person:… or urn:li:organization:…).
comment_on_linkedin_post- Comment on a post as the Page or the member, or reply under a comment by passing parent_comment_urn. Confirm the wording with the user first.
delete_linkedin_comment- Delete a comment. A Page can remove any comment on its own posts (LinkedIn has no hide); a profile only its own comments. Irreversible: confirm with the user.
delete_linkedin_post- Delete a post the account published. Irreversible: confirm with the user.
get_linkedin_stats- LinkedIn analytics. Page accounts: follower count plus impressions, unique impressions, clicks, likes, comments, shares and engagement rate, lifetime or per DAY/MONTH between since and until, optionally for one post_id. Profile accounts: reactions and comment counts for a post_id.
Automations 19
Replies that run on their own, with a fixed text or AI, on numbers, Instagram, Facebook and TikTok.
set_inbound_mode- How a number's incoming messages flow. "managed": Meta delivers them to easyCoexistence, automations can answer, and they can be forwarded to forward_url signed with a secret only the user has (X-EC-Signature: t=<unix>,v1=<HMAC-SHA256 of "<t>.<body>">); the secret is returned once. Turning managed on removes a direct webhook destination. "direct": Meta delivers straight to the destination set with set_webhook_destination, easyCoexistence never sees the messages and automations stop. Pass forward_url alone to change forwarding on a managed number, null to stop it.
list_automations- The account's automations (optionally for one number), with their trigger, steps and status, plus which AI providers have a key saved. A number must be managed (set_inbound_mode) for its automations to run.
create_automation- Create an automation on a number (connection_id from list_numbers) or on an Instagram account, Facebook Page or TikTok account (its channel_id from list_social_accounts, passed as connection_id): a trigger and a flow of steps, with branches (condition, ai_decide), questions that wait for answers (ask), contact fields and tags, any API (http_request), AI agents (agent) and sub-flows (start_automation). The owner keeps answering from the phone app, and the automation pauses on a chat the owner answers. Only one automation answers each message; for one number answering everything with an agent, use match "any" and a single agent step. Test it with test_automation before relying on it.
update_automation- Change an automation. Fields left out keep their value; steps, when given, replace the whole list. connection_id moves it to another number or Instagram, Facebook or TikTok channel (its trigger and steps must fit there).
delete_automation- Delete an automation and its run history.
test_automation- Run an automation's steps on a sample message without sending anything to anyone. The AI step and the webhook really run, so the result shows the actual reply. Returns the run with every step's output.
list_automation_runs- An automation's recent runs (last 30 days), newest first: status (done, failed, skipped, waiting), skip_reason (human_active = the owner answered from the phone recently, window_closed = over 24 h since the customer wrote, ai_limit, superseded), every step's output and error, and AI tokens used.
get_automation_run- One run with every step's input, output, error and timing.
list_agents- The account's AI agents: instructions, model, tools, knowledge items, and which automations use each one.
list_files- The account's pictures and documents (a menu, a price list, photos) that automations and agents can send to customers: id, name, the note saying when to send it, kind (image | document) and the agent it belongs to, if any. Use an id in an automation step {type:"send_file", file_id, caption?}. An agent sends its own files by itself when the note fits the question, so a good note matters. Files are uploaded by the user in the dashboard (the agent's page, section Pictures and files), never through chat.
create_agent- Create an AI agent that answers people for the business, on the user's own AI key. Then add knowledge (add_agent_knowledge), test it (test_agent) and attach it: an automation step {type:"agent", agent_id}. Returns the agent.
update_agent- Change an agent. Fields left out keep their value; tools and settings, when given, replace the whole object.
delete_agent- Delete an agent and its knowledge. Refused while an automation uses it.
add_agent_knowledge- Teach an agent: pass title + content (FAQ, prices, policies, product list; up to 200,000 characters per item) or url: a public https page, or a public link to a file (PDF, Word .docx, Excel .xlsx, PowerPoint .pptx, text, CSV; 20 MB at most), read once now. Only the text is kept. A picture or a scanned PDF behind a link is written out by the agent's own model on the user's key. A file on the user's computer is uploaded in the dashboard instead (the agent's page, Knowledge, Upload a file). Up to 24,000 characters in all go whole into its prompt; past that the agent searches them, so give items clear titles. Pass knowledge_id with title + content to replace an item.
delete_agent_knowledge- Remove one knowledge item from an agent.
test_agent- Chat with an agent without sending anything: pass the conversation so far (messages, the last one from the customer) and optionally a contact {name, fields, tags}. Returns its answer, the tools it called (custom tools really call the user's API), and the contact as it changed it. Nothing is saved. Uses the user's AI key.
list_conversations- People who wrote to the user's managed numbers and social accounts, newest first: name, phone, channels, tags, fields, last message. Filter by q (name or phone), tag, or channel_id. Only numbers and accounts with an automation turned on keep their chats, from the moment it was turned on: an empty list on a number with no automation means nothing was kept, not that nobody wrote (create_automation starts keeping them). Messages are kept for the account's retention (30, 90 or 365 days); contacts stay.
get_conversation- One contact's messages, oldest first (in = the person, out = an automation or agent, with which one, echo = the owner from the phone app), their fields, tags, the agent's notes on them, and whether the bot is paused for them.
update_contact- Change a contact: fields {key: value or null to clear} (keys lower_case_digits_underscore), add_tags, remove_tags, and pause_hours (automatic replies off on their chats for that long; 0 switches them back on). A paused_until in the year 9999 means off until someone switches them on.
Partner API setup 5
For software that connects its own customers: the key, the events URL and hosted connect links.
get_partner_setup- Partner API setup status, for a user whose own software or agency platform will let ITS customers connect numbers (hosted connect links): whether billing is ready, whether an API key exists, where status events go, and the next step. Call this first when the user wants to set that up, then walk them through it with create_api_key, set_partner_events_url and create_connect_link.
create_api_key- Create the account's Partner API key (ec_live_…) and return it ONCE. The user must store it as a server-side secret. One key per account: if one exists this refuses unless replace_existing=true, because replacing revokes the old key immediately. Only pass replace_existing=true after the user explicitly confirms.
revoke_api_key- Revoke the account's Partner API key (for a leaked key or to stop the integration). Every request with it fails from then on. Requires confirm=true, only after the user explicitly asks.
set_partner_events_url- Set the HTTPS URL that receives Partner API status events (connection.connected, .disconnected, .sending_blocked and the rest; the reply lists every event this account gets) and return its signing secret ONCE, with how to verify the X-EC-Signature header. url=null turns events off. When a URL is already set, a new one needs replace_secret=true: it issues a new secret, which breaks the live integration until the user's backend has it.
create_connect_link- Create a hosted connect link (a Partner API connect session) for one of the user's customers, the same as POST /api/v1/connect-sessions: returns a URL on easycoexistence.com to send the customer, valid 1 hour. The customer runs Meta's popup there and is sent to redirect_url. The resulting number belongs to and is billed to this account. Use it to test a Partner API setup or to onboard a customer by hand.
Connect your first channel in two minutes.
No platform reviews to wait for. Connect WhatsApp, Instagram, TikTok or another channel, then ask your AI to post, reply or report, and watch it work.
- 3 days free
- Cancel any time
- Official APIs only
- Monitored 24/7
Frequently asked questions
How many tools does the easyCoexistence MCP server have?
72 today, listed on this page by network and read from the server's own definitions, so the list is always current.
Does one connector cover every network?
Yes. Add https://easycoexistence.com/api/mcp once and sign in; the tools reach every number and account connected to your easyCoexistence account.
Can the assistant call an endpoint no tool covers?
On TikTok, from your own code: get_social_credentials hands it the account's token for any endpoint of TikTok's API for Business. On Instagram and Facebook, no: their tokens stay with easyCoexistence, so the assistant works through the named tools.
How much does it cost?
The connector is included. Connections cost US$ 9 to US$ 0.75 per connection per month, falling as you add connections, the same on every network, with the first 3 days free.