bluesky-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLUESKY_INSTANCE | Yes | The Bluesky instance URL (e.g., https://bsky.social) | |
| BLUESKY_ACCESS_TOKEN | Yes | Bluesky access token for authentication |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bluesky_social_toolC | Portmanteau: post/timeline/outbox_* — fleet drafts use outbox_enqueue → approve → publish. Return Format
Examples
|
| bluesky_helpC | Help for bluesky-mcp. |
| bluesky_shutdownA | Signal graceful shutdown (process exit left to host). |
| show_outbox_cardB | Rich Prefab card summarizing pending outbox drafts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| bluesky_outbox_prompt | How to queue and publish fleet promotion drafts safely. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| outbox_summary_resource | Live outbox summary (pending/total) as a resource. |
| bluesky-outbox/SKILL.md | Bluesky Outbox Skill |
| bluesky-outbox/_manifest | File listing for bluesky-outbox |
| Prefab Renderer (show_outbox_card) |
TDQS
Scored across 4 tools
bluesky_help and bluesky_shutdown are clearly distinct, but show_outbox_card overlaps with the outbox operations in bluesky_social_tool. The portmanteau nature of bluesky_social_tool also makes it a catch-all, increasing selection difficulty.
Naming is inconsistent: bluesky_help and bluesky_shutdown share a prefix, but show_outbox_card uses a verb_noun pattern without the prefix, and bluesky_social_tool is a descriptive noun. No uniform verb or prefix convention is applied.
4 tools is within the typical 3-15 range, though the portmanteau tool feels overloaded by encapsulating many operations. Still, the count is reasonable for the server's apparent scope.
The tool set covers help, shutdown, outbox management (enqueue/approve/publish/list), and social interactions (post/timeline/notifications). Minor gaps like explicit post deletion or profile updates may exist, but the core workflow appears covered.