bluesky-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLUESKY_HANDLE | Yes | Your Bluesky handle (e.g. user.bsky.social) | |
| BLUESKY_APP_PASSWORD | Yes | Your Bluesky app password |
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 |
|---|---|
| bluesky_get_timelineA | Get the authenticated account's chronological following feed. This is the main way to 'scroll' Bluesky. |
| bluesky_get_author_feedB | Get the posts posted by a specific account (their profile feed). |
| bluesky_search_postsB | Full-text search across public Bluesky posts. |
| bluesky_get_postA | Fetch one or more posts by their at:// URI, including like/repost counts and the cid needed to like/repost them. |
| bluesky_get_profileB | Get profile info (bio, follower counts, etc.) for an account. |
| bluesky_get_followersC | List the accounts that follow a given user. |
| bluesky_get_followingB | List the accounts a given user follows. |
| bluesky_get_notificationsA | Get likes, reposts, replies, follows, and mentions for the authenticated account. |
| bluesky_mark_notifications_readA | Mark all current notifications as seen. |
| bluesky_resolve_handleB | Look up the DID (permanent account id) for a handle. Needed for some actions like following. |
| bluesky_postA | Publish a new post (skeet), optionally as a reply to another post. |
| bluesky_delete_postA | Permanently delete one of your own posts. |
| bluesky_likeA | Like a post. Get the uri and cid from bluesky_get_post, bluesky_get_timeline, or bluesky_search_posts. |
| bluesky_unlikeA | Undo a like. Requires the AT-URI of the like record itself (returned as |
| bluesky_repostA | Repost a post. Get the uri and cid from bluesky_get_post, bluesky_get_timeline, or bluesky_search_posts. |
| bluesky_unrepostA | Undo a repost. Requires the AT-URI of the repost record itself (returned as |
| bluesky_followA | Follow a user by DID. Use bluesky_resolve_handle first if you only have their handle. |
| bluesky_unfollowA | Undo a follow. Requires the AT-URI of the follow record itself (returned as |
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 18 tools
Each tool targets a distinct resource and action. Timeline vs. author feed are clearly separated, and like/unlike, repost/unrepost, follow/unfollow are paired but unambiguous. No overlapping purposes.
All tools follow a consistent pattern with the 'bluesky_' prefix and verb_noun structure (get_timeline, delete_post, resolve_handle). Even standalone verbs like 'like' and 'repost' fit the style and are predictable.
18 tools is slightly above the typical 3-15 well-scoped range, but the count is justified for a complete Bluesky client covering feeds, posts, interactions, and notifications. No redundant tools.
The tool set covers core lifecycle actions: reading feeds, posting, deleting, liking, reposting, following, and notifications. Minor gaps exist like thread fetching and profile editing, but agents can work around them for most tasks.