Skip to main content
Glama

MCP Docs Server

A simple way to make your documentation files available to AI assistants like Claude.

What Does This Do?

Think of this as a library catalog for your documentation. You have a bunch of markdown files (.md files) with documentation, guides, or notes. This server:

  1. Finds all your markdown files automatically

  2. Makes them available to AI tools through something called MCP (Model Context Protocol)

  3. Lets AI assistants search through and read your documentation

It's like giving Claude or other AI tools a filing cabinet of your documentation that they can open and read whenever they need information.

Related MCP server: docubridge

How It Works (Simple Explanation)

  1. You put documentation files in folders - Just save your .md files in organized folders

  2. The server finds them automatically - No need to manually register each file

  3. AI can read them - AI assistants can now access and search your documentation

Real Example

Let's say you have documentation for "Service 1" with these files:

  • user-functions.md - How user features work

  • call-functions.md - How calling features work

  • calendar-functions.md - How calendar features work

You would organize them like this:

docs/
└── service-1/
    ├── user-functions.md
    ├── call-functions.md
    └── calendar-functions.md

That's it! The server will automatically find these files and make them available as:

  • docs://service-1/user-functions

  • docs://service-1/call-functions

  • docs://service-1/calendar-functions

Quick Start (Step by Step)

Step 1: Install Python Requirements

You need Python 3.10 or newer and uv (a Python package manager) installed.

Install uv if you don't have it:

curl -LsSf https://astral.sh/uv/install.sh | sh

Then install the required package:

uv pip install mcp

Step 2: Add Your Documentation Files

Put your markdown files in the docs/ folder. Organize them in subfolders by topic or service:

docs/
├── service-1/
│   ├── user-functions.md
│   ├── call-functions.md
│   └── calendar-functions.md
├── service-2/
│   └── api-guide.md
└── getting-started/
    └── introduction.md

The subfolder name (like service-1) becomes the category.

Step 3: Connect to Claude Code

The easiest way is to use the Claude Code CLI. From this project folder, run:

claude mcp add --transport stdio docs -- uv run python /full/path/to/mcp-example/src/mcp_docs_server.py

Replace /full/path/to/mcp-example with your actual project path.

Verify it's connected:

claude mcp list

You should see: docs: ... - ✓ Connected

That's it! Claude Code can now access your documentation.

Adding New Documentation

To add new documentation at any time:

  1. Create a new .md file in the appropriate folder under docs/

  2. That's it! The server finds new files automatically

For example, to add documentation for a new service:

docs/
└── service-3/          # Create new folder
    └── setup.md        # Add your documentation file

No need to restart the server or change any code.

Using with Claude Code

If you're using Claude Code (the CLI tool), follow Step 3 above. The server is already configured and running!

You can now ask Claude Code questions like:

  • "List all available docs resources"

  • "Read the service-1/user-functions documentation"

  • "Search the docs for authentication"

Claude Code will automatically access your documentation files.

Managing the Server

Check if the server is connected:

claude mcp list

Remove the server:

claude mcp remove docs

Re-add the server if needed:

claude mcp add --transport stdio docs -- uv run python /full/path/to/mcp-example/src/mcp_docs_server.py

Connecting to Claude Desktop

To make your documentation available in Claude Desktop:

  1. Find your Claude Desktop config file:

    • Mac: ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows: %APPDATA%/Claude/claude_desktop_config.json

  2. Open the file and add this (replace /path/to/mcp-example with your actual folder path):

{
  "mcpServers": {
    "docs": {
      "command": "python",
      "args": ["/path/to/mcp-example/src/mcp_docs_server.py"]
    }
  }
}

Learn More

Available Tools

1 tool
search_docsC

Search through all documentation files for a given query

NameRequiredDescriptionDefault
queryYesThe search query to find in documentation
categoryNoOptional category to filter search results

Tool Schema Changelog

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

  1. 1 tool updatev0.1.0
    • First observedsearch_docs

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'search_docs' has a clear and distinct purpose that cannot be confused with any other tool in the set.

Naming Consistency5/5

The single tool follows a consistent verb_noun pattern with 'search_docs'. Since there is only one tool, the naming is inherently consistent with no deviations or mixed conventions to evaluate.

Tool Count2/5

A single tool is too few for a server named 'MCP Docs Server', which suggests a documentation-focused domain. This minimal set lacks basic operations like retrieving, creating, updating, or deleting documents, making it feel thin and incomplete for the apparent scope.

Completeness2/5

The tool set is severely incomplete for a documentation server. While 'search_docs' provides a useful function, there are obvious gaps such as no CRUD operations (e.g., get_doc, create_doc, update_doc, delete_doc) or other lifecycle management tools, which will likely cause agent failures in handling documentation tasks.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues

Related MCP Connectors

Related MCP Servers

  • A
    license
    B
    quality
    B
    maintenance
    Enables AI agents to discover, read, search, and install Markdown-based knowledge (rules, skills, workflows) from a local directory via MCP tools.
    14
    1,505 npm
    1
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    MCP server that exposes one or more documentation folders (Markdown, MDX, TXT) to AI agents, enabling listing, reading, and searching of documentation files.
    -