ATProto MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_profileA | Get detailed profile information for a Bluesky actor (handle or DID). |
| resolve_handleA | Resolve a Bluesky handle to its persistent Decentralized Identifier (DID). |
| search_postsB | Search for public posts on Bluesky using keywords or phrases. |
| get_author_feedB | Retrieve the post feed for a specific author. |
| get_post_threadA | Get a specific post and its surrounding conversation thread. |
| get_suggestionsB | Get suggested actors to follow. |
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 6 tools
Each tool targets a distinct aspect of the AT Protocol: feed, thread, profile, suggestions, handle resolution, and search. No overlap in functionality.
All tool names follow a consistent verb_noun pattern with underscores, using verbs like get, resolve, and search paired with specific nouns.
With 6 tools, the server is appropriately scoped for its purpose, covering key read operations without being excessive or insufficient.
The tools cover common read and query operations for Bluesky, but lack write capabilities (e.g., posting, following), which may be intentional but leaves a minor gap.