bluesky-mcp
Allows managing a Bluesky account: post, reply, like, repost, follow/unfollow, search, and read timeline/notifications.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@bluesky-mcp Post 'Hello from Bluesky MCP' to my timeline"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
bluesky-mcp
An MCP (Model Context Protocol) server for managing a Bluesky account from Claude (or any MCP-compatible client): post, reply, like, repost, follow/unfollow, search, and read your timeline/notifications. Uses the official AT Protocol API with a handle + app password — no OAuth app, no approval process required, and works even with 2FA enabled since it never touches your real account password.
The original one-off post.js CLI script is still here and still works if you just want to fire
off a single post from the terminal without going through Claude.
Setup
Clone the repo and install dependencies:
git clone https://github.com/AhmadTariq1337/bluesky-mcp.git cd bluesky-mcp npm installCopy
.env.exampleto.envand add your handle + app password (get an app password from Bluesky: Settings → Privacy and Security → App Passwords):cp .env.example .envRegister it as an MCP server in your client's config. For Claude Desktop (
claude_desktop_config.json):"bluesky": { "command": "node", "args": ["/absolute/path/to/bluesky-mcp/index.js"] }Restart Claude Desktop (fully quit from the tray, not just close the window) so it picks up the new server.
Related MCP server: bluesky-mcp
Tools exposed
Tool | Does |
| Get your home feed (scroll) |
| Get a user's posts |
| Search public posts |
| Get post details incl. the |
| Get profile info |
| List a user's followers / follows |
| Read/clear notifications |
| Look up a DID from a handle |
| Post, optionally as a reply |
| Delete your own post |
| Like / undo a like |
| Repost / undo a repost |
| Follow / unfollow (by DID) |
For the "un-" actions, pass the AT-URI of the record itself (the like/repost/follow record,
returned in viewer.like / viewer.repost / viewer.following on posts and profiles) — not the
original post or account's URI.
Standalone CLI (no Claude needed)
node post.js "Just shipped a new project, check it out!"(npm run post-cli -- "text" works the same way.) Prints a link to the live post. 300 character
limit, checked before sending.
Security
.envholds your real handle and app password, and is gitignored — never commit it.App passwords are scoped and revocable from Bluesky's settings, unlike your main account password.
License
MIT
Available Tools
18 toolsbluesky_delete_postDelete a postA
Permanently delete one of your own posts.
Inputs: uri (required).
bluesky_followFollow an accountA
Follow a user by DID. Use bluesky_resolve_handle first if you only have their handle.
Inputs: did (required).
bluesky_get_author_feedGet a user's postsB
Get the posts posted by a specific account (their profile feed).
Inputs: actor (required), limit, cursor.
bluesky_get_followersGet followersC
List the accounts that follow a given user.
Inputs: actor, limit, cursor.
bluesky_get_followingGet accounts followedB
List the accounts a given user follows.
Inputs: actor, limit, cursor.
bluesky_get_notificationsGet notificationsA
Get likes, reposts, replies, follows, and mentions for the authenticated account.
Inputs: limit, cursor.
bluesky_get_postGet a postA
Fetch one or more posts by their at:// URI, including like/repost counts and the cid needed to like/repost them.
Inputs: uris (required).
bluesky_get_profileGet a profileB
Get profile info (bio, follower counts, etc.) for an account.
Inputs: actor.
bluesky_get_timelineGet home timelineA
Get the authenticated account's chronological following feed. This is the main way to 'scroll' Bluesky.
Inputs: limit, cursor.
bluesky_likeLike a postA
Like a post. Get the uri and cid from bluesky_get_post, bluesky_get_timeline, or bluesky_search_posts.
Inputs: cid (required), uri (required).
bluesky_mark_notifications_readMark notifications as readA
Mark all current notifications as seen.
Inputs: no named parameters.
bluesky_postCreate a postA
Publish a new post (skeet), optionally as a reply to another post.
Inputs: text (required), rootCid, rootUri, replyToCid, +1 more.
bluesky_repostRepostA
Repost a post. Get the uri and cid from bluesky_get_post, bluesky_get_timeline, or bluesky_search_posts.
Inputs: cid (required), uri (required).
bluesky_resolve_handleResolve a handle to a DIDB
Look up the DID (permanent account id) for a handle. Needed for some actions like following.
Inputs: handle (required).
bluesky_search_postsSearch postsB
Full-text search across public Bluesky posts.
Inputs: query (required), limit, cursor.
bluesky_unfollowUnfollow an accountA
Undo a follow. Requires the AT-URI of the follow record itself (returned as viewer.following on a profile view).
Inputs: followUri (required).
bluesky_unlikeRemove a likeA
Undo a like. Requires the AT-URI of the like record itself (returned as viewer.like on a post view), not the post's URI.
Inputs: likeUri (required).
bluesky_unrepostRemove a repostA
Undo a repost. Requires the AT-URI of the repost record itself (returned as viewer.repost on a post view), not the original post's URI.
Inputs: repostUri (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 18 tools
Each tool targets a distinct resource and action. Timeline vs. author feed are clearly separated, and like/unlike, repost/unrepost, follow/unfollow are paired but unambiguous. No overlapping purposes.
All tools follow a consistent pattern with the 'bluesky_' prefix and verb_noun structure (get_timeline, delete_post, resolve_handle). Even standalone verbs like 'like' and 'repost' fit the style and are predictable.
18 tools is slightly above the typical 3-15 well-scoped range, but the count is justified for a complete Bluesky client covering feeds, posts, interactions, and notifications. No redundant tools.
The tool set covers core lifecycle actions: reading feeds, posting, deleting, liking, reposting, following, and notifications. Minor gaps exist like thread fetching and profile editing, but agents can work around them for most tasks.
Maintenance
Related MCP Connectors
Hosted X (Twitter) MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Publish and schedule Bluesky posts and threads from your AI assistant.
MCP server for QPost — lets AI agents publish video and image posts to YouTube, TikTok, Instagram.
Related MCP Servers
- AlicenseBqualityDmaintenanceAn MCP server that enables users to interact with the Bluesky social network through comprehensive read and write API tools, including session management and timeline navigation. It also features a Jetstream-powered local SQLite database for indexing and searching Japanese posts.362MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for Bluesky that can post on your behalf by using the AT Protocol.7MIT
- AlicenseNot gradedqualityNot gradedmaintenanceMCP server for Bluesky/AT Protocol enabling LLM clients and agents to authenticate, search, post, like, follow, and manage chat on Bluesky.MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that connects to Bluesky and provides natural language tools to interact with the ATProtocol, enabling feed fetching, post management, search, and profile analysis.32MIT