Bluesky MCP Server

What is Bluesky MCP Server?

A Model Context Protocol server that connects to Bluesky and provides tools to interact with the ATProtocol. It enables LLM-based applications to bring Bluesky context directly into their context window, for example turning Claude Desktop into a natural language Bluesky client.

How to use Bluesky MCP Server?

Clone the repository, install dependencies with pnpm install, and build with pnpm run build. Configure your MCP client (e.g., Claude Desktop) by adding a server entry to claude_desktop_config.json with the commands and environment variables BLUESKY_IDENTIFIER, BLUESKY_APP_PASSWORD, and BLUESKY_SERVICE_URL. You must create an app password in your Bluesky account settings.

Key features of Bluesky MCP Server

• Interact with Bluesky features via natural language
• Fetch and analyze feeds, followers, and profiles
• Search for feeds, posts, and people
• Create, like, and retrieve posts
• Follow users programmatically
• Access trending topics on Bluesky

Use cases of Bluesky MCP Server

• Use an LLM to compose and publish posts to Bluesky
• Analyze follower lists or user profiles through natural language queries
• Search for posts about a topic and summarize recent discussion
• Retrieve and review your home timeline or specific feed posts
• Build a custom assistant that interacts with Bluesky on your behalf

FAQ from Bluesky MCP Server

What tools does Bluesky MCP Server provide?

It provides 15 tools including get‑timeline‑posts, get‑feed‑posts, get‑user‑posts, search‑posts, search‑people, search‑feeds, create‑post, like‑post, follow‑user, get‑trends, and others.

How do I authenticate with Bluesky?

You must create an app password in Bluesky Settings > App Passwords and set it along with your handle and the service URL as environment variables.

Where does my session data live?

The server stores session information in memory only and does not share it with the MCP client. The client only has access to the tools, not to your authentication or app password.

What are the runtime requirements?

Node.js is required. The project uses pnpm for dependency management and is built with a standard Node build process. No additional runtime beyond the MCP client is needed.

How can I test the tools without an LLM?

You can use the MCP Inspector by running npx @modelcontextprotocol/inspector node build/src/index.js and configuring the environment variables in the inspector’s panel.