Bsky MCP Server

MCP server for Bluesky. Exposed over MCP by the bsky mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

You can use this MCP server to bring context from various Bluesky / ATProtocol API endpoints directly into the context window of your LLM based application. For example, you can add this server to Claude Desktop and then use it as a natural language Bluesky client.

• Interact with common Bluesky features via natural language (e.g. "Get recent posts from David Roberts")
• Fetch and analyze feeds ("Find me a feed about Seattle and tell me what people are talking about")
• Fetch and analyze lists of followers ("What types of accounts does Mark Cuban follow? Give me a detailed report")
• Use an LLM to write a post and then post it for you 😱 ("Write a haiku about today's weather in my area and post it to bluesky")
• Search for feeds, posts, and people ("Find posts about the #teslatakedown and give me a summary of recent events")
• Analyze who follows you? ("Who follows me on Bluesky? Give me a report")

Adding it to your client

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

• get-pinned-feeds — returns the set of all "pinned" items from the authenticated user's preferences
• get-timeline-posts — returns posts from the authenticated user's home timeline
• get-feed-posts — returns posts from the specified feed
• get-list-posts — returns posts from the specified list
• get-user-posts — returns the specified user's posts
• get-profile — returns the profile details of the specified user
• get-follows — returns the set of users an account follows
• get-followers — returns the set of users who follow an account
• get-liked-posts — returns recent posts liked by the authenticated user
• get-trends — returns current trending topics on Bluesky with post counts
• get-post-thread — returns a full conversation thread for a specific post, showing all replies and context
• convert-url-to-uri — converts a Bluesky web URL to an AT URI format that can be used with other tools

Configuration

You will need 3 environment variables: BLUESKY_IDENTIFIER, BLUESKY_APP_PASSWORD, BLUESKY_SERVICE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Bsky.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the bsky mcp server does with a few real requests.

When to reach for it

This sits in the AI and media services group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Bsky's toolset — get-pinned-feeds, get-timeline-posts, get-feed-posts and 11 more — is a fair guide to whether it matches your workflow. It is maintained by brianellin; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.