Developer & Agents•
11 min read
•
2026-11-13 · Updated 2026-11-13

Bluesky MCP Setup: Post to AT Protocol with App Passwords and AI Agents

TL;DR — Direct Answer

A Bluesky MCP server exposes AT Protocol actions, such as creating a post or uploading a video, as tools an AI assistant can call. Fastest setup: create a Bluesky App Password, connect Bluesky in Reeling, add Reeling's MCP server to your Claude or Cursor config, then ask the agent to draft, preview and schedule the post.

By Reeling Team. Examples describe the documented implementation; no live publishing test is implied.

What is a Bluesky MCP server?

A Bluesky MCP server is a Model Context Protocol server that turns AT Protocol actions, such as reading a timeline, creating a post, uploading a video or replying in a thread, into tools that Claude, Cursor or Claude Code can call. What your agent can actually do depends on which server you install.

When we checked on November 13, 2026, the options fell into two groups. Self-hosted community servers on GitHub, such as brianellin/bsky-mcp-server and gwbischof/bluesky-social-mcp, log in with your handle and an App Password stored in the MCP client's environment and call the Bluesky API directly; most are built for reading, searching and quick posting. Scheduler-backed servers, such as Reeling's open-source adapter (github:yomariano/reeling-mcp), publish through the scheduler's existing Bluesky connection, so the App Password stays in the scheduler, posts can be queued for a later time and the same call can reach other networks.

Self-hosted GitHub Bluesky MCP serversReeling MCP (hosted or local adapter)
AuthenticationHandle plus App Password in BLUESKY_IDENTIFIER and BLUESKY_APP_PASSWORD environment variablesReeling API key (rl_...); the App Password is entered once in Reeling's Connect Channels
Where the Bluesky credential livesIn your MCP client config on every machine that runs the serverIn your Reeling project, not in the agent's config
Reading timelines, search and trendsYes, the main focus of most serversNo; Reeling reads replies through its inbox, not your feeds
Text-only and image postsYes on servers that expose send_post or send_imagesNo; Reeling publishes Bluesky video posts
Video postsSome servers (for example a send_video tool)Yes: MP4, MOV or WebM up to 50 MiB
SchedulingNo; the post goes out when the tool runsYes: scheduled_at takes an ISO 8601 time
Cross-posting in one callNo; Bluesky onlyYes: add threads, youtube, tiktok or other platform keys
Replies and metricsReply and like tools vary by serverreeling_get_inbox and reeling_reply_to_comment for Bluesky threads; likes, replies, reposts and quotes
Approval and dry runDepends on your client's tool approval promptClient approval prompt plus read-only tools to inspect channels first
CostFree; you run and update itCreator plan $19/month or Agency $39/month (Starter has no MCP access)

App Password or OAuth for Bluesky automation?

Use an App Password for a personal agent or scheduler today. It is a separate password that Bluesky generates for one app; it can post as you but cannot delete your account or create further App Passwords, and you can revoke it on its own without changing your main password. Reeling's Bluesky connection asks for your handle and an App Password, never your main password.

OAuth is the AT Protocol's primary authorization mechanism, and the specification expects most user-facing apps to use it. It is the right choice if you are building a public app that many people will log in to, because users approve your client in their own browser and you never handle a password at all. For a single creator or team wiring Claude or Cursor to their own account, an App Password per tool is simpler and easier to audit. Name each one after the tool that uses it, leave direct-message access off unless the tool really needs it, and revoke it the day you stop using that tool.

QuestionApp PasswordOAuth
Best forYour own account in a scheduler, script or MCP serverPublic apps that many Bluesky users sign in to
Setup timeAbout a minute in Bluesky settingsClient metadata, redirect handling and token refresh to build
Can it delete your account or create more App Passwords?NoOnly what the granted scopes allow
Revoke one tool without touching othersYes, delete that App PasswordYes, revoke that app's session
Supported by ReelingYes: handle plus App Password in Connect ChannelsNot used for Bluesky
Main riskAnyone holding it can post as you until it is revokedImplementation mistakes in your own client

Step 1: Create a Bluesky App Password and connect it in Reeling

In Bluesky, open Settings, then Privacy and security, then App passwords, and choose Add App Password. Name it Reeling, leave direct-message access off, and copy the generated password straight away, because Bluesky shows it only once. The direct link is bsky.app/settings/app-passwords.

In Reeling, open the project you want the agent to post from, go to Connect Channels and choose Bluesky. Enter your handle without the @ (for example yourname.bsky.social, or your custom domain) and paste the App Password. Reeling confirms the connection in the project; if it says the credentials failed, check the handle first, then generate a fresh App Password rather than retyping the old one.

