Not everything is a terminal job. Claude Desktop is where planning conversations happen, the kind where you think out loud about next week, and with planpo.st connected those conversations end with a scheduled calendar instead of a to-do note.
Free plan, no card: 2 accounts, 30 posts a month, your agent included. X needs a paid plan.
Connect Claude Desktop
Sign in, no key
Settings -> Connectors -> Add custom connector
Name: PlanPost
URL: https://mcp.planpo.st/mcp
Leave the authentication fields as detected, then Connect.
A browser tab opens on planpo.st: log in and allow access.macOS: ~/Library/Application Support/Claude/claude_desktop_config.json; Windows: %APPDATA%\Claude\claude_desktop_config.json
You sign in, there is no key to paste. Its posts go out at the time the agent sets, unless you turn on approval when you connect.
Setup is a custom connector in Settings: one URL and a sign-in, no code and no key. From then on "schedule it" is a thing Claude can actually do, and "did it work" is a question it can answer from your analytics and revenue.
Claude Desktop is Anthropic's desktop app for macOS and Windows. It supports MCP through custom connectors in the settings UI and through a local config file, and it is the easiest way to use planpo.st with an agent if you never touch a terminal.
Plain requests work. Each one below is something you could send today, and what happens next.
You say
Here are four ideas I noted this week. Turn them into a posting plan for Instagram, LinkedIn and Threads, spread over the week at good times.
What happens
Claude drafts each idea per network, respects each network's limits (2,200 characters on Instagram, 500 on Threads, 3,000 on LinkedIn), asks get_best_times for slots, and books the week. You get a filled calendar and a summary you can veto line by line.
You say
How did last week go? Which posts got the most engagement, and how much revenue came in?
What happens
get_analytics returns impressions, likes, comments and shares per post, and get_revenue_overview the week's revenue and how it compares with the week before. Claude puts the two side by side. Analytics and revenue are on Creator and Pro.
You say
Use the three product photos I uploaded to planpo.st and queue them as Instagram posts this week.
What happens
list_media finds the photos, create_post writes a caption for each and books three slots. With approval on, they wait for you and nothing publishes until you say yes. Delegation without surprise posts.
You say
Use my brand voice for this week's posts.
What happens
get_brand_voices lists the tone profiles you have saved and get_brand_voice_prompt returns the instructions for one. Claude applies them to every draft in the conversation from then on. Brand voices are on Pro.
You say
Nothing should go out from the 24th to the 26th. Move those posts to the 27th, same times.
What happens
list_posts finds the posts scheduled in those three days, and update_post moves each one to the 27th at the time it already had. Claude lists what moved.
You say
I want to post weekdays at 9:00 and 17:00. Set that as my schedule.
What happens
get_posting_schedule shows the current queue and set_posting_schedule replaces it with the ten slots. Changing the slots is a Pro feature.
All 7 that planpo.st publishes to. Each network has its own rules, and each pairing has its own page with the settings table, three prompts and the limits that stop a post.
Short posts, 500 characters, one image or video, clickable links.
Good for planning a week of Threads in one sitting: talk through the topics, let Claude space them out, approve the list.
Profile or company page, 3,000 characters, up to 9 images or one video.
The long conversation is the draft. Claude Desktop turns twenty minutes of thinking out loud into a LinkedIn post, and you read the final text in the tool call before it is scheduled.
Feed posts, carousels up to 10, Reels and Stories. Media on every post.
Claude Desktop cannot send a file from your disk, so Instagram posts start from photos you have already uploaded to planpo.st. Claude writes the caption and books the slot.
Posts and threads, 280 characters, images or video, no links.
No terminal involved. You talk the idea through with Claude, settle on wording under 280 characters, and it schedules the post or the thread from the same chat.
Page posts with link cards, photo sets, video and Reels.
For someone who runs a Page and never opens a terminal this is the simplest setup. Describe the post in a chat and it lands on the Page at the time you asked for.
Video uploads and Shorts with title, description, tags and visibility.
Upload the video in the dashboard, then let Claude Desktop do the part people skip: a title written like a search query, a real description, tags and a publish time.
Video posts, 2,200 character captions, a privacy level on every post.
The clips are uploaded to planpo.st first, and the conversation with Claude handles the captions, the privacy level and the schedule.
The same list on the hosted and the local server. Grouped by the job they do, with the ones Claude Desktop reaches for most:
| Job | Tools | What that covers |
|---|---|---|
| Posts and scheduling | create_post, bulk_create_posts, update_post, preview_post, get_best_times, suggest_schedule | Draft, schedule and reschedule, one post or up to 50 in a call. Each network can get its own text, media and settings, and every post can wait for your approval if you turn that on. |
| What is queued and what failed | list_posts, get_post, list_campaigns, get_delivery_report, retry_failed, list_pending_approvals | Filter the queue by status, network or campaign. Failed posts come back with the error and the fix, and a passing failure can be sent again. |
| Analytics | get_analytics | Impressions, likes, comments and shares for published posts, on Creator and Pro. |
| Revenue | get_revenue_overview | Revenue totals, conversions and the trend from Stripe, Shopify or RevenueCat, on Creator and Pro. Revenue next to each post is on Pro. |
| Accounts | list_connections, get_connection_link, list_account_groups, get_account_group | Find the accounts to post to, and hand you the link to connect a new one. |
Every tool with its description is in the MCP tool reference.
Turn on approval. By default Claude Desktop's posts go out at the time it sets. Switch on “Ask me before anything goes live” when you connect it, or any time on the Agent page, and every post it writes waits in Posts, under In review, until you approve it. With an API key, the switch is “Require approval before publishing”, in the key's row on the Agent page. Claude Desktop cannot change either setting itself.
Ask for drafts, if you want less than that. A post created without a time is a draft, and nothing leaves planpo.st until it is scheduled.
Scope the key. With an API key, permissions such as posts:read and posts:write decide what it can touch, so a key without posts:write lets Claude Desktop read the calendar and the numbers and change nothing.
It finds out when the post is created, not two weeks later when the slot arrives. Every post is checked against the rules of each network it targets: character limits, required media, the X rule against links, a TikTok privacy level, a connection that has lapsed.
A post that breaks one is saved as a draft and the tool result lists each issue with a code, the network and the fix in words. Claude Desktop reads that, corrects the post with update_post, and it goes back on the schedule. Softer problems, such as a caption link that will not be clickable on Instagram or a missing YouTube title, come back as warnings and do not block anything.
When a post reaches some of its networks and fails on one, its status is partially_published, with a result per network, so a post is never reported as published while one network refused it.
Partly, and the rest is in the app. Claude Desktop can read your revenue totals, the conversions and the trend through get_revenue_overview, on Creator and Pro. Which post each payment came from is on Pro, on the app's Revenue screen: links in your posts are tracked, and a payment from Stripe, Shopify or RevenueCat that follows a click is matched to the post that caused it.
It takes about a minute. The desktop app. Supports both a config file and custom connectors. No API key is needed: add the hosted endpoint and sign in to planpo.st when the browser opens. With a key instead, add the server, hosted or local, and the tools appear.
Config location: macOS: ~/Library/Application Support/Claude/claude_desktop_config.json; Windows: %APPDATA%\Claude\claude_desktop_config.json
Settings -> Connectors -> Add custom connector
Name: PlanPost
URL: https://mcp.planpo.st/mcp
Leave the authentication fields as detected, then Connect.
A browser tab opens on planpo.st: log in and allow access.Settings -> Connectors -> Add custom connector
Name: PlanPost
URL: https://mcp.planpo.st/mcp
Then add the header:
Authorization: Bearer pk_live_xxx{
"mcpServers": {
"planpost": {
"command": "npx",
"args": ["-y", "planpost-mcp"],
"env": { "PLANPOST_API_KEY": "pk_live_xxx" }
}
}
}For Claude Desktop the custom connector is the easy route: two fields in Settings, a sign-in, and no file to edit. Choose the local config when you want the key in a file on your own disk, and remember the app reads that file only when it starts.
| Question | Hosted HTTP | Local npm (stdio) |
|---|---|---|
| What it is | Streamable HTTP to https://mcp.planpo.st/mcp | The planpost-mcp npm package over stdio, started with npx |
| What you install | Nothing | Node 18 or newer. npx fetches the package |
| How it signs in | You sign in to planpo.st in the browser, or send an API key in a header | An API key in an environment variable on your machine |
| Tools you get | All of them; signed in, all but image generation | All of them, the same list |
| Updates | Server side, nothing to do | Tied to the package version npx has cached |
| Choose it when | You want it working in a minute | The key should stay in your own environment |
Both reach the same tools, so switching later is a config change and nothing else. The Claude Desktop setup guide has every variant.
Free plan, no card: 2 accounts, 30 posts a month, your agent included. X needs a paid plan.