ATproto Docs 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_documentationA | Search the documentation for the given query. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a clear, distinct purpose focused on searching documentation.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'search_documentation' follows a clear verb_noun pattern.
A single tool is too few for a server named 'ATproto Docs MCP Server', which suggests a documentation-focused domain. This minimal set lacks essential operations like browsing, retrieving specific sections, or navigating documentation structure.
The tool surface is severely incomplete for a documentation server. It only provides search functionality, missing basic operations such as listing documentation topics, getting detailed content, or accessing related resources, which are critical for comprehensive documentation interaction.