Before your first video, verify your email address in Bluesky. Bluesky requires a verified email before an account can upload video, and Reeling's integration notes list the same requirement.

Bluesky App Password checklist
[ ] Bluesky > Settings > Privacy and security > App passwords > Add App Password
[ ] Name: Reeling (one App Password per tool)
[ ] Direct-message access: off
[ ] Password copied once and pasted only into Reeling Connect Channels
[ ] Handle entered without @, e.g. yourname.bsky.social
[ ] Bluesky email verified (required for video upload)
[ ] Channel appears under the right Reeling project

Step 2: Add the Reeling MCP server to Claude Desktop, Cursor or Claude Code

Create an API key in Reeling Settings (keys start with rl_), then add one server entry named reeling. Claude Desktop and Cursor can run the local adapter with npx and the key in the REELING_API_KEY environment variable. Claude Code can connect to the hosted Streamable HTTP endpoint at https://mcp.reeling.app/mcp with an X-API-Key header, or register the same local command.

Claude Desktop reads claude_desktop_config.json from ~/Library/Application Support/Claude/ on macOS or from the Claude folder inside %APPDATA% on Windows; Cursor reads .cursor/mcp.json in your project. Restart the client after saving and ask it to list its tools. Keep the key out of anything you commit; the free MCP config generator writes the same JSON with placeholder values you can fill in locally.

# Claude Desktop (claude_desktop_config.json) or Cursor (.cursor/mcp.json)
{
  "mcpServers": {
    "reeling": {
      "command": "npx",
      "args": ["-y", "github:yomariano/reeling-mcp#v1.1.0"],
      "env": {
        "REELING_API_KEY": "rl_your_api_key"
      }
    }
  }
}

# Claude Code: hosted Streamable HTTP endpoint
claude mcp add --transport http reeling https://mcp.reeling.app/mcp \
  --header "X-API-Key: rl_your_api_key"

# Claude Code: local stdio adapter instead
claude mcp add --env REELING_API_KEY=rl_your_api_key --transport stdio reeling \
  -- npx -y github:yomariano/reeling-mcp#v1.1.0

# Confirm the server is connected
claude mcp get reeling

Step 3: Find your Bluesky channel with read-only tools

Start every session with read-only calls so the agent proves it is looking at the right account before it writes anything. reeling_list_projects returns your project IDs, and reeling_list_channels with that project_id returns each connected channel with its platform, username and status. Confirm the Bluesky handle and project match what you expect.

reeling_get_platform_matrix returns Reeling's own per-network notes, including the Bluesky entry: App Password authentication, 50 MiB video and a 300-character post. Asking the agent to quote those limits back to you is a cheap way to make sure it drafts within them.

// 1. Read-only: list projects
reeling_list_projects({})

// 2. Read-only: confirm the Bluesky channel in that project
reeling_list_channels({"project_id": "YOUR_PROJECT_ID"})

// 3. Read-only: Reeling's limits per network
reeling_get_platform_matrix({})

// Prompt to give Claude or Cursor:
// "List my Reeling projects, show the Bluesky channel in the Launch project
//  with its handle and status, and tell me Reeling's Bluesky limits.
//  Do not publish anything yet."

Step 4: Draft, preview and schedule a Bluesky video post

Ask the agent for a draft first, then approve the write. reeling_publish_post needs platforms set to bluesky, a public video_url, the post text in content and, to schedule rather than publish now, scheduled_at as an ISO 8601 time with Z or an offset. project_id ties the post to the project that holds your Bluesky connection.

Keep client-side approval switched on for reeling_publish_post. Claude Desktop, Cursor and Claude Code all show the tool arguments before a consequential call runs, which is your dry run: check the handle's project, the text length, the video URL and the time. The call returns a post ID; pass it to reeling_get_post_status after the scheduled time to confirm delivery.

If you need different text for Bluesky than for other networks in the same job, use the REST API. POST https://api.reeling.app/api/v1/publish accepts a bluesky object with its own text (up to 300 characters) and the time in scheduled_for, while the MCP tool sends one content string to every platform listed.

// MCP: arguments the agent should show you before the tool runs
reeling_publish_post({
  "project_id": "YOUR_PROJECT_ID",
  "platforms": ["bluesky"],
  "video_url": "https://cdn.example.com/clips/launch-demo-45s.mp4",
  "content": "We rebuilt our onboarding in a week. Here is the 45-second walkthrough of what changed and why. Feedback welcome in the replies.",
  "scheduled_at": "2026-11-17T15:00:00Z"
})

// After the slot: confirm delivery
reeling_get_post_status({"post_id": "POST_ID_FROM_THE_RESPONSE"})

