Pendpost MCP Server

pendpost is a free, open-source (MIT), local-first social media planner where an AI agent drafts and schedules posts across Instagram, Facebook, LinkedIn, YouTube, X, Telegram, Discord, Mastodon, Nostr, WordPress, and Ghost behind a human. Exposed over MCP by the pendpost mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

• Humanizer brand-lint. — Captions are checked before publish against editable rules in rules.json. The humanizer layer flags English AI-writing tells. Errors block publish; warnings are advisory
• Dual interface. — A web dashboard and any MCP client drive the same contract. A parity test enforces that every capability ships on both faces
• German and Swiss localization. — Run the dashboard, digest, and notifications in English or real Swiss German (de-CH, with proper umlauts and 24-hour Swiss dates); set the language in Settings. See the localization docs

Adding it to your client

The server ships on npm as pendpost, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

• Compose — ** plan_create_post, plan_update_post, plan_delete_post, campaign_create, campaign_set_active

Configuration

You will need 8 environment variables: TELEGRAM_BOT_TOKEN, TELEGRAM_CHANNEL_ID, DISCORD_WEBHOOK_URL, MASTODON_INSTANCE_URL, MASTODON_ACCESS_TOKEN, WORDPRESS_SITE_URL, GHOST_SITE_URL, GHOST_ADMIN_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the pendpost mcp server does with a few real requests.

When to reach for it

This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Pendpost's toolset — Compose — is a fair guide to whether it matches your workflow. It is maintained by pendpost; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.