Skip to main content
The ChatSyncs MCP server connects your ChatSyncs account to the AI assistant you already use: Claude, ChatGPT and others. Once connected, you run your WhatsApp business by asking in plain English:
“Send Rahul a message saying his order shipped today.” “Who messaged us in the last hour and hasn’t had a reply?” “Tag everyone who asked about pricing as Hot Lead and assign them to Priya.”
The assistant works out which ChatSyncs actions those need, shows you what it’s about to do, and does it on your account.
MCP stands for Model Context Protocol, an open standard that lets AI assistants use real tools. You don’t need to understand it. You add ChatSyncs once in your AI app, paste your ChatSyncs API key on a ChatSyncs page, and the assistant gains a set of ChatSyncs abilities.

​
Connect your AI app

Claude

Web, desktop and mobile. Easiest; works on the Free plan.

ChatGPT

Web. Every action on Business, Enterprise or Edu.

Claude Code

One terminal command.

OpenAI Codex

Codex CLI, IDE extension and ChatGPT desktop.

Cursor

The Cursor editor’s Agent.

VS Code + Copilot

GitHub Copilot Chat.

Gemini CLI

Google’s terminal agent.

Other apps

Windsurf, Zed, Cline, n8n, Make.
Not sure which? Compare them: if you’re not technical, use Claude or ChatGPT in your browser.

​
What you need first

1

A ChatSyncs account with a connected WhatsApp number

The assistant acts on your existing setup. If you haven’t connected a number yet, start with Connect your number to ChatSyncs.
2

Your ChatSyncs API key

From the API Developer Console. See Get your API key.
3

An AI app that supports MCP

Any of the apps above. Each has a page with the exact clicks.

​
Is this the same as the Developer API?

It’s the same power, without the code. The Developer API is for developers who write a program that calls ChatSyncs. The MCP server is that API already wrapped up, so an AI assistant can use it for you.

​
What the assistant can do

Messaging

Send text, files, images and approved templates. Send messages with tappable reply buttons. Check whether a message was delivered or read.

Contacts

Look someone up, add a contact, update their details, read the conversation history, leave an internal note.

Organising

Create labels and apply them, set custom fields, enrol people in follow-up sequences, update deals, resolve or archive conversations.

Team and shop

Assign a chat to a team member, trigger a chatbot flow, list catalog orders and move them to Shipped or Delivered.
There are 43 abilities in total. The full list is on the Tools reference, and Things to ask has prompts that work.

​
The 24-hour rule still applies

This is WhatsApp’s rule, not ChatSyncs’, and the AI can’t get around it:
  • Within 24 hours of a customer messaging you, you can reply with anything: free text, images, files, buttons.
  • After that, only an approved template will be delivered.
So “message everyone on my list about the sale” needs an approved marketing template. If you ask for plain text to someone who last messaged three days ago, WhatsApp rejects it. The assistant knows this rule and normally tells you before trying.
Messages sent through the assistant are real. They reach real customers, use your message credits, and can’t be unsent. Your AI app asks before anything that sends or changes something. Read what it proposes before you approve, and be careful with “always allow” options.

​
What it costs

Nothing extra from ChatSyncs. The MCP server uses your existing plan and its limits: your subscriber cap, your message credits, and Meta’s own messaging charges. Your AI app’s own plan is separate (see which plans work).

​
What the AI can’t do

  • Broadcast to a whole list in one step. There’s no bulk-send ability, on purpose. Use Broadcasting for campaigns.
  • Create or approve message templates. Make those in ChatSyncs; the assistant can then send the approved ones.
  • Change your billing, plan or account settings.
  • Act on its own. It only does something when you ask, in a chat where ChatSyncs is turned on.

​
Frequently asked

No. With Claude or ChatGPT you click through a few settings and paste your API key into a ChatSyncs page. There’s no code anywhere in that process.
With browser sign-in, ChatSyncs checks your key when you connect and your AI app stores it. The ChatSyncs MCP server keeps no copy. You can cut off every connected app at once by regenerating the key. See Get your API key.
Yes. Each person connects in their own AI app with an API key from your ChatSyncs account. A key carries the full permissions of the account it came from.
Not by default. Claude, ChatGPT, Cursor, VS Code and the command-line apps all ask before an action that sends or changes something. Deleting a contact and blocking a conversation are marked as destructive, so apps warn you more firmly.
Claude, ChatGPT, Claude Code, OpenAI Codex, Cursor, VS Code with GitHub Copilot and Gemini CLI have step-by-step guides. Windsurf, Zed, Cline, Make and n8n are covered in Other apps. Any app that supports remote MCP over HTTP can connect.
No. Your ChatSyncs chatbots keep answering customers automatically, around the clock. The MCP server is for you: a way to run your account by asking instead of clicking.