Skip to main content
Connecting takes about a minute. You do it once per app, and the connection then stays active until you revoke it.

First: get your API key

1

Open the Developer page

In ChatSyncs, go to Control Panel → Developer (direct link).
2

Copy your API key

It’s shown at the top of the page as Your API key.
Treat this key like your password. Anyone holding it can send WhatsApp messages and read your customer data. Never paste it into a chat message, a support ticket, or a public repository — only into the connect screens below.

Claude Desktop and claude.ai

The easiest route: you’ll be shown a page that asks for your key.
1

Open connector settings

In Claude, go to Settings → Connectors and choose Add custom connector.
2

Enter the ChatSyncs server URL

Paste this and click Add:
3

Paste your API key

Claude opens a ChatSyncs page in your browser asking for your API key. Paste it and click Connect.We check the key with ChatSyncs straight away, so you’ll see “Connected as <your business name>” if it worked — and a clear error if the key was wrong, rather than a connection that silently fails later.
4

Done

You’re returned to Claude and the ChatSyncs tools are available. Try asking “What WhatsApp numbers are on my ChatSyncs account?”
Only paste your key into a page whose address starts with https://mcp.chatsyncs.com. If the address is anything else, close it — someone is trying to collect your key.

Claude Code

One command, with your key sent as a header:
Then check it:

Other MCP apps

Any app that supports MCP over HTTP works. Use: If your app’s settings screen has no place for a header, you can put the key in the URL instead:
Prefer the header if your app offers one. A key inside a URL can end up recorded in server logs and browser history. Use the URL form only when there’s no alternative, and regenerate your key if you think it has been exposed.

Check that it worked

Ask your assistant:
“Show me my ChatSyncs account details.”
You should get your plan name, your usage, and each connected WhatsApp number. If you get an error instead, see Troubleshooting.

Security

In your AI assistant’s own credential storage — on your device, or in your Claude account. The ChatSyncs MCP server keeps no database of customer keys: your key arrives with each request, is used, and is discarded.
Go to Control Panel → Developer in ChatSyncs and regenerate your API key. Every assistant still holding the old key stops working immediately. Then reconnect with the new key wherever you still want access.You can also remove the connector in your assistant’s settings, which deletes its copy of the key.
No. Claude requests your approval before each action. Actions that delete a contact or block someone are marked so you get a stronger warning.
No. Only the actions you approve reach ChatSyncs, as ordinary API calls. Your chat with the assistant stays between you and your AI provider.
Not from your side — a ChatSyncs API key carries all the permissions of the account it came from; there is no read-only key. The practical control is that Claude asks before every action, so nothing is sent without you approving it.

Frequently asked

No. The server is hosted by ChatSyncs. You only add its address in your assistant’s settings.
Yes — add it as a second connector with the other account’s API key. Give them distinct names so you can tell them apart.
If you have one number, it’s used automatically. With several, the assistant lists them and asks which to use — so say which number you mean, e.g. “send it from the support number”.
Until you revoke it. Claude refreshes its access quietly in the background; you won’t be asked to paste your key again.