Devdocs MCP

Name: Devdocs MCP
Author: madhan-g-p

by madhan-g-pversion 1.0.0i★ –iRuns on your computer

Registry nameio.github.madhan-g-p/devdocs-mcp

Install

Overview

Description from the maker (original English)

Local DevDocs MCP Server (Developer Docs with project specific context awareness)

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "devdocs": {
      "command": "npx",
      "args": [
        "-y",
        "@madhan-g-p/devdocs-mcp-server"
      ]
    }
  }
}

Run this in your terminal

claude mcp add devdocs -- npx -y @madhan-g-p/devdocs-mcp-server

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "devdocs": {
      "command": "npx",
      "args": [
        "-y",
        "@madhan-g-p/devdocs-mcp-server"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "devdocs": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@madhan-g-p/devdocs-mcp-server"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account madhan-g-p, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32531 servers in this category
Published to the registry more recently than 2% of the other 32531 servers in this category
Basic checks equal to or better than 100% of the other 32531 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Devdocs MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 10 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Reelsaw

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Reelsaw

by osbytes

Drive a self-hosted Reelsaw: turn long videos into vertical clips, edit, re-render and export them.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

DevDocs-MCP: Documentation Authority for AI Agents

Eliminate AI hallucinations with local, version-aware, and authoritative documentation.

DevDocs-MCP is a Model Context Protocol (MCP) server that provides version-pinned, deterministic documentation sourced from DevDocs.io to AI assistants (Claude, RooCode, Cline, Copilot etc.). It acts as a local Documentation Intelligence Layer, ensuring your agent always has the correct API context without network latency or training data drift.

This server follows the proposed MCP server standard defined by the MCP , which is being adopted by AI tools and agents across the ecosystem, including those from providers such as Anthropic, OpenAI, and Google.

⚠️ Project Status Notice ⚠️

This project is under active and heavy development. Still need to test existing features and implement more new features like optimal caching , update latest doc automatically and also on request basis , optimal querying and more... Design decisions, APIs, and structure are expected to evolve based on strong opinions, reviews, and feedback from the developer community. I warmly welcome discussions, critiques, and contributions to help shape this project in the right direction.

📑 Table of Contents

Overview
Key Capabilities
Quickstart
Installation & Setup
AI Agent Configuration
Further Reading

🎯 Overview

What This Project Is

A local MCP server written in NestJS (TypeScript).
A deterministic authority for documentation metadata and content.
A lazy-ingestion engine that caches DevDocs offline.
A project-aware context manager that pins docs to your package.json versions.

What This Project Is NOT

❌ An AI agent or code generator.
❌ A web scraper (it uses structured DevDocs datasets).
❌ A DevDocs UI replacement.
❌ A hosted SaaS (it runs 100% locally).

Why This Exists (The Problem)

Modern AI coding agents face three major hurdles:

Hallucination: Guessing API signatures or using deprecated methods.
Latency: Fetching live web docs for every query is slow.
Version Drift: Mixing up React 18 with React 19 features.

The Solution: DevDocs-MCP provides "Just-in-Time" documentation retrieved from local storage, filtered by your project's specific dependency versions.

Mental Model

DevDocs-MCP acts as a middleware between your IDE Agent and the documentation source.

graph TD

🚀 Key Capabilities

Offline-First: Documentation is cached locally; no internet is needed after ingestion.
Ranked Fuzzy Search: Instantly find relevant entries (e.g., "intersection observer").
Version Awareness: Automatically maps to specific library versions in your project.
Node-Only Architecture: Uses sql.js for zero-native dependencies (no Python/C++ build steps).
Structured Outputs: Returns clean, LLM-optimized content.

⚡ Quickstart

Clone & Install

  git clone https://github.com/madhan-g-p/DevDocs-MCP.git

cd DevDocs-MCP pnpm install

Configure Environment

  cp .env.example .env

Edit .env: Set DEVDOCS_DATA_PATH to where you want to store docs.

Build & Run

  pnpm build

pnpm start:prod

Note: Strictly use pnpm for development and contributions.

🛠️ Installation & Setup

DevDocs-MCP is optimized for zero-fuss setup with pnpm. It is a Node-only project.

Prerequisites

Node.js 18+ (tested on 18.x and 20.x).

🐳 Docker Usage

DevDocs-MCP is designed to be lightweight and persistent. Since it downloads and caches large documentation datasets, managing your data volumes correctly is essential.

Method A: Docker Compose (Dynamic & Persistent)

This is the recommended way. It supports 3 storage modes via the DEVDOCS_VOLUME_SOURCE variable in your .env file.

Configure your preferred storage in .env: `bash

Mode 1: Named volume (Default - Docker manages it)

DEVDOCS_VOLUME_SOURCE=devdocs_data

Mode 2: Host Path (Outside Docker - Local folder)

DEVDOCS_VOLUME_SOURCE=./my-docs-storage

Start the server: bash docker compose up -d

Flexibility: Every time you start the container, you can point to a new volume (to start fresh) or an existing volume (to keep your data) just by changing the DEVDOCS_VOLUME_SOURCE in your .env file. Both the mcp.db (database library) and the data/ (documentation downloads) are stored inside this volume.

Method B: Docker Run (Manual)

If you just want to run the public image directly from Docker Hub:

docker run -d -p 3000:3000 \

-v "devdocs_data:/app/data" \ --name devdocs-mcp \ madhandock1/devdocs-mcp:latest

💾 Data Strategy

The project uses a single mount point at /app/data which contains:

/app/data/mcp.db: The SQLite registry.
/app/data/docs/: The cached documentation files.

This unified structure makes it easy to backup or move your entire documentation authority by simply moving one folder or volume.

Configuration (`.env`)

Variable	Description	Default
`DEVDOCS_DATA_PATH`	Path to store downloaded documentation JSONs.	`./data`
`MCP_DB_PATH`	Path to the SQLite metadata database.	`mcp.db`
`LOG_LEVEL`	Verbosity (debug, info, warn, error).	`info`

Ingesting Documentation

Once the server is connected to your agent, use the ingest tool to download documentation for your specific stack: Agent will take care of it once the server is up and running , it is supposed to list the available to tools and take decision accordingly.

"dependencies": { "react": "18.2.0", "typescript": "5.0.0" } }

>Note: The Devdocs fetch url required to be used for ingestion is defined in `src/config/constants.ts`. This URL currently points to the correct and officially supported path. If the [devdocs](https://github.com/freecodecamp/devdocs) community changes this path in future, the configuration may need to be updated accordingly.<br/>

This approach does not involve web scraping. It follows the same supported mechanism used by DevDocs to provide documentation for offline use, similar to how users download documentation within DevDocs itself.

🤖 AI Agent Configuration

RooCode / Cline / Claude Desktop (Recommended: STDIO)

Add this to your mcp_settings.json. By setting the cwd (Current Working Directory), the server will automatically load configuration from your .env file, allowing you to use relative paths for data storage.

"mcpServers": { "devdocs": { "command": "node", "args": ["dist/main.js"], "cwd": "file://path/to/your/DevDocs-MCP" } } }

Pro Tip: Use the absolute path to the project in cwd. The server will then find your .env and use the DEVDOCS_DATA_PATH and MCP_DB_PATH you've defined there (e.g., ./data or mcp.db), making the setup portable!

Remote / Web Clients (HTTP SSE)

If you need to expose the server via a port (for production/remote setups):

Start the server with a port flag:

   node dist/main.js --port 3000

Configure your client:

SSE URL: http://your-server:3000/mcp/sse
Type: SSE (Supported by most MCP clients, atleast I guess so)

📖 Further Reading

System Architecture: Deep dive into the data flow, schema, and sql.js internals.
Contributor Guidelines: Workflow, coding standards, and PR requirements.
LICENSE: MIT License.

*Inspired from this project devdocs-local , devdocs-local-demo by @Nathaniel Whiteinge*

Devdocs MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Reelsaw

README from the maker

DevDocs-MCP: Documentation Authority for AI Agents

📑 Table of Contents

🎯 Overview

🚀 Key Capabilities

⚡ Quickstart

Edit .env: Set DEVDOCS_DATA_PATH to where you want to store docs.

🛠️ Installation & Setup

Prerequisites

🐳 Docker Usage

Method A: Docker Compose (Dynamic & Persistent)

Mode 1: Named volume (Default - Docker manages it)

Mode 2: Host Path (Outside Docker - Local folder)

DEVDOCS_VOLUME_SOURCE=./my-docs-storage

Method B: Docker Run (Manual)

💾 Data Strategy

Configuration (.env)

Ingesting Documentation

🤖 AI Agent Configuration

RooCode / Cline / Claude Desktop (Recommended: STDIO)

Remote / Web Clients (HTTP SSE)

📖 Further Reading

Configuration (`.env`)