Skip to main content
Any app that can use a remote MCP server over HTTP can use ChatSyncs. These are the ones customers ask about most. They are less polished than the main guides, so expect to edit a settings file.

​
Before you start

  • Your ChatSyncs API key, from the API Developer Console (how).
  • An app version with remote MCP over HTTP. Update the app first; older versions often only support SSE, which ChatSyncs doesn’t.
  • Comfort editing a settings file. Most of these apps need one.

​
The settings, for any app

​
App by app

Open the ⋯ menu at the top right of the Cascade panel and go to the MCPs section to open mcp_config.json. Add:
It signs in through the ChatSyncs page. ("url" works in place of "serverUrl" too.) To use your key instead, add "headers": { "Authorization": "Bearer YOUR_CHATSYNCS_API_KEY" } next to serverUrl. On Enterprise, an admin must turn MCP on first.
Go to Settings → AI → MCP Servers, click Add Server, choose Add Remote Server, and use the URL https://mcp.chatsyncs.com/mcp. Or add this to your Zed settings:
With no Authorization header set, Zed opens the ChatSyncs sign-in page for you. To use your key instead, add "headers": { "Authorization": "Bearer YOUR_CHATSYNCS_API_KEY" }.
Cline’s documentation doesn’t describe browser sign-in for remote servers, so use your key. In the Cline panel, click the MCP Servers icon, open the Configure tab, and click Configure MCP Servers. That opens the settings file (cline_mcp_settings.json). Add:
Keep "autoApprove": [] empty so Cline always asks before sending a message. The Remote Servers tab has no box for a header, so if you add it there instead, choose the Streamable HTTP transport (not SSE) and you’d have to use the key-in-address form (last resort, see below).
In a scenario, add the MCP Client module and click Create a connection. In MCP Server, choose + New MCP Server and enter the URL https://mcp.chatsyncs.com/mcp. Then either sign in through the ChatSyncs page when Make asks, or paste your API key into API Key / Access token.
It depends on your n8n version. n8n’s own documentation for the MCP Client Tool node still describes only an SSE Endpoint, which ChatSyncs doesn’t support. Use the node only if yours lets you choose an HTTP Streamable transport. Set the endpoint to https://mcp.chatsyncs.com/mcp and Authentication to Bearer, with your API key as the token.If your n8n only offers an SSE endpoint, call ChatSyncs with the HTTP API integration or the Developer API instead.

​
Check it worked

Ask the app’s assistant:
“List my WhatsApp templates.”
If it lists your templates, you’re connected.

​
Disconnect

Delete the chatsyncs entry from the app’s settings (or the connection in Make or n8n). If you used the header or key-in-URL method, the key was in that app’s settings, so regenerate it when you stop using the app.

​
Last resort: the key in the address

For an app that accepts only a URL (no browser sign-in, no headers):
  • The address is the password. Anyone who sees it (in a screenshot, a shared file, a log) gets full access to your account.
  • Addresses get logged. ChatSyncs’ code never writes your key to its logs, but the full address can still be recorded by hosting and network logs (including ChatSyncs’ hosting provider) and by your app.
  • A wrong key looks connected. The error only shows on your first request.
Regenerate your key when you stop using that app, and immediately if the address may have been seen. Full detail: How connecting works.

​
Frequently asked

No. ChatSyncs serves MCP over HTTP only (POST requests to /mcp), not the older SSE transport. Check whether the app has an update with “Streamable HTTP” support.
Leave both empty. ChatSyncs registers each app automatically. If the app won’t continue without them, use the header method instead.
No need: it’s hosted at mcp.chatsyncs.com for every customer, and your app only needs the address.