# REST: same post with Bluesky-specific text
curl -X POST https://api.reeling.app/api/v1/publish \
  -H "X-API-Key: $REELING_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "project_id": "YOUR_PROJECT_ID",
    "platforms": ["bluesky"],
    "video_url": "https://cdn.example.com/clips/launch-demo-45s.mp4",
    "bluesky": {"text": "We rebuilt our onboarding in a week. 45-second walkthrough below."},
    "scheduled_for": "2026-11-17T15:00:00Z"
  }'

Bluesky post limits an AI agent must respect

Bluesky's post record allows 300 graphemes and 3,000 bytes of text, up to four images of about 2 MB each, or one video. Bluesky's app has accepted videos up to three minutes since version 1.99, and Bluesky's video launch post set a daily upload cap of 25 videos or 10 GB per account. Account-level writes are rate limited at 5,000 points an hour and 35,000 a day, with each new post costing 3 points, and logins (createSession) are limited to 30 per 5 minutes and 300 a day.

Reeling applies stricter limits of its own, and those are the ones that decide whether a scheduled job succeeds: 300 characters of text, video up to 50 MiB in MP4, MOV or WebM, and a composer check of 60 seconds per video. Reeling counts Unicode code points rather than graphemes, so a family or flag emoji counts as several characters; text that passes Reeling's count always fits Bluesky's. The login limit matters most for self-hosted servers that open a new session on every tool call.

LimitBluesky (AT Protocol)Reeling for BlueskyWhat to tell your agent
Post text300 graphemes and 3,000 bytes300 characters (code points)Keep drafts at 280 characters or fewer to leave room for edits
ImagesUp to 4 per post, about 2 MB eachNot publishedUse a self-hosted server for image posts
Video per post11One clip per post
Video lengthUp to 3 minutes in the Bluesky app60 seconds in the composerCut clips to 60 seconds or less
Video sizeUp to 50 MB per blob on Bluesky-hosted PDSes50 MiB; MP4, MOV or WebMExport at a bitrate that stays under 50 MiB
Daily video uploads25 videos or 10 GB per day (Bluesky, September 2024)Subject to Bluesky's capSpread large batches over several days
Record writes5,000 points/hour, 35,000/day; a post costs 3Subject to Bluesky's limitsSchedule; do not burst-post
Logins30 per 5 minutes, 300 per day per accountHandled by Reeling's stored connectionSelf-hosted servers should reuse sessions

Hosted or self-hosted: which Bluesky MCP server should you use?

Choose a self-hosted community server if you mainly want your agent to read and search Bluesky, post text or images, and you are comfortable keeping an App Password in a local config file. It is free, works without any scheduler, and you can read every line of code it runs.

Choose Reeling's MCP server if the job is publishing video on a schedule, especially to Bluesky and other networks at once, or if several people or machines run the agent. The Bluesky credential stays in one Reeling project instead of every laptop's config, posts can be queued, and delivery and replies come back through the same tools. Running both side by side is fine: a community server for reading and research, Reeling for scheduled video, each with its own App Password so you can revoke either one independently.

Your jobUse
Summarise my timeline or search posts about a topicSelf-hosted community server
Post a quick text or image update right nowSelf-hosted community server
Schedule a video post for next Tuesday at 15:00 UTCReeling MCP
Send one clip to Bluesky, Threads and YouTube Shorts in one callReeling MCP
Let a team share one Bluesky connection without sharing the passwordReeling MCP
Reply to comments on posts you publishedEither; Reeling covers replies on its own posts via the inbox

Cross-post Bluesky, Threads and X from one agent prompt

Add more platform keys to the same reeling_publish_post call to send one clip everywhere, for example platforms set to bluesky, threads and x. Because the MCP tool sends one content string to every platform, write to the tightest limit in the list: 300 characters for Bluesky, 280 weighted characters for X and 500 for Threads. The video must also fit the strictest rule, which is Reeling's 60 seconds and 50 MiB for Bluesky.

Each destination succeeds or fails on its own, so check every channel result with reeling_get_post_status rather than assuming one success means all three went out. Reeling's spam score covers Reddit, Quora and Medium rather than Bluesky, so if the same agent run also drafts community posts for those sites, check those drafts with the free social spam checker before you approve them.

// One clip, three networks: text written to the 280-character X limit
reeling_publish_post({
  "project_id": "YOUR_PROJECT_ID",
  "platforms": ["bluesky", "threads", "x"],
  "video_url": "https://cdn.example.com/clips/launch-demo-45s.mp4",
  "content": "45 seconds on how we rebuilt onboarding in a week. What would you change?",
  "scheduled_at": "2026-11-17T15:00:00Z"
})

Replies, inbox and metrics after you publish

