Skip to main content
Glama
Atlas Docs MCP Server

Atlas Docs MCP Server

by CartographAI

Atlas Docs MCP Server

NPM Version

A Model Context Protocol (MCP) server that provides AI assistants with documentation for libraries and frameworks.

WARNING

Atlas Docs is currently in beta. Not everything might work perfectly, but we're actively improving the service. Your patience andfeedback are greatly appreciated!

What Does This Server Do?

LLMs are great at generating general code, but suck at correctly using less popular or newly released libraries. This isn't surprising, since the models have not been trained comprehensively on code using these libraries.

Atlas Docs MCP server:

  • Provides technical documentation for libraries and frameworks

  • Processes the official docs into a clean markdown version for LLM consumption

  • Is easy to set up with Cursor, Cline, Windsurf and any other MCP-compatible LLM clients

Claude 3.5 Sonnet on its own:

elevenlabs-without-atlas-annotated

Claude 3.5 Sonnet with Atlas Docs MCP:

elevenlabs-with-atlas-annotated

Related MCP server: Context7 MCP

📦 Installation

Atlas Docs MCP server works with any MCP client that supports the stdio protocol, including:

  • Cursor

  • Cline

  • Windsurf

  • Claude Desktop

Add the following to your MCP client configuration file:

{
  "mcpServers": {
    "atlas-docs": {
      "command": "npx",
      "args": ["-y", "@cartographai/atlas-docs-mcp"]
    }
  }
}

That's it! You may need to restart the app (for Claude Desktop) for the server to be recognised.

Tip: Prompt your model to check the docs eg. "Use the tools to check the documentation for Astro to ensure that you use the library correctly."

Installing via Smithery

Alternatively, you can install Atlas Docs MCP automatically via Smithery. Example for claude desktop:

npx -y @smithery/cli install @CartographAI/atlas-docs-mcp --client claude

Change "claude" to "cursor", "cline" or "windsurf" for the respective clients.

📒 Available Libraries

Want docs for another library not in this list? Please open an issue in this repo, we'll try to process and add it!

🔨 Available Tools

  1. list_docs: List all available documentation sets

  2. get_docs_index: Retrieves a condensed, LLM-friendly index of a documentation set

  3. get_docs_full: Retrieves a complete documentation set in a single consolidated file

  4. search_docs: Search a documentation set by keywords

  5. get_docs_page: Retrieves a specific page of a documentation set

💭 How It Works

Atlas Docs processes tech libraries' documentation sites into clean, markdown versions. This MCP server provides the docs as MCP tools, calling Atlas Docs APIs for the data.

Running the backend locally

Please visit CartographAI/atlas and follow the instructions in the README. Update ATLAS_API_URL with the url of your deployment.

Support & Feedback

Please open an issue in this repo to request docs for a library, or to report a bug.

If you have any questions, feedback, or just want to say hi, we'd love to hear from you. You can find us on Cartograph's Discord comunity for real-time support, or email us at contact@cartograph.app

Available Tools

5 tools
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.

Inputs: docName (required).

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.

Inputs: docName (required).

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.

Inputs: docName (required), pagePath (required).

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.

Inputs: no named parameters.

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.

Inputs: query (required), docName (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers