The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the PostSyncer listing page.
Schedule, publish, and analyze social media posts from Claude Code, Claude Cowork, Cursor, and Grok Build — across 11 platforms: X (Twitter), Instagram, Facebook, LinkedIn, TikTok, YouTube, Threads, Bluesky, Mastodon, Pinterest, and Telegram.
The plugin bundles the official PostSyncer MCP server (https://postsyncer.com/mcp) plus a skill that teaches Claude the full PostSyncer workflow: workspaces, connected accounts, posts (publish now / schedule / draft / repeat), threads, first comments, media library, campaigns, labels, comment moderation, and performance analytics.
From the Claude plugin directory:
Or directly from this repo:
Install from the Cursor Marketplace, or clone this repo into ~/.cursor/plugins/local/postsyncer and run Developer: Reload Window. The manifest lives in .cursor-plugin/plugin.json.
The Codex manifest lives in .codex-plugin/plugin.json; the plugin is also listed in the ChatGPT/Codex plugin directory as PostSyncer.
Point your client at https://postsyncer.com/mcp (Streamable HTTP). The server is published in the official MCP Registry as io.github.PostSyncer/postsyncer.
Install from the xAI plugin marketplace (postsyncer). The Claude-format manifest in .claude-plugin/plugin.json is used as-is.
Two options:
/mcp inside Claude Code, select postsyncer, and click authenticate. You log in to PostSyncer once in the browser; no token to paste.workspaces, accounts, labels, campaigns, posts) and configure it as a Bearer token for the postsyncer MCP server.| Component | Description |
|---|---|
| MCP server | Remote HTTP server at postsyncer.com/mcp with ~50 tools mirroring PostSyncer REST API v1 |
postsyncer skill | Workflow guidance: discovery, media prep, posting rules, threads, first comments, scheduling, repeats, analytics, moderation |
This plugin ships no scripts, hooks, or local binaries. Its only component besides the skill file is a remote MCP server:
| Endpoint | Purpose |
|---|---|
https://postsyncer.com/mcp | The PostSyncer MCP server (Streamable HTTP). All tool calls go here. |
https://postsyncer.com/oauth/* | OAuth 2.0 authorization when you choose the OAuth login flow. |
Credentials: either an OAuth grant issued during the login flow, or a PostSyncer API token you create yourself and configure as a Bearer token. The plugin never reads environment variables, files, or secrets from your machine, and the MCP server only accesses the PostSyncer workspaces the authenticated account can see.
MIT