PostSyncer

io.github.PostSyncerPublished by GitHub account PostSyncerv1.0.1Updated Oct 24, 2026

Schedule, publish, and analyze social media posts across 11 platforms from any MCP client.

Overview

AI-generated overview

A remote MCP server that lets an assistant schedule, publish and analyze social media posts across 11 platforms from a connected PostSyncer account.

What you can do
List connected social accounts and workspaces, labels and campaigns, and inspect comment moderation queues and performance analytics across workspaces. Create posts as publish-now, scheduled, draft or repeating, including threads and first comments. Upload media to the media library and prepare posts with images, such as carousels.
When to use it
Useful when you want an assistant to draft, schedule or repeat social posts across several networks, or to report on how recent posts performed, without switching between platform dashboards.
Requirements
A remote Streamable HTTP endpoint at postsyncer.com/mcp; no local runtime or packages. A PostSyncer account, authenticated either through OAuth in the browser or with a PostSyncer API token created in the app and sent as a Bearer token, scoped to the abilities you need. Network access to postsyncer.com.
Before you install
The server can publish, schedule and repeat posts and upload media to live social accounts, so review content before it goes out. It also handles comment moderation and account data. Access is limited to the workspaces the authenticated account can see. An API token grants the abilities chosen when creating it, so keep them minimal; the OAuth grant or token is a credential to protect.

Installation

In SourceWeft

  1. Open PostSyncer in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.PostSyncer%2Fpostsyncer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "postsyncer": {
      "type": "http",
      "url": "https://postsyncer.com/mcp"
    }
  }
}

README

PostSyncer Plugin

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.

Install

From the Claude plugin directory:

bash
claude plugin install postsyncer

Or directly from this repo:

bash
claude plugin marketplace add PostSyncer/claude-pluginclaude plugin install postsyncer@postsyncer

Cursor

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.

Codex

bash
codex plugin marketplace add PostSyncer/claude-plugin

The Codex manifest lives in .codex-plugin/plugin.json; the plugin is also listed in the ChatGPT/Codex plugin directory as PostSyncer.

Gemini CLI

bash
gemini extensions install https://github.com/PostSyncer/claude-plugin

Any MCP client

Point your client at https://postsyncer.com/mcp (Streamable HTTP). The server is published in the official MCP Registry as io.github.PostSyncer/postsyncer.

Grok Build

Install from the xAI plugin marketplace (postsyncer). The Claude-format manifest in .claude-plugin/plugin.json is used as-is.

Authenticate

Two options:

  1. OAuth (recommended) — run /mcp inside Claude Code, select postsyncer, and click authenticate. You log in to PostSyncer once in the browser; no token to paste.
  2. API token — create a token in the PostSyncer app (Settings → API) with the abilities you need (workspaces, accounts, labels, campaigns, posts) and configure it as a Bearer token for the postsyncer MCP server.

Try it

  • "List my connected social accounts"
  • "Schedule a post to LinkedIn and X for tomorrow at 9am announcing our new feature"
  • "Upload these product shots and draft an Instagram carousel with the link in a first comment"
  • "How did last week's posts perform across all my workspaces?"
  • "Repeat this post every Monday for a month"

What's included

ComponentDescription
MCP serverRemote HTTP server at postsyncer.com/mcp with ~50 tools mirroring PostSyncer REST API v1
postsyncer skillWorkflow guidance: discovery, media prep, posting rules, threads, first comments, scheduling, repeats, analytics, moderation

Network and permissions

This plugin ships no scripts, hooks, or local binaries. Its only component besides the skill file is a remote MCP server:

EndpointPurpose
https://postsyncer.com/mcpThe 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.

Links

License

MIT

Source: README.md at commit 1bb419f

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts