Log inSubmit server
Pendpost logo

Pendpost

Local-first MCP social planner for drafting, approving, scheduling, and publishing content across multiple platforms.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Pendpost

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "pendpost": {
      "command": "npx",
      "args": [
        "-y",
        "pendpost"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y pendpost

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 9d ago.

Overview

The pendpost MCP server lets AI agents draft, lint, schedule, and queue social posts while keeping a human approval gate before publishing. It runs locally, exposes native stdio MCP and streamable HTTP at /mcp, and shares its contract with a web dashboard. Use it when agents should manage campaigns without being allowed to publish unapproved content. Native scheduling is used where platforms support it; other lanes require pendpost to remain running.

Use cases

  • Draft multi-platform campaign posts for human review
  • Schedule approved content across connected social accounts
  • Run brand-lint and media validation before publishing
  • Inspect account health, activity, assets, and publishing status

Key features

  • Human approval gate for every post
  • Native MCP stdio and streamable HTTP transports
  • Multi-platform social and blog publishing
  • Brand-lint and media validation
  • Scheduling with platform-specific behavior
  • Safety controls for Meta blocks and lane pauses

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 47d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · pendpost (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars14Stargazers on the source repository.
npm downloads1.4kPackage downloads in the last 30 days.
Last commit10d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Pendpost works

What pendpost MCP server does

The pendpost MCP server provides a local-first workflow for planning social media and long-form content. An agent can create posts, organize campaigns, inspect accounts and assets, validate media, apply brand-lint rules, schedule work, and prepare items for publication. A human remains responsible for the final publishing decision.

Supported publishing targets include Instagram, Facebook, LinkedIn, YouTube, X, Telegram, Discord, Mastodon, Nostr, WordPress, and Ghost. Reddit, Pinterest, TikTok, and Google Business Profile are identified as beta platforms in the project documentation.

Every post has an approval state. New posts created through plan_create_post begin as drafts, and only the approval or rejection tools can change that state. Unapproved posts cannot publish. The default workflow therefore keeps the agent on the drafting and scheduling side of the process while a person handles approval.

How it works

The pendpost MCP server can be launched over native stdio, allowing an MCP client to start it with npx -y pendpost --stdio. It also supports streamable HTTP at /mcp when the local web server is already running. The dashboard and MCP interface use the same underlying capabilities, with parity checks intended to keep both interfaces aligned.

Publishing behavior depends on the platform. Facebook scheduled posts and YouTube publishAt use native scheduling, so those posts can run while the local process is offline. Instagram, LinkedIn, and X do not provide native scheduling in this setup, so pendpost must be running when those posts are due.

Safety controls include editable brand-lint rules, a Meta action-block circuit breaker, cadence limiting, and a lane pause switch. A Meta error 368 stops the Meta lane and does not automatically resume it. Health checks avoid Graph traffic while that breaker is active.

Setup and configuration

The quickest local start is npx pendpost, followed by opening http://127.0.0.1:8090. Git and Docker launch methods are also documented. The first run includes an example campaign in data/plans, allowing the planning and approval flow to be inspected before accounts are connected.

For MCP clients, configure the stdio command with npx, the -y flag, the package name, and --stdio. Claude Desktop can use the release .mcpb bundle, which starts the server and opens the approval dashboard. HTTP clients can connect to http://127.0.0.1:8090/mcp after the server is running.

Platform credentials are configured through the dashboard Setup page or a local .env file. The repository documents interactive setup commands for Meta, LinkedIn, YouTube, and X, plus credential-based setup for other lanes. An unconnected lane waits for its platform connection rather than pretending that publishing succeeded.

Tools and capabilities

The pendpost MCP server groups its tools into several areas:

  • Inspect plans, accounts, assets, activity, configuration, clients, media, platform readiness, health, previews, brand-lint results, and digests.
  • Create, update, delete, and activate campaigns and posts.
  • Approve or reject posts before publication.
  • Set schedules, publish due items, reschedule, unschedule, mark posts as posted, and verify publication.
  • Upload, rename, delete, set covers for, and clear covers from assets.
  • Fetch insights, refresh tokens, record blocks, recheck health, and control the Meta lane.
  • Manage client configuration and active clients.

Read-only tools cannot publish, while write operations remain subject to the approval rules.

Limitations and notes

The server is local-first and does not remove the need to create developer applications or complete OAuth flows for connected platforms. An agent can assist with setup prompts, but authentication and consent still occur at the relevant login gates.

Auto-approve exists as an owner-only, revocable option, while the normal behavior is human approval. PENDPOST_MODE=mock is intended for tests and demonstrations and routes lanes through a credential-free mock driver; it is not the normal production publishing mode.

The project requires Node.js 20 or newer and is released under the MIT license. Dashboard, digest, and notification language can be set to English or Swiss German (de-CH).

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Pendpost

pendpost is an MCP server that connects AI agents to a local social media planner and publishing workflow. Its main tools create, inspect, lint, schedule, approve, reject, and publish posts across supported platforms. A human approval gate blocks unapproved content, while the dashboard and MCP interface use the same capabilities.

Install it by running `npx pendpost`, or configure an MCP client to launch `npx -y pendpost --stdio`. You can also clone the repository and run `npm start`, or use Docker Compose. The local dashboard opens at `http://127.0.0.1:8090`.

Yes, pendpost works with Claude Desktop through the `.mcpb` bundle attached to GitHub releases or through a standard stdio MCP configuration. The bundle starts `npx -y pendpost --stdio` and opens the approval dashboard in the same process.

Pendpost prevents publication by creating new posts as drafts and requiring `approve_post` before they can go live. `reject_post` handles rejected items, and the system fails closed when no approval exists. Auto-approve is available only to the owner and can be revoked.

The server supports Instagram, Facebook, LinkedIn, YouTube, X, Telegram, Discord, Mastodon, Nostr, WordPress, and Ghost, with Reddit, Pinterest, TikTok, and Google Business Profile listed as beta platforms. Platform credentials must be connected before publishing.

Related MCP servers

All in Social Media All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPendpost AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/pendpost?style=directory)](https://allmcps.com/mcp/pendpost)
HTML Embed
<a href="https://allmcps.com/mcp/pendpost"><img src="https://allmcps.com/api/badge/pendpost?style=directory" alt="Pendpost on AllMCPs" /></a>