atproto

This MCP server acts as a bridge between large language model (LLM) clients and the AT Protocol ecosystem, enabling access to Bluesky and other AT Protocol-based networks through a Model Context Protocol (MCP) interface. It can operate in unauthenticated mode for public data and in authenticated mode for write operations, feeds, and private data. The server exposes a suite of MCP tools (the project notes 57 tools) that let an LLM client perform actions such as searching posts, viewing profiles, following or liking content, and more, all via the MCP protocol. Clients connect using MCP protocol (JSON-RPC 2.0) and the MCP server translates those calls into AT Protocol API requests, returning structured results to the LLM or downstream client. Features include real-time WebSocket streams for live data, rate-limiting handling, and a modular architecture for extending tools and resources. Tools like search_posts, get_user_profile, start_oauth_flow, handle_oauth_callback, refresh_oauth_tokens, and revoke_oauth_tokens are available in unauthenticated mode, while authentication is required for write operations and private data access. New in the release you’ll see batch operations, analytics, content discovery, and conversation context tracking to improve LLM awareness across interactions.

To use it, you run the MCP server (via npx in this setup) and configure your LLM client to point to the atproto MCP server. The LLM client will then issue MCP calls such as get_user_profile, search_posts, or create a like, which the MCP server will translate into AT Protocol API requests and return to the client. In unauthenticated mode, you can start immediately to access public data; for writing or accessing private data, enable and manage authentication (OAuth) flows as described in the documentation.

Prerequisites:

• Node.js 20.x or later
• npm (or pnpm) available on PATH
• Access to the AT Protocol MCP package and dependencies

Option A: Install globally (recommended for quick start)

1. Install the MCP server globally via npm:

npm install -g atproto-mcp

2. Run the server using npx (works with the Quick Start example):

npx atproto-mcp

Option B: Run directly with npx without prior global install

1. Launch the MCP server directly via npx:

npx atproto-mcp

Option C: Use a package manager/CI workflow as part of your deployment

1. Add as a devDependency or dependency in your project and invoke via npx or a script:

npm install atproto-mcp --save-exact

Then run:

npx atproto-mcp

Notes:

• The MCP server is designed to be launched by an MCP client (e.g., an LLM integration) using the npx command demonstrated above.
• For production deployments, consider wrapping the start command in a process manager (PM2, systemd, etc.) to ensure reliability and restarts.

Tips and considerations:

• Unauthenticated mode provides read-only access to public AT Protocol data (e.g., public profiles and posts). Authentication is required for write operations, private data, and certain features introduced in newer API changes (e.g., 2025 changes to search_posts requiring authentication).
• To enable authenticated features, configure OAuth flows in your environment and use the provided OAuth-related MCP tools (start_oauth_flow, handle_oauth_callback, refresh_oauth_tokens, revoke_oauth_tokens).
• The MCP server follows MCP SDK conventions and works with MCP clients that understand JSON-RPC 2.0 contracts. Expect tool names like get_user_profile, search_posts, get_followers, get_thread, and more.
• If you’re running in a hosted or multi-tenant environment, consider scoping permissions and ensuring rate-limits align with AT Protocol policies to avoid throttling.
• The MCP server supports real-time data via WebSocket streams; ensure your LLM client can subscribe to and filter those streams as needed.
• When upgrading, review release notes for changes to tool availability or required authentication scopes, as some features may move behind authentication or require new OAuth scopes.