Reeling reads replies to your Bluesky posts into its unified inbox. reeling_get_inbox with platform set to bluesky lists them, and reeling_reply_to_comment posts an answer into the thread; Bluesky replies need the thread's root and parent references, so pass the reply_context object exactly as reeling_get_inbox returned it for that comment. Keep approval on for replies too, since they publish immediately.

For numbers, reeling_sync_metrics refreshes Bluesky likes, replies, reposts and quotes. Reeling's platform notes are explicit that the Bluesky views figure is an interaction total, not measured impressions, so do not let an agent report it as reach.

// Read-only: Bluesky replies waiting in the inbox
reeling_get_inbox({"platform": "bluesky"})

// Write (approve first): reply inside the thread
reeling_reply_to_comment({
  "platform": "bluesky",
  "comment_id": "COMMENT_ID_FROM_INBOX",
  "reply_text": "Thanks! The new flow ships to everyone on Monday.",
  "reply_context": {"...": "copy the reply_context object from reeling_get_inbox"}
})

Troubleshooting Bluesky MCP errors

Most failures come from the connection, the video or the text length. Check them in that order before you retry, and never let an agent loop on the same failing call: repeated attempts burn Bluesky's write and login budgets.

SymptomLikely causeFix
Connect Channels says the credentials failedHandle typed with @ or without its domain, a stray space, or the main password pastedEnter yourname.bsky.social without @ and generate a fresh App Password
Posting stopped working after weeksThe App Password was revoked in Bluesky settingsCreate a new App Password and reconnect the channel
Video upload rejectedBluesky email not verified, file over 50 MiB or clip over 60 secondsVerify the email in Bluesky, re-export the file, trim the clip
Text too longOver 300 characters, often because of emoji sequences or a long URLShorten to 280 characters or fewer and preview again
HTTP 429 from a self-hosted serverToo many logins or writes in a short windowReuse sessions, slow the schedule and wait for the window to reset
Agent cannot see the reeling toolsClient not restarted, wrong config file or missing API keyRestart the client, run claude mcp get reeling, check REELING_API_KEY

Pre-flight checklist for a Bluesky agent

Run through this list before you let an agent schedule a week of Bluesky posts. It covers the credential, the client, the content and the follow-up check.

[ ] One App Password named for this tool; DM access off; main password never shared
[ ] Bluesky email verified
[ ] Bluesky channel listed by reeling_list_channels in the right project
[ ] Reeling plan with MCP access (Creator or Agency); API key stored outside git
[ ] Client approval on for reeling_publish_post and reeling_reply_to_comment
[ ] Text: 280 characters or fewer (Reeling allows 300; X allows 280 weighted)
[ ] Video: MP4, MOV or WebM, 60 seconds or less, under 50 MiB, at a public URL
[ ] scheduled_at: ISO 8601 with Z or an offset; posts spread out, not bursted
[ ] After each slot: reeling_get_post_status for every post ID and channel

Frequently Asked Questions

What is a Bluesky MCP server?

It is a Model Context Protocol server that exposes Bluesky and AT Protocol actions, such as creating posts, uploading video, reading timelines or replying in threads, as tools an AI client like Claude, Cursor or Claude Code can call. Community servers call Bluesky directly with your App Password; Reeling's server publishes and schedules through Reeling's stored Bluesky connection.

Can Claude post to Bluesky?

Yes. Connect Bluesky to Reeling with your handle and an App Password, add Reeling's MCP server to Claude Desktop or Claude Code, and Claude can schedule a Bluesky video post with reeling_publish_post. Keep tool approval on so you confirm the text, video and time before each post is queued.

Is it safe to give an AI agent a Bluesky App Password?

It is much safer than sharing your main password. An App Password cannot delete your account or create more App Passwords, and you can revoke it alone at any time. It can still post as you, so create one per tool, leave direct-message access off, and with Reeling the password stays in Reeling rather than in the agent's config.

What are Bluesky's post limits for automated posting?

Bluesky allows 300 graphemes of text, up to four images or one video per post, videos up to three minutes in its app, and 5,000 write points an hour per account, with each post costing 3. Reeling is stricter: 300 characters, video up to 50 MiB in MP4, MOV or WebM, and 60 seconds per clip.

Does Bluesky support OAuth instead of App Passwords?

Yes. OAuth is the AT Protocol's primary authorization mechanism, and the specification expects most user-facing apps to use it. App Passwords are still supported and remain the simplest way to connect your own account to a scheduler or MCP server; Reeling's Bluesky connection uses a handle plus App Password.

Sources and related documentation

Connect Bluesky and schedule your first agent post

Add your handle and an App Password in Connect Channels, plug Reeling's MCP server into Claude or Cursor, then approve your first scheduled Bluesky video.

See the Bluesky integration
Account requirements apply
Tags:#Bluesky#MCP Server#AT Protocol#Claude#Cursor