
Wraps the AT Protocol API to pull data from Bluesky directly into Claude. You get seven tools: look up profiles by handle, fetch user timelines and followers, pull posts from algorithmic feeds like "discover" or "what's hot", retrieve full conversation threads, and resolve handles to DIDs. No posting or write operations, just read access to public Bluesky data. Part of the Pipeworx gateway, which means you can either connect to this server standalone or access it through their unified endpoint alongside 670+ other data sources. Useful when you need to analyze Bluesky accounts, track conversations, or pull social context into your workflows without leaving your MCP client.
Public tool metadata for what this MCP can expose to an agent.
get-my-handle-and-didReturn the handle and did of the currently authenticated user for this blusesky session. Useful for when someone asks information about themselves using "me" or "my" on bluesky.Return the handle and did of the currently authenticated user for this blusesky session. Useful for when someone asks information about themselves using "me" or "my" on bluesky.
No parameter schema in public metadata yet.
get-timeline-postsFetch your home timeline from Bluesky, which includes posts from all of the people you follow in reverse chronological order2 paramsFetch your home timeline from Bluesky, which includes posts from all of the people you follow in reverse chronological order
countnumbertypestringposts · hourscreate-postCreate a new post on Bluesky2 paramsCreate a new post on Bluesky
replyTostringtextstringget-profileGet a user's profile from Bluesky1 paramsGet a user's profile from Bluesky
handlestringsearch-postsSearch for posts on Bluesky3 paramsSearch for posts on Bluesky
limitnumberquerystringsortstringtop · latestdefault: topget-post-threadGet a full conversation thread for a specific post, showing replies and context1 paramsGet a full conversation thread for a specific post, showing replies and context
uristringconvert-url-to-uriConvert a Bluesky web URL to an AT URI format that can be used with other tools1 paramsConvert a Bluesky web URL to an AT URI format that can be used with other tools
urlstringsearch-peopleSearch for users/actors on Bluesky2 paramsSearch for users/actors on Bluesky
limitnumberquerystringsearch-feedsSearch for custom feeds on Bluesky2 paramsSearch for custom feeds on Bluesky
limitnumberquerystringget-liked-postsGet a list of posts that the authenticated user has liked1 paramsGet a list of posts that the authenticated user has liked
limitnumberget-trendsGet current trending topics on Bluesky2 paramsGet current trending topics on Bluesky
includeSuggestedbooleanlimitnumberlike-postLike a post on Bluesky1 paramsLike a post on Bluesky
uristringfollow-userFollow a user on Bluesky1 paramsFollow a user on Bluesky
handlestringget-pinned-feedsGet the authenticated user's pinned feeds and lists.Get the authenticated user's pinned feeds and lists.
No parameter schema in public metadata yet.
get-feed-postsFetch posts from a specified feed3 paramsFetch posts from a specified feed
countnumberfeedstringtypestringposts · hoursget-list-postsFetch posts from users in a specified list3 paramsFetch posts from users in a specified list
countnumberliststringtypestringposts · hoursget-user-postsFetch posts from a specific user3 paramsFetch posts from a specific user
countnumbertypestringposts · hoursuserstringget-followsGet a list of users that a person follows2 paramsGet a list of users that a person follows
limitnumberuserstringget-followersGet a list of users that follow a person2 paramsGet a list of users that follow a person
limitnumberuserstringget-post-likesGet information about users who have liked a specific post2 paramsGet information about users who have liked a specific post
limitnumberuristringlist-resourcesList all available MCP resources with their descriptionsList all available MCP resources with their descriptions
No parameter schema in public metadata yet.
Bluesky MCP — wraps the AT Protocol API
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_profile | Look up a Bluesky user's profile by handle (e.g., "alice.bsky.social"). Returns display name, bio, follower/following counts, avatar, and verification status. |
get_posts | Fetch recent posts from a Bluesky user's timeline. Returns post text, timestamps, likes, reposts, reply counts, and threaded replies. |
search_posts | Search Bluesky posts by keyword or phrase. Returns matching posts with author handles, timestamps, engagement metrics, and content.Requires bsky_handle and bsky_app_password in the gateway URL query params. |
get_feed | Get posts from a Bluesky feed (e.g., "discover", "what's-hot"). Returns recent posts with authors, timestamps, and engagement counts. |
get_followers | Get a user's followers on Bluesky by handle. Returns follower profiles including handles, display names, bios, and follower counts. |
get_follows | Get accounts a Bluesky user follows by handle. Returns followed profiles with handles, display names, bios, and descriptions. |
get_thread | Fetch a post thread by URI. Returns the parent post and all replies in conversation order with timestamps, authors, and engagement data. |
resolve_handle | Convert a Bluesky handle to its DID (decentralized identifier). Returns the DID for programmatic account lookups. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"bluesky": {
"url": "https://gateway.pipeworx.io/bluesky/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/bluesky/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Bluesky data" })
The gateway picks the right tool and fills the arguments automatically.
MIT