How to Schedule Social Media Posts with Claude

To schedule social media posts with Claude, add PostBoost's MCP connector (https://postboost.co/mcp) to Claude, sign in once, and ask in plain words: "Draft a LinkedIn post about our new feature and schedule it at the best time this week." Claude calls PostBoost tools to find your accounts, save a draft, check it and put it on your calendar. Nothing goes out until you say so.

This guide shows the setup for Claude.ai, Claude Desktop and Claude Code, the exact tool calls behind one request, and how to check every draft before an assistant schedules it.

What you need#

• A PostBoost account with at least one connected social account. The Free plan works: API, webhooks and MCP are on every plan.
• Claude.ai or Claude Desktop (custom connectors are available on Free, Pro, Max, Team and Enterprise; Free allows one custom connector), or Claude Code in your terminal.

You do not need an API token. The connector uses OAuth 2.1, so Claude opens the PostBoost login page and asks you to approve access.

Connect Claude to PostBoost#

Claude.ai or Claude Desktop

1. On Pro or Max, open Customize → Connectors, click + Add and choose Add custom connector.
2. Name: PostBoost. URL: https://postboost.co/mcp.
3. Keep the detected OAuth sign-in and finish setup, then click Connect and approve the connection on the PostBoost consent screen.

On Team and Enterprise plans an owner adds the connector first under Organization settings → Connectors → Add → Custom → Web; each member then connects their own PostBoost login.

Claude Code

claude mcp add --transport http --scope user postboost https://postboost.co/mcp

Run /mcp inside Claude Code and choose Authenticate next to postboost. For CI jobs that cannot open a browser, pass --header "Authorization: Bearer YOUR_API_TOKEN" with a token from Settings → Access Tokens instead. The Claude Code guide has a shared .mcp.json version that reads the token from an environment variable.

Claude acts with your PostBoost role: it sees the workspaces your login can access and can do what you can do there. Remove the connector in Claude to revoke access.

What happens when you ask Claude to schedule a post#

The connector has 46 tools: 24 read-only, 21 write and 1 destructive (delete-post, which moves a post to the trash unless you ask for a permanent delete). Here is the chain for one request:

Draft a LinkedIn post about our new OAuth connector and schedule it at the best time this week.

list-workspaces()                         → the workspace uuid
list-accounts({ workspace })              → LinkedIn Page, id 7
create-post({ workspace, account_ids: [7], content: "..." })
                                          → saved as a draft
get-best-posting-times({ workspace, account_ids: [7] })
                                          → next slot: 2026-10-14 09:00, Europe/Istanbul
schedule-post({ workspace, uuid, scheduled_at: "2026-10-14 09:00", timezone: "Europe/Istanbul" })

Two details matter here. create-post always saves a draft unless you pass a schedule, so "write me five posts" gives you five drafts to review in the PostBoost calendar. And get-best-posting-times returns the next concrete slot per account, based on when that account's audience engages most, so Claude does not have to guess a time. An account with too little posting history is left out of the next slots; for a new account, pick a time yourself.

Prompts that work well#

These are written for the connector's tools. Swap in your own accounts and topics.

• Plan a week: "List my accounts. Write one post per weekday for our LinkedIn Page about [topic]. Save them as drafts and show me the list."
• Check before scheduling: "Run validate-post on each draft and tell me about any errors before you schedule anything."
• Fill the queue: "Add the three approved drafts to the queue." (add-post-to-queue uses the next free slot of your posting schedule.)
• Sound like the brand: "Read our brand voice first, then rewrite this caption for X and Threads." (get-brand-voice returns tone, audience, words to avoid and example posts; see how to set one up.)
• Find failures: "Show posts that failed in the last 7 days and tell me why each one failed."
• Report back: "Summarise last month's analytics for the workspace and build a PDF report." (get-analytics-summary, then create-report, which returns a download link valid for 7 days.)

Check every draft before Claude schedules it#

Assistants retry and loop, so make a dry run part of every request. Through the connector, the check is a tool Claude calls; through the REST API, PostBoost also enforces the same rules on every write.

• Dry run. validate-post takes the same arguments as create-post and creates nothing. It returns content errors (for example a caption over X's 280 characters) and every guardrail that would stop the post: a duplicate, a full daily cap, an account that needs reconnecting, the X allowance. Add "run validate-post on each draft before scheduling" to your prompt.
• Duplicate guard. The rule validate-post checks: content that matches a post created for the same account in the last 24 hours. Case, spacing and media order are ignored. The REST API refuses such a post.
• Daily caps per account. For example 50 scheduled posts per UTC day on X, 25 on Instagram, 20 on a LinkedIn profile and 15 on TikTok. Drafts are never capped. The REST API stops scheduling at the cap.
• Account health. get-account-health shows which accounts can publish today. Ask Claude to check it before a big batch so nothing is scheduled to an account that needs reconnecting.

The full rules and caps per network are in Agent guardrails.

When to use the advanced server instead#

PostBoost runs a second MCP server at https://postboost.co/mcp/postboost with one tool per REST API operation, including AI image generation, workspace and user administration. It takes a dashboard access token. Use it for scripts and agents that already speak the REST API; for day-to-day work in Claude, the curated connector is safer and easier. Both are described in the MCP server docs.

If something does not work#

• Claude never opens a sign-in page: check the URL is exactly https://postboost.co/mcp.
• "Workspace not found or you do not have access": ask Claude to call list-workspaces and use a uuid from that list.
• A network refuses a feature: some features wait on the network's own review (for example first comments on Facebook and Instagram). The permissions page lists what each network allows today.

Next: compare how other tools handle AI assistants on /compare, or start on the Free plan and connect Claude in two minutes.