Docs MCP Server
Creates a personal, always-current knowledge base for AI by indexing documentation from websites, GitHub, npm, PyPI, and local files.Read full description
araboldLABSCO SUMMARY
Docs from the version you installed, not the version on the website.
The usual failure when a model writes library code is that it is describing a different release — the current docs online, or whatever it remembers. Reading the markdown out of the installed package removes that mismatch, and confines everything to your working directory in the process. One server instance is scoped to one package, so a project with several dependencies worth documenting means several entries in the config.
What it is
A documentation server that reads from the packages already installed in your project rather than from the web. You name a package and a registry, and it exposes that package's markdown documentation as tools or resources. Because it reads what is installed in your working directory, the docs match the version you are actually building against.
What you get
- Markdown documentation for a named package, served from your local install
npm,gomodulesandpypias registries via theregistryargument- Python
helproot docs mounted by default, since many PyPi packages ship no markdown docsSubDirto point at a specific documentation folder instead of the package rootmcpPrimitiveto expose the docs as tools or as resources, for clients that support only one
Requirements
Run it with npx -y markdown-sidecar-mcp (package markdown-sidecar-mcp, version 1.0.0). Pass workingDir for the repository, packageName for the package you want and registry for where it came from. The package has to be installed locally already — this reads your environment, it does not fetch. Access stays inside the working directory you name. No account, no key, no network call.
Setup effort
One command — npx -y markdown-sidecar-mcp
USE CASES
01
Getting code that matches the library version you pinned
Serve the docs from the copy in your project instead of the latest release online.
02
Working with a Go module the model does not know well
Point it at the module cache with the gomodules registry and let it read the docs.
03
Using a Python package that ships no markdown
Fall back to the mounted help root docs for that package.
04
Narrowing to one part of a large documentation tree
Point docsSubDir at the folder that matters instead of the package root.
BEFORE YOU INSTALL
What to know first
Requires
npx on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y markdown-sidecar-mcpMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"sidecar": {
"command": "npx",
"args": [
"-y",
"--package",
"markdown-sidecar-mcp",
"--",
"mcp",
"start",
"--workingDir",
"<YOUR_REPO_WORKING_DIR>",
"--packageName",
"<YOUR_PACKAGE_NAME>",
"--registry",
"npm"
]
}
}
}
