Markdown Sidecar MCP Server

This provides a structured way to serve and access markdown documentation from an MCP server for NPM packages, Go Modules, or PyPi packages. It

Local serverstdioPython

What is the Markdown Sidecar MCP MCP server?

This provides a structured way to serve and access markdown documentation from an MCP server for NPM packages, Go Modules, or PyPi packages. It enables informed code generation by exposing these markdown files as resources or tools. Exposed over MCP by the markdown sidecar mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Its toolset

Everything the assistant can do here goes through one of these:

  • workingDir — The working directory of your repo
  • packageName — The name of the package or module to request
  • registry — Registry the package will be found in (npm, gomodules, or pypi)
  • docsSubDir — [OPTIONAL] The specific subdirectory to look for markdown docs in. Defaults to package root
  • mcpPrimitive — [OPTIONAL] The MCP primitive to expose from the server (tool or resource). This defaults to tool, some clients do not currently support resources

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at markdown-sidecar-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the file and storage access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Markdown Sidecar MCP's toolset — workingDir, packageName, registry and 2 more — is a fair guide to whether it matches your workflow. It is maintained by lwsinclair; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Markdown Sidecar MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the markdown sidecar mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
workingDirThe working directory of your repo.
packageNameThe name of the package or module to request
registryRegistry the package will be found in (npm, gomodules, or pypi)
docsSubDir[OPTIONAL] The specific subdirectory to look for markdown docs in. Defaults to package root.
mcpPrimitive[OPTIONAL] The MCP primitive to expose from the server (tool or resource). This defaults to tool, some clients do not currently support resources.

How to install the Markdown Sidecar MCP MCP server

{
  "mcpServers": {
    "markdown-sidecar": {
      "command": "npx",
      "args": ["-y", "markdown-sidecar-mcp"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Markdown Sidecar MCP to workingDir.
  • Use Markdown Sidecar MCP to packageName.
  • Use Markdown Sidecar MCP to registry.

Frequently asked questions

It connects Markdown Sidecar MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (workingDir, packageName, registry, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Markdown Sidecar MCP directly.