Atlas 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
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 |
|---|---|
| list_docsA | Lists all available documentation libraries and frameworks. Use this as your first step to discover available documentation sets. Returns name, description and source url for each documentation set. Required before using other documentation tools since you need the docName. |
| search_docsA | Searches a documentation set for specific content. Use this to find pages containing particular keywords, concepts, or topics. Returns matching pages ranked by relevance with their paths and descriptions. Follow up with get_docs_page to get full content. |
| get_docs_indexA | Retrieves a condensed, LLM-friendly index of the pages in a documentation set. Use this for initial exploration to understand what's covered and identify relevant pages. Returns a markdown page with a list of available pages. Follow up with get_docs_page to get full content. |
| get_docs_pageA | Retrieves a specific documentation page's content using its relative path. Use this to get detailed information about a known topic, after identifying the relevant page through get_docs_index or search_docs. Returns the complete content of a single documentation page. |
| get_docs_fullA | Retrieves the complete documentation content in a single consolidated file. Use this when you need comprehensive knowledge or need to analyze the full documentation context. Returns a large volume of text - consider using get_docs_page or search_docs for targeted information. |
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 5 tools
Each tool has a clearly distinct purpose: listing available doc sets, searching within a set, getting an index, fetching a specific page, and retrieving full content. Even similar-sounding tools like get_docs_index and list_docs are easily differentiated by their descriptions and scope.
All tool names follow a clear verb_noun pattern using the same object prefix 'docs'. The verbs list, search, and get accurately describe the action, and the specific suffixes index, page, and full make the target resource clear.
Five tools is a well-scoped set for a documentation retrieval server. Each tool covers a necessary step in the workflow without unnecessary duplication or bloat.
The tool surface covers the complete documentation access workflow: discover doc sets, search and browse indexes, retrieve individual pages, and get the full corpus. No obvious gaps or dead ends are present.