> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chatsyncs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect other apps to ChatSyncs (Windsurf, Zed, Cline, n8n, Make)

> How to connect ChatSyncs to MCP apps without their own guide (Windsurf / Devin Desktop, Zed, Cline, n8n's MCP Client Tool and Make's MCP Client module), with the exact config for each: server URL https://mcp.chatsyncs.com/mcp, OAuth sign-in or an Authorization Bearer header, and when the key-in-URL address is the only option. Also says which apps cannot connect (SSE-only clients). Use when a customer asks whether a particular AI tool or automation platform works with the ChatSyncs MCP server.

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](/mcp/choose-an-app),
so expect to edit a settings file.

## Before you start

* **Your ChatSyncs API key**, from the
  [API Developer Console](https://platform.chatsyncs.com/api/developer/console)
  ([how](/mcp/api-key)).
* **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

| Setting | Value |
| - | - |
| Server URL | `https://mcp.chatsyncs.com/mcp` |
| Transport | HTTP / "Streamable HTTP". **SSE-only apps can't connect.** |
| Sign-in (best) | OAuth with automatic registration. Leave client ID and secret empty. |
| Sign-in (alternative) | Header `Authorization: Bearer YOUR_CHATSYNCS_API_KEY` |
| Last resort | `https://mcp.chatsyncs.com/mcp/k/YOUR_CHATSYNCS_API_KEY`, see the warning below |

## App by app

| App | Works? | How it signs in |
| - | - | - |
| Windsurf / Devin Desktop | Yes | Browser sign-in or header |
| Zed | Yes | Browser sign-in, or header |
| Cline | Yes | Header in the settings file (the add-server form has no header box) |
| Make | Yes | OAuth, or the key in the **API Key / Access token** box |
| n8n | Only if your node offers **HTTP Streamable** | Bearer header |

<AccordionGroup>
  <Accordion title="Windsurf / Devin Desktop">
    Open the **⋯** menu at the top right of the Cascade panel and go to the MCPs section to open
    `mcp_config.json`. Add:

    ```json theme={null}
    {
      "mcpServers": {
        "chatsyncs": {
          "serverUrl": "https://mcp.chatsyncs.com/mcp"
        }
      }
    }
    ```

    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.
  </Accordion>

  <Accordion title="Zed">
    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:

    ```json theme={null}
    {
      "context_servers": {
        "chatsyncs": {
          "url": "https://mcp.chatsyncs.com/mcp"
        }
      }
    }
    ```

    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" }`.
  </Accordion>

  <Accordion title="Cline">
    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:

    ```json theme={null}
    {
      "mcpServers": {
        "chatsyncs": {
          "type": "streamableHttp",
          "url": "https://mcp.chatsyncs.com/mcp",
          "headers": {
            "Authorization": "Bearer YOUR_CHATSYNCS_API_KEY"
          },
          "disabled": false,
          "autoApprove": []
        }
      }
    }
    ```

    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).
  </Accordion>

  <Accordion title="Make">
    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**.
  </Accordion>

  <Accordion title="n8n">
    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](/learn/chatsyncs-integrations/http-api-integration-in-chatsyncs) or
    the [Developer API](/developer-api/introduction) instead.
  </Accordion>
</AccordionGroup>

## 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](/mcp/api-key#revoke-access-regenerate-the-key) 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):

```
https://mcp.chatsyncs.com/mcp/k/YOUR_CHATSYNCS_API_KEY
```

<Warning>
  * **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](/mcp/connect#last-resort-the-key-in-the-address).
</Warning>

## Frequently asked

<AccordionGroup>
  <Accordion title="My app only supports SSE. Can I use it?">
    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.
  </Accordion>

  <Accordion title="My app asks for a client ID and secret">
    Leave both empty. ChatSyncs registers each app automatically. If the app won't continue
    without them, use the header method instead.
  </Accordion>

  <Accordion title="Can I run the ChatSyncs MCP server on my own computer?">
    No need: it's hosted at `mcp.chatsyncs.com` for every customer, and your app only needs the
    address.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.