planpo.st exposes its whole product as MCP tools: 45 of them, covering scheduling to seven networks, media generation, approvals, analytics and revenue. Connect any agent and it can do what the dashboard does.
The difference from every other social MCP server is the last step. Posts carry tracked links, payments from Stripe, Shopify or RevenueCat match back to the post that caused them, and the agent can read the result. Your agent posts, then tells you what the post earned.
Streamable HTTP at mcp.planpo.st. Works from every client that takes a URL, including ChatGPT.
claude mcp add --transport http planpost https://mcp.planpo.st/mcp \ --header "Authorization: Bearer pk_live_xxx"
stdio over npx, Node 18+. The package is planpost-mcp on npm.
PLANPOST_API_KEY=pk_live_xxx npx -y planpost-mcp
Draft, schedule, bulk-create, preview per platform, publish now or at the best time.
create_postbulk_create_postsupdate_postlist_postspreview_postpublish_postsuggest_scheduleget_best_times
Upload media, generate images and carousels, render video from templates.
upload_medialist_mediagenerate_imagegenerate_carouselrender_carouselcreate_videoget_video_status
The part the other MCP servers do not have: attributed revenue per post.
get_revenue_overviewget_analytics
List connections, group accounts per brand or client, address a group in one call.
list_connectionsget_connection_linkcreate_account_grouplist_account_groupsadd_connections_to_group
Route drafts through human sign-off and keep the agent writing in your voice.
submit_for_approvalget_approval_statuslist_pending_approvalsget_brand_voicesget_brand_voice_prompt
Point at a blog or feed, pull content in, repurpose it into platform-shaped posts.
add_content_sourcefetch_source_contentrepurpose_contentlist_imported_content
Tool names above are the real ones; a few list and delete variants are omitted for space. Your API key's scopes decide which tools an agent actually gets.
Plan next week from content-plan.md: three posts each on LinkedIn and Threads, best times, drafts only. Then tell me what last week's posts earned.
The agent reads your plan, calls get_best_times, books six drafts with create_post, then calls get_revenue_overview and answers the second question with attributed amounts per post. You approve the drafts in the dashboard, or ask the agent to walk you through them. That is the whole loop: plan, publish, prove.
Claude Code runs your social calendar now.
Ship the feature, then let Cursor post about it.
Plan your week in a conversation with Claude.
ChatGPT can post. Ours also tells you what it earned.
Your terminal, Google's agent, your social calendar.
Codex writes the code. It can write the announcement too.
Antigravity manages agents. Give one of them your calendar.
Message your agent. It schedules the week.
Using something not listed?
The agent schedules to every channel the dashboard can, native formats included.
Revenue tools read attributed payments from the sources you connect, so the agent reports in dollars.
Post, track, attribute, learn: how the pieces fit is its own page.
What agents can do here