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.
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.
- Markdown documentation for a named package, served from your local install
- `npm`, `gomodules` and `pypi` as registries via the `registry` argument
- Python `help` root docs mounted by default, since many PyPi packages ship no markdown
- `docsSubDir` to point at a specific documentation folder instead of the package root
- `mcpPrimitive` to expose the docs as tools or as resources, for clients that support only one
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.
One command — npx -y markdown-sidecar-mcp