BlogUpdated Aug 26, 2026

How to Schedule Bluesky Posts with MCP (Claude, ChatGPT, Cursor)

Schedule Bluesky posts from Claude or ChatGPT with MCP. The open AT Protocol makes the integration simple: OAuth once and queue posts from chat.

To schedule Bluesky posts with MCP, connect a remote MCP server to your AI client and link your Bluesky account. SocialRobot exposes one at https://socialrobot.io/api/mcp: after one OAuth approval, the agent can draft posts, queue them with create_post for any future time, reschedule or delete them, and pull analytics. Every post waits on your calendar for review before it publishes.

Bluesky runs on the AT Protocol, an open standard with a documented public API, and that single design decision changes what it feels like to automate on this network. There is no gatekeeping layer between your assistant and your account: the protocol defines how posting works, anyone can build against it, and integrations do not depend on one company deciding your use case deserves access. What gets built on stable open protocols also tends to keep working, because there is no private surface quietly shifting under the tooling.

SocialRobot's hosted MCP server sits on that foundation and turns it into conversation: draft in chat, schedule from chat, review before anything goes out. The full walkthrough of the SocialRobot MCP setup covers the generic connection flow for every platform.

Setup

Link your Bluesky account in SocialRobot first. Then point your MCP client at:

{
  "mcpServers": {
    "socialrobot": {
      "type": "http",
      "url": "https://socialrobot.io/api/mcp"
    }
  }
}

The first connection opens SocialRobot login plus one consent screen. Publishing and media upload are separate scopes from analytics, so read-only evaluation is always available. Works in Claude, ChatGPT, Cursor, VS Code, Windsurf, Zed, or any remote-MCP client.

The workflow: one newsletter, three posts

Bluesky rewards frequent posting more than polished posting, which makes it the natural home for repurposing. Say your newsletter goes out Tuesday mornings:

My newsletter just went out. Here is the draft. Pull the three strongest ideas from it and turn each into a standalone Bluesky post under 280 characters, written conversationally, no hashtags unless they earn their place. Schedule them for Tuesday 1pm, Wednesday 10am, and Thursday 5pm.

The agent reads the source, drafts three distinct posts instead of three paraphrases of one, and calls create_post three times with those slots. All three land in your SocialRobot calendar as scheduled. Read them together and you will often find one overlaps another; fix it there:

Merge the second and third posts into one and keep the Wednesday slot free.

reschedule_post and delete_post handle the reshuffling without you touching a composer.

Thursday, close the loop:

How did this week's Bluesky posts do compared to last week?

get_posts_with_analytics returns per-post numbers so next week's picks come from data rather than vibes.

Prompts and the tools behind them

You sayThe agent calls
"Queue this post for tomorrow at 9am"create_post
"Turn my newsletter into three posts across the week"create_post (three times)
"Move Thursday's post to Friday"reschedule_post
"Drop the post about the outage"delete_post
"What did I schedule for next week?"list_posts
"Which posts got the most engagement this month?"get_posts_with_analytics

Open protocol, fewer surprises

Because Bluesky's API is a public standard, the integration surface does not shift the way closed platforms' surfaces do. Fewer breaking changes mean your prompts keep working longer, and the server absorbs whatever does change.

Where it fits alongside other networks

Most people running Bluesky seriously are also on X or LinkedIn. The same SocialRobot connection covers both, and the same conversation can cross-post deliberately:

Draft this announcement once, then adapt it: the Bluesky version conversational, the LinkedIn version structured with a hook line.

One idea, platform-appropriate phrasing, every version queued for review. That is the actual payoff of MCP on an open network: the plumbing recedes far enough that you think about writing, not wiring.

Getting started

  1. Create a SocialRobot account (MCP included free).
  2. Connect your Bluesky account.
  3. Add https://socialrobot.io/api/mcp to Claude, ChatGPT, or Cursor.
  4. Paste your next newsletter. Ask for three posts. Approve them in the calendar.
  5. Or compare all MCP schedulers in the roundup.

Connect your accounts and let your agent publish.

SocialRobot MCP is free on every plan. Add socialrobot.io/api/mcp to Claude, ChatGPT, or Cursor and start scheduling from chat.

Read the MCP guide