Bluesky MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLUESKY_HANDLE | Yes | Your Bluesky handle (e.g., you.bsky.social) | |
| BLUESKY_APP_PASSWORD | Yes | Your Bluesky App Password (generated from Settings → App Passwords) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_postsB | Search Bluesky for posts matching a query. |
| timelineC | Get the authenticated user's home timeline. |
| notificationsC | Get the authenticated user's notifications. |
| profileB | Get a Bluesky profile by handle or DID. |
| threadA | Get a post and its replies. |
| postA | Publish a Bluesky post. Requires confirm: true. |
| thread_postA | Publish a self-thread (each post replies to the previous). Requires confirm: true. |
| replyC | Reply to a post. Requires confirm: true. |
| likeC | Like a post. Requires confirm: true. |
| repostB | Repost a post. Requires confirm: true. |
| followB | Follow an account. Requires confirm: true. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose: follow, like, post, reply, repost, search, thread operations, profile retrieval, notifications, and timeline. No overlapping functionality.
Tools use consistent lowercase and underscores for compound names, but mix verb names (follow, like) with noun names (notifications, profile, thread, timeline). While readable, the pattern is not entirely uniform.
With 11 tools, the server covers the essential Bluesky operations (posting, reading, searching, interacting) without being bloated or too sparse. The count fits the domain well.
Core workflows like posting, replying, searching, and timeline reading are covered. Minor gaps exist: no tools for unfollowing, unliking, or deleting posts, but the surface is sufficient for most agent tasks.