Skip to main content

​
Client setup

Configure your AI client to connect to the PostSyncer MCP server.
Create a token first: open app.postsyncer.com → Settings → API Integrations, click Create, and copy the key. It is a Sanctum personal access token—same as the REST API. Choose abilities (workspaces, accounts, labels, campaigns, posts) to match what you need; see Authentication.

​
Connection details

SettingValue
URLhttps://postsyncer.com/mcp
TransportStreamable HTTP
AuthorizationBearer YOUR_TOKEN (send as the Authorization HTTP header)
Replace YOUR_TOKEN with the token from API Integrations (include the Bearer prefix in the header value).

​
Claude Desktop

Add PostSyncer under mcpServers in your Claude Desktop MCP configuration file.
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
  "mcpServers": {
    "postsyncer": {
      "url": "https://postsyncer.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE",
        "Accept": "application/json"
      }
    }
  }
}
Restart Claude Desktop after saving. If your Claude build uses different keys for remote servers, check the latest Model Context Protocol and Anthropic documentation for your version.

​
Claude Code

Add PostSyncer as an MCP server in your Claude Code MCP configuration (same mcpServers shape as Claude Desktop): 
{
  "mcpServers": {
    "postsyncer": {
      "url": "https://postsyncer.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE",
        "Accept": "application/json"
      }
    }
  }
}
Use the config location and reload steps described in the current Claude Code docs for your install.

​
Cursor

  1. Open Cursor Settings → MCP and add a new server, or edit your global MCP config file (commonly ~/.cursor/mcp.json on macOS/Linux, or %USERPROFILE%\.cursor\mcp.json on Windows).
  2. Use HTTP / Streamable HTTP transport, URL https://postsyncer.com/mcp, and headers as below.
{
  "mcpServers": {
    "postsyncer": {
      "transport": "http",
      "url": "https://postsyncer.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE",
        "Accept": "application/json"
      }
    }
  }
}
Restart Cursor (or reload MCP) so the tool list refreshes.

​
Other MCP clients

Any MCP-compatible client that supports Streamable HTTP (or remote HTTP) and custom headers can use PostSyncer:
  • URL: https://postsyncer.com/mcp
  • Transport: Streamable HTTP
  • Header: Authorization: Bearer YOUR_TOKEN_HERE
  • Recommended: Accept: application/json
Follow that product’s own docs for where to enter the URL and headers.

​
Verify the connection

After connecting, ask your assistant to run a read-only tool, for example:
List my workspaces
If setup is correct, it should call list-workspaces and return data. Then try list my connected accounts to exercise list-accounts.

​
Troubleshooting

SymptomWhat to check
401 / UnauthorizedToken missing, revoked, or Authorization not formatted as Bearer plus your token (no typos or extra spaces). Create a new token from API Integrations if unsure.
Missing toolsToken abilities: you need posts for post, comment, and analytics tools; workspaces and accounts to discover IDs.
Empty or partial toolsUpdate the client; some older builds mishandle tools/list pagination.

​
See also