# pendpost [Health: Active]

**Category:** 🌐 Social Media  
**Repository:** https://github.com/pendpost/pendpost  
**GitHub Stars:** 14  
**npm Downloads (last month):** 1438  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/pendpost

## Description
Local-first social MCP: an agent drafts and schedules posts; you approve before anything publishes.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "pendpost": {
    "command": "npx",
    "args": ["-y","pendpost"]
  }
}
```

## Documentation

## 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`).

_Full upstream README: https://allmcps.com/mcp/pendpost/readme_