Skip to main content

​
PostSyncer MCP

PostSyncer exposes a Model Context Protocol (MCP) server so AI assistants and coding agents can manage social content with tools (structured actions) instead of ad-hoc HTTP calls.
Create your token in app.postsyncer.com → Settings → API Integrations. MCP uses the same Bearer personal access tokens and abilities as REST (workspaces, accounts, labels, campaigns, posts).

​
Endpoint

ItemValue
MCP URLhttps://postsyncer.com/mcp
Auth headerAuthorization: Bearer YOUR_TOKEN
TransportStreamable HTTP
Treat tokens like production passwords. They can publish posts, delete content, and disconnect accounts when matching tools are invoked.

​
What the server does

The PostSyncer MCP server (name PostSyncer, version 1.0.0) implements tools that mirror API v1:
  • Workspaces — discover context and connected accounts.
  • Accounts — list connected social profiles; disconnect when needed.
  • Labels & campaigns — organize content.
  • Posts — create, list, read, update, delete, schedule.
  • Comments — list, sync from platforms, create replies, update, delete, hide.
  • Analytics — summary, workspace, post, and account metrics; sync post analytics.
Server instructions remind models to start with list-workspaces and list-accounts, respect workspace boundaries, and only run delete-* tools when the user clearly asked.

​
Relationship to the REST API

  • Parity: MCP tools call the same backend rules as https://postsyncer.com/api/v1.
  • Choose MCP when your client supports Streamable HTTP and Bearer headers (see Client setup).
  • Choose REST for servers, webhooks, mobile apps, or languages without MCP.

​
More on PostSyncer.com

​
Next steps

Client setup

Claude Desktop, Claude Code, Cursor, and other Streamable HTTP clients.

Tools reference

Full list of MCP tool names grouped by domain.