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

# Client Setup

> Configure your AI client to connect to the SocialSyncs MCP server

## Claude Code (Recommended)

The fastest way to add the SocialSyncs MCP server to Claude Code is with a single terminal command:

```bash theme={null}
claude mcp add socialsyncs \
  --transport http \
  --header "Authorization: Bearer your-api-key" \
  "https://app.socialsyncs.co/api/mcp"
```

Or use the API-key-in-URL form (no header needed):

```bash theme={null}
claude mcp add socialsyncs --transport http "https://app.socialsyncs.co/api/mcp/your-api-key"
```

Replace `your-api-key` with your key from **Settings → Public API**.

Alternatively, add it manually to `.mcp.json` in your project root:

```json theme={null}
{
  "mcpServers": {
    "socialsyncs": {
      "type": "http",
      "url": "https://app.socialsyncs.co/api/mcp/your-api-key"
    }
  }
}
```

<Warning>
  The `"type": "http"` field is required in `.mcp.json`. Without it, Claude Code
  silently skips the server and it will not appear in `/mcp`.
</Warning>

After saving, restart Claude Code or run `/mcp` to reload.

## Testing Against a Local Instance

If you are running SocialSyncs locally (e.g., `localhost:3000`), point Claude Code at your local backend instead:

```bash theme={null}
claude mcp add socialsyncs \
  --transport http \
  --header "Authorization: Bearer your-api-key" \
  "http://localhost:3000/mcp"
```

Or via `.mcp.json`:

```json theme={null}
{
  "mcpServers": {
    "socialsyncs": {
      "type": "http",
      "url": "http://localhost:3000/mcp/your-api-key"
    }
  }
}
```

<Note>
  Your backend must be running before Claude Code tries to use the tools. Start it with `pnpm dev` from the repo root, then restart Claude Code.
</Note>

## Claude Desktop

Add the following to your Claude Desktop MCP configuration file:

<Tabs>
  <Tab title="macOS">
    Edit `~/Library/Application Support/Claude/claude_desktop_config.json`:

    ```json theme={null}
    {
      "mcpServers": {
        "socialsyncs": {
          "type": "http",
          "url": "https://app.socialsyncs.co/api/mcp/your-api-key"
        }
      }
    }
    ```
  </Tab>

  <Tab title="Windows">
    Edit `%APPDATA%\Claude\claude_desktop_config.json`:

    ```json theme={null}
    {
      "mcpServers": {
        "socialsyncs": {
          "type": "http",
          "url": "https://app.socialsyncs.co/api/mcp/your-api-key"
        }
      }
    }
    ```
  </Tab>
</Tabs>

Replace `your-api-key` with your actual API key from **Settings > Developers > Public API**.

The Bearer-token transport works too — pick whichever your client supports better. Both authenticate the same way:

```bash theme={null}
claude mcp add socialsyncs --transport http \
  --url https://app.socialsyncs.co/api/mcp \
  --header "Authorization: Bearer your-api-key"
```

## Cursor

In Cursor, go to **Settings > MCP** and add a new server:

* **Name:** socialsyncs
* **Type:** HTTP
* **URL:** `https://app.socialsyncs.co/api/mcp/your-api-key`

## Other MCP Clients

Any MCP-compatible client can connect to SocialSyncs. Use the streamable HTTP transport:

* **URL:** `https://app.socialsyncs.co/api/mcp/your-api-key`
* **Transport:** Streamable HTTP

Or, if your client supports Bearer token authentication:

* **URL:** `https://app.socialsyncs.co/api/mcp`
* **Transport:** Streamable HTTP
* **Authorization:** `Bearer your-api-key`

## Self-Hosted

For self-hosted instances, replace `https://app.socialsyncs.co/api` with your `NEXT_PUBLIC_BACKEND_URL`:

```
https://your-server.com/mcp/your-api-key
```

## Verify Connection

Once connected, ask your AI agent:

> "List my connected social media accounts"

If the connection is working, the agent will call the `integrationList` tool and return your connected accounts.