Skip to main content
Glama
README.md
# devdocs-mcp
KnowledgeBase MCP server for Developer Documentation

## Installation

### Quick Start with uvx (Recommended)

Run directly from GitHub with ML dependencies (required for semantic search):

```bash
uvx --from "devdocs-mcp[ml] @ git+https://github.com/HellButcher/devdocs-mcp.git" devdocs-mcp
```

### MCP Server Configuration

Add to your MCP client configuration (e.g., Claude Desktop, Cline):

```json
{
  "mcpServers": {
    "devdocs": {
      "command": "uvx",
      "args": [
        "--from",
        "devdocs-mcp[ml] @ git+https://github.com/HellButcher/devdocs-mcp.git",
        "devdocs-mcp"
      ]
    }
  }
}
```

### Development Setup

Clone and install with ML dependencies:

```bash
git clone https://github.com/HellButcher/devdocs-mcp.git
cd devdocs-mcp
uv sync --extra ml
uv run devdocs-mcp
```

### Install with locked dependency versions

`uvx`/`uv tool install` resolve dependencies fresh and don't use the repo's `uv.lock`. If you want the exact, tested dependency versions instead, clone the repo and use the provided install script, which exports `uv.lock` and installs the tool constrained to it:

```bash
git clone https://github.com/HellButcher/devdocs-mcp.git
cd devdocs-mcp
./install.sh            # with ML dependencies (semantic search)
./install.sh --no-ml    # without ML dependencies

# then just call devdocs-mcp to run it
devdocs-mcp
```

## Features

- Access to 819+ documentation sources from devdocs.io
- Semantic search with vector embeddings (requires ML dependencies)
- Custom local documentation sources
- Efficient caching and incremental updates
- 10 MCP tools for documentation queries

## Configuration

Configuration is stored at XDG paths:
- Config: `~/.config/devdocs-mcp/config.json`
- Cache: `~/.cache/devdocs-mcp/` (docs + embeddings)

Environment variables:
- `DEVD_EMBEDDING_MODEL` - Override the default embedding model

TDQS

A4.1/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a distinct operation: listing, metadata, semantic search, content retrieval, download, index rebuild, removal, and adding local/web sources. There is no ambiguity or overlap between any two tools.

Naming Consistency4/5

Most tools follow a verb_noun pattern (list_docs, search_docs, get_document, download_doc, remove_doc, rebuild_index), but 'doc_info' (noun_noun) and the add_local_source/add_web_source pair (verb_adj_noun) deviate slightly. Overall, the naming is still predictable and readable.

Tool Count5/5

Nine tools is well-scoped for a documentation management server. Each tool earns its place, covering source management, search, retrieval, and maintenance without redundancy.

Completeness5/5

The tool set covers the full lifecycle: adding local/web sources, downloading docs, listing/inspecting, searching, retrieving content, removing, and rebuilding the index. There are no obvious gaps or dead ends.

Maintenance

ActivitySlowing
ResponsivenessNo issues