Bluesky MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLUESKY_IDENTIFIER | Yes | Your Bluesky handle (username) | |
| BLUESKY_SERVICE_URL | Yes | Bluesky service URL (default: https://bsky.social) | https://bsky.social |
| BLUESKY_APP_PASSWORD | Yes | App password created in Bluesky settings |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-my-handle-and-didA | 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. |
| get-timeline-postsA | Fetch your home timeline from Bluesky, which includes posts from all of the people you follow in reverse chronological order |
| create-postB | Create a new post on Bluesky |
| get-profileB | Get a user's profile from Bluesky |
| search-postsB | Search for posts on Bluesky |
| get-post-threadA | Get a full conversation thread for a specific post, showing replies and context |
| convert-url-to-uriA | Convert a Bluesky web URL to an AT URI format that can be used with other tools |
| search-peopleB | Search for users/actors on Bluesky |
| search-feedsB | Search for custom feeds on Bluesky |
| get-liked-postsA | Get a list of posts that the authenticated user has liked |
| get-trendsB | Get current trending topics on Bluesky |
| like-postB | Like a post on Bluesky |
| follow-userA | Follow a user on Bluesky |
| get-pinned-feedsB | Get the authenticated user's pinned feeds and lists. |
| get-feed-postsB | Fetch posts from a specified feed |
| get-list-postsA | Fetch posts from users in a specified list |
| get-user-postsB | Fetch posts from a specific user |
| get-followsB | Get a list of users that a person follows |
| get-followersB | Get a list of users that follow a person |
| get-post-likesA | Get information about users who have liked a specific post |
| repostB | Repost (retweet) a post on Bluesky |
| unfollow-userB | Unfollow a user on Bluesky |
| create-listA | Create a new list on Bluesky (curate list or moderation list) |
| get-listsA | Get all lists created by a user on Bluesky |
| add-to-listB | Add a user to a Bluesky list |
| remove-from-listB | Remove a user from a Bluesky list |
| delete-listB | Delete a list on Bluesky |
| get-notificationsA | Get your recent Bluesky notifications (likes, reposts, follows, mentions, replies) |
| get-conversationsA | List your recent DM conversations on Bluesky |
| send-dmB | Send a direct message to a user on Bluesky |
| get-dm-messagesB | Get messages from a specific DM conversation on Bluesky |
| list-resourcesA | List all available MCP resources with their descriptions |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize-timeline |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| bluesky-platform-info | |
| bluesky-post-schema |
TDQS
Scored across 32 tools
Most tools target distinct resources and actions, but a few pairs like get-post-likes vs. get-liked-posts or get-user-posts vs. get-timeline-posts could cause confusion. Descriptions largely clarify these differences, making the set mostly unambiguous.
All tool names follow a consistent hyphenated verb-noun pattern (e.g., get-profile, create-post, unfollow-user), making the set predictable and easy to navigate. No mixed conventions or vague verbs are present.
With 32 tools, the server exceeds the 25+ threshold for too many tools. While the broad scope of Bluesky interactions justifies many operations, the count feels heavy and several retrieval tools could potentially be consolidated.
Core social interactions are covered (posts, follows, likes, lists, DMs), but notable gaps exist: no post deletion, no profile editing, and no block/mute functionality. These omissions could hinder common workflows.