Pendpost

pendpost

Agent-operated social media with a human approval gate.

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, and Nostr, plus long-form blogs on WordPress and Ghost, with Reddit, Pinterest, TikTok, and Google Business Profile in beta, all behind a human approval gate you control. It is MCP-native: AI agents draft, lint, schedule, and queue your posts, but nothing goes live until a human approves it. It is built for developers, agencies, and technical solopreneurs who want agents to do the work without handing them the keys, and without getting accounts flagged.

Why pendpost is different (not just a scheduler)

Most "AI social" tools are schedulers with an agent bolted on. pendpost is the opposite. It is an operations layer designed around the agent-plus-human workflow, and these are the parts a scheduler does not give you:

• Human approval gate. Every post carries an approval state (draft, approved, rejected) and is fail-closed: a post with no approval will not publish. plan_create_post always creates a draft, and only approve_post or reject_post can flip it. Nothing publishes until it's approved. By default that's you; auto-approve is owner-only and revocable.
• Anti-ban circuit breakers. A Meta error 368 (an action block) trips a breaker that halts the Meta lane and never auto-resumes, because 368 carries no machine-readable clear time. Health probes send zero Graph traffic while blocked. A cadence cap defers bursts rather than dropping them, and a lane pause kill switch is always available.
• 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.
• Honest native scheduling. Where a platform supports it (YouTube publishAt, Mastodon, WordPress, Ghost), pendpost hands the post to the platform's own scheduler, so it goes out even when your computer is off. Instagram, Facebook, LinkedIn, and X go out at their time from pendpost itself: from the optional 24/7 cloud service when you turn it on, otherwise from your computer while pendpost runs, or from an always-on host. It stays honest about which cover/thumbnail mechanics actually apply per platform.
• 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.

Quickstart

One line, no setup:

npx pendpost

then open http://127.0.0.1:8090

No account, no signup - pendpost runs locally and starts immediately. You can draft, approve, and schedule a full campaign right away; the first run ships an example "Acme Launch" campaign in data/plans, so you see real content at once. Connect a platform in Setup when you are ready to publish - until then a lane is live-but-unauthenticated, so publishing simply waits for the connection rather than faking it.

Prefer git or docker?

# git

git clone https://github.com/pendpost/pendpost pendpost cd pendpost npm start # or: node bin/pendpost.mjs (builds the dashboard on first run)

then open http://127.0.0.1:8090

# docker

docker compose up

then open http://127.0.0.1:8090

The dashboard

The planner and the approval queue are the two screens you live in: draft and schedule on the left, approve or reject on the right. Nothing on the right can approve itself.

MCP clients

The easiest path self-boots: pendpost speaks MCP over native stdio, so the client launches the server for you - nothing to start first.

Claude Desktop (one-click): install the pendpost .mcpb bundle attached to each GitHub release. It self-boots npx -y pendpost --stdio and opens the approval dashboard in the same process.

Claude Code and Cursor plugins: the Claude plugin bundle lives in packaging/claude-plugin/ and the Cursor plugin manifest in .cursor-plugin/. Both launch the same pinned npx pendpost@ --stdio server. Agents that install servers for you (for example Cline) can follow llms-install.md.

Any stdio MCP client:

