LabscoMCP early access ↗
alekspetrovMCP SERVER · OFFICIAL PROJECT

MCP Documentation Service

Manage a folder of Markdown documentation from an assistant - read, write, edit, search, and check its health.

by alekspetrov ↗Team Wikis & Documentation Platforms✓ Official

LABSCO SUMMARY

Health checking is what separates this from filesystem access.

Reading and writing Markdown is something a plain filesystem server already does. Assessing missing frontmatter and broken links across the set, and generating navigation from the structure, is the part that treats the folder as documentation rather than as files - and it is the question nobody asks until the docs have already rotted.

What it is

A documentation manager over a directory of Markdown files with YAML frontmatter. It handles the file operations and the metadata, and it can assess the state of the whole set rather than one page at a time.

What you get

  • Read and write documents with their frontmatter, and make precise line-based edits
  • List and search documents by content or by metadata
  • Create folders and sections, and move, rename or delete documents
  • A health check across the documentation - missing metadata, broken links and other quality problems
  • Link and metadata validation as separate calls when you want just one of those answers
  • Navigation generated from the documentation structure, readable and reorderable
  • A consolidated single-document view of everything, produced for feeding to a language model

Requirements

Node. Run it with npx mcp-docs-service and the path to your documentation directory, which is the only argument it needs - that path is the boundary of what it can touch. Client configuration is the same shape for Cursor and Claude Desktop; both take an absolute path to the docs folder.

Setup effort

One command — npx mcp-docs-service <YOUR_PATH_TO_DOCS>

See installation options