Skip to main content
The fastest way to add the SocialSyncs MCP server to Claude Code is with a single terminal command: 
claude mcp add socialsyncs \
  --transport http \
  --header "Authorization: Bearer your-api-key" \
  "https://api.socialsyncs.co/mcp"
Or use the API-key-in-URL form (no header needed): 
claude mcp add socialsyncs --transport http "https://api.socialsyncs.co/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: 
{
  "mcpServers": {
    "socialsyncs": {
      "type": "http",
      "url": "https://api.socialsyncs.co/mcp/your-api-key"
    }
  }
}
The "type": "http" field is required in .mcp.json. Without it, Claude Code silently skips the server and it will not appear in /mcp.
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: 
claude mcp add socialsyncs \
  --transport http \
  --header "Authorization: Bearer your-api-key" \
  "http://localhost:3000/mcp"
Or via .mcp.json: 
{
  "mcpServers": {
    "socialsyncs": {
      "type": "http",
      "url": "http://localhost:3000/mcp/your-api-key"
    }
  }
}
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.

​
Claude Desktop

Add the following to your Claude Desktop MCP configuration file:
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
  "mcpServers": {
    "socialsyncs": {
      "type": "http",
      "url": "https://api.socialsyncs.co/mcp/your-api-key"
    }
  }
}
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: 
claude mcp add socialsyncs --transport http \
  --url https://api.socialsyncs.co/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://api.socialsyncs.co/mcp/your-api-key

​
Other MCP Clients

Any MCP-compatible client can connect to SocialSyncs. Use the streamable HTTP transport:
  • URL: https://api.socialsyncs.co/mcp/your-api-key
  • Transport: Streamable HTTP
Or, if your client supports Bearer token authentication:
  • URL: https://api.socialsyncs.co/mcp
  • Transport: Streamable HTTP
  • Authorization: Bearer your-api-key

​
Self-Hosted

For self-hosted instances, replace https://api.socialsyncs.co 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.