{

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

Advanced / dev (HTTP transport): pendpost also serves MCP over streamable-HTTP at /mcp. This needs the server already running via npx pendpost:

claude mcp add --transport http pendpost http://127.0.0.1:8090/mcp

AI-assisted setup (Claude for Chrome)

Going live on a real platform means creating a developer app in each vendor's portal and running one OAuth ceremony. pendpost makes that agent-drivable: on each incomplete card in the dashboard's Setup page, a Copy AI prompt button copies a ready-to-paste, secret-safe prompt for Claude for Chrome that drives the portal for that one platform. You authenticate at every login/consent gate, and the credential is minted locally by the CLI - it never passes through the agent or the chat. The same setup contract is documented for any agent in AGENTS.md.

What the MCP tools do

Every capability is an MCP tool, and the dashboard mirrors it. Read-only tools can never publish; write tools create drafts and are gated by the approval rules above. Grouped by what they do:

• Read and inspect: plan_list, plan_get, account_status, assets_list, activity_log, validate_media, platform_validate, pendpost_health, publish_preview, brand_lint, generate_digest, config_get, clients_overview.
• Compose: plan_create_post, plan_update_post, plan_delete_post, restore_post, campaign_create, campaign_set_active.
• Approve (the human gate): approve_post, reject_post. Nothing publishes until it's approved; by default that's you.
• Schedule and publish: scheduler_set, publish_due_run, reschedule, unschedule, mark_posted, verify_post.
• Covers and assets: set_cover, clear_cover, asset_upload, rename_asset, delete_asset.
• Insights and safety: fetch_insights, token_refresh, pendpost_record_block, health_recheck, meta_lane_set.
• Config and clients: config_set, client_create, client_update, client_archive, client_list, client_set_active.

The authoritative count and the read/write split are derived from lib/mcp.mjs and verified by test/parity-check.mjs (see the MCP docs). Each tool also carries readOnlyHint/destructiveHint/title annotations in tools/list.

Going live

When you are ready to publish, connect each platform in Setup (or copy .env.example to .env and fill in only the platforms you use). A platform publishes once its credential is present; until then it is live-but-unauthenticated and publishing waits for the connection. (PENDPOST_MODE=mock exists only as a test/demo fixture that routes every lane through the credential-free mock driver.)

Each platform has an interactive setup ceremony that writes to .env:

# Meta (Facebook + Instagram). A System User token is preferred for automation.

node scripts/meta-social.mjs setup-system-user \ --system-user-token --page-id --app-id --app-secret

(or node scripts/meta-social.mjs setup for a long-lived Page token)

LinkedIn (after creating an OAuth app)

node scripts/linkedin-social.mjs auth

YouTube (after creating an OAuth client)

node scripts/yt-social.mjs auth

X (Twitter), OAuth 2.0 PKCE (browser). OAuth 1.0a needs no command - see below.

node scripts/x-social.mjs auth

Static-credential lanes (no browser): paste the credential into .env (or use

the dashboard Setup form), then validate with the engine's auth command.

node scripts/telegram-social.mjs auth # TELEGRAM_BOT_TOKEN + TELEGRAM_CHANNEL_ID node scripts/discord-social.mjs auth # DISCORD_WEBHOOK_URL node scripts/mastodon-social.mjs auth # MASTODON_INSTANCE_URL + MASTODON_ACCESS_TOKEN node scripts/wordpress-social.mjs auth # WORDPRESS_SITE_URL + _USERNAME + _APP_PASSWORD node scripts/ghost-social.mjs auth # GHOST_SITE_URL + GHOST_ADMIN_API_KEY node scripts/nostr-social.mjs keygen --save && node scripts/nostr-social.mjs auth # + NOSTR_RELAYS

Running more than one client? Append --client to any command above so the credential lands in that client's .env (single-client installs don't need it, and pendpost_health's connectAction already fills the flag in for you).

X (Twitter) supports two auth paths; OAuth 1.0a is recommended because it needs no browser and sidesteps the ERR_TOO_MANY_REDIRECTS that some apps hit on X's OAuth 2.0 consent screen.

• OAuth 1.0a (recommended, zero browser). In the X developer portal: (1) set the app's User authentication settings to Read and Write FIRST; (2) then under Keys and tokens, generate/regenerate both the API Key/Secret and the Access Token/Secret; (3) paste all four into .env as X_API_KEY, X_API_SECRET, X_ACCESS_TOKEN, X_ACCESS_TOKEN_SECRET. The lane goes live the moment X_ACCESS_TOKEN_SECRET is set - no auth command. Verify with node scripts/x-social.mjs probe (prints connected as @handle). Gotchas, in order:
• All four values must come from the same app and the same generation.
• Regenerating the API Key/Secret invalidates the Access Token/Secret - so always regenerate the Access Token/Secret after the API Key/Secret, never before.
• One wrong character yields 401 "Could not authenticate you" (code 32), which masquerades as an access-token problem. Copy the values from the portal; do not hand-type them.
• OAuth 2.0 PKCE (browser). Create an OAuth 2.0 confidential client with callback http://localhost:8087/callback and scopes `tweet.read tweet.write users.read media.write offline.