Model Context Protocol · REST API v1
The social media stack built for AI agents
Let your assistant list workspaces, pick connected accounts, draft and schedule posts, sync and moderate comments, and refresh analytics—using the same product logic as the PostSyncer dashboard. Works with MCP clients like Claude, Cursor, ChatGPT connectors, and autonomous stacks such as OpenClaw.
Why agents use PostSyncer
Protocol-native MCP
Thirty-plus structured tools—not brittle HTML scraping. Your model gets schemas, validation, and consistent JSON aligned with API v1.
Multi-network publishing
One workflow for Instagram, TikTok, YouTube, X, LinkedIn, Facebook, Threads, Bluesky, Pinterest, Telegram, Mastodon, and more—through the accounts you already connected in PostSyncer.
Comments & analytics
Go beyond “post only”: sync threads, reply, hide spam, delete when appropriate, and pull workspace, post, or account analytics on demand.
MCP server endpoint
Use Streamable HTTP against https://postsyncer.com/mcp with
Authorization: Bearer <personal access
token>.
Token abilities mirror REST: workspaces, accounts,
labels, campaigns, posts.
Technical setup for editors and gateways: Integrating clients.
MCP tool directory
| Area | MCP tools |
|---|---|
| Workspaces |
list-workspaces
|
| Accounts |
list-accounts, delete-account
|
| Labels |
list-labels, create-label, get-label, update-label, delete-label
|
| Campaigns |
list-campaigns, create-campaign, get-campaign, update-campaign, delete-campaign
|
| Posts |
list-posts, create-post, get-post, update-post, delete-post
|
| Comments |
list-comments, sync-comments-from-platforms, create-comment, get-comment, update-comment, delete-comment, hide-comment
|
| Analytics |
get-analytics-summary, get-analytics-workspace, get-analytics-post, get-analytics-account, sync-post-analytics
|
Need column-by-column detail? See the tools reference in the API docs.
favorite accounts
Invest in
Growth
,
Not Just Tools
Simple pricing for creators, teams, and agencies.
No per-user fees. No hidden limits. Start free.
Starter Plan
For solo creators and freelancers
Pro
Growing teams and agencies
Pro Plus
Best ValueAdvanced AI tools for businesses and teams
Still deciding?
View full feature comparisonCompare all plans
See how each plan stacks up. All plans include a 3-day free trial.
Frequently Asked Questions
Common questions about PostSyncer for AI agents and MCP
PostSyncer MCP is a Model Context Protocol server that exposes the same capabilities as PostSyncer’s REST API v1: workspaces, connected accounts, labels, campaigns, posts, comment moderation, and analytics. Your AI assistant calls real tools instead of copy-pasting API examples.
The PostSyncer MCP server URL is https://postsyncer.com/mcp (Streamable HTTP). Authenticate with Authorization: Bearer <token> using a Sanctum personal access token from your PostSyncer account—the same token style as the REST API.
The PostSyncer server registers over thirty tools, including listing and managing posts, comments (including sync and hide), campaigns, labels, workspaces, accounts, and analytics (summary, workspace, post, account, plus sync). Destructive tools such as delete-post or delete-account should only run when the user clearly asked.
No. MCP and the REST API talk to the same backend. Use MCP when your client supports it (Claude, Cursor, ChatGPT connectors, OpenClaw, and others). Use REST when you are building custom backends, webhooks, or languages without MCP.
Match the REST API scopes you need: workspaces, accounts, labels, campaigns, and posts. Listing or editing posts, comments, or analytics requires the posts ability. Start with the minimum scopes and add more only when needed.