docs-to-mcp-cli

What is docs-to-mcp-cli?

A CLI tool that generates a self‑contained, runnable MCP (Model Context Protocol) server from markdown documentation files. It exposes the documentation via specific tools so AI assistants can browse, search, and retrieve full document content.

How to use docs-to-mcp-cli?

Install globally with npm install -g @tiberriver256/docs-to-mcp-cli or use directly with npx. Run docs-to-mcp-cli --docs <pattern> --packageName <n> (both required) and optionally specify --outDir and --toolName. A bundled server is created in the output directory; start it with node dist/index.js.

Key features of docs-to-mcp-cli

• Generates a self‑contained MCP server from markdown files
• Provides three tools: list_docs, get_doc, and search_docs
• Supports fuzzy matching across all documents
• Customizable output directory and tool/package name
• Run the server with a single Node.js command

Use cases of docs-to-mcp-cli

• Let an AI assistant browse and search your project’s markdown documentation
• Give LLMs context‑aware access to API docs, guides, or internal wikis
• Convert static documentation into a live tool for AI‑powered question answering

FAQ from docs-to-mcp-cli

What is the Model Context Protocol (MCP)?

MCP is an open standard that enables AI assistants to access external tools and data sources.

What tools does the generated server expose?

It creates three tools: list_docs (lists documents with previews), get_doc (retrieves full content by path), and search_docs (fuzzy search across all documents).

How do I run the generated server?

After generation, execute node dist/index.js from the output directory.

What arguments are required?

The --docs (glob pattern for markdown files) and --packageName (name of the MCP server) options are both required.

Can I change the output directory?

Yes, use the --outDir option; the default is dist.