mcpdoc

mcpdoc

4.5

mcpdoc is hosted online, so all tools can be tested directly either in theTools tabor in theOnline Client.

If you are the rightful owner of mcpdoc and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcpreview.com.

MCP LLMS-TXT Documentation Server provides a structured way to manage and retrieve LLM documentation using the Model Context Protocol.

The MCP LLMS-TXT Documentation Server is an open-source solution designed to give developers full control over the tools used by applications like Cursor, Windsurf, and Claude Code/Desktop. It allows users to specify a list of `llms.txt` files and provides a `fetch_docs` tool to read URLs within these files. This setup enables users to audit tool calls and the context returned, ensuring transparency and control over the documentation retrieval process. The server supports various platforms and can be configured using YAML or JSON files, or directly through command-line arguments. It also includes security measures like domain access control to prevent unauthorized access to documentation sources.

Features

  • Full Control: Allows developers to manage tools used by applications for documentation retrieval.
  • Transparency: Users can audit tool calls and the context returned.
  • Security: Implements strict domain access controls to ensure documentation is retrieved from trusted sources.
  • Flexible Configuration: Supports YAML, JSON, and direct command-line configuration for specifying documentation sources.
  • Platform Compatibility: Works with various platforms like Cursor, Windsurf, Claude Code/Desktop, and Claude Desktop.

Tools

  • list_doc_sources: List all available documentation sources. This is the first tool you should call in the documentation workflow. It provides URLs to llms.txt files or local file paths that the user has made available. Returns: A string containing a formatted list of documentation sources with their URLs or file paths
  • fetch_docs: Fetch and parse documentation from a given URL or local file. Use this tool after list_doc_sources to: 1. First fetch the llms.txt file from a documentation source 2. Analyze the URLs listed in the llms.txt file 3. Then fetch specific documentation pages relevant to the user's question Args: url: The URL to fetch documentation from. Returns: The fetched documentation content converted to markdown, or an error message if the request fails or the URL is not from an allowed domain.