Serve llms-txt documentation over MCP (MCP Python SDK v2 / 2026-07-28 spec)
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"llmstxt-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# llmstxt-mcp — MCP LLMS-TXT Documentation Server *Installed from PyPI as **`llmstxt-mcp-server`**; the CLI command is `mcpdoc`.* > **A maintained fork of [langchain-ai/mcpdoc](https://github.com/langchain-ai/mcpdoc), ported to MCP Python SDK v2.** > > Upstream `mcpdoc` targets SDK v1 and declares an unbounded `mcp[cli]>=1.4.1`. Now > that MCP Python SDK **v2.0.0** (the 2026-07-28 spec release) is on PyPI, a fresh > `uvx --from mcpdoc mcpdoc ...` resolves `mcp` 2.x and fails immediately — SDK v2 > removed `mcp.server.fastmcp` and renamed `FastMCP` to `MCPServer`. > > This fork ports the server to `MCPServer`, pins `mcp>=2.0.0,<3`, and adds the > `streamable-http` transport. Original work © LangChain, Inc., MIT licensed; this > fork keeps the same license. See [Differences from upstream](#differences-from-upstream). > > The PyPI distribution is `llmstxt-mcp-server` (PyPI rejects `llmstxt-mcp` as too > similar to the unrelated `llms-txt-mcp` project). The import package and CLI > command remain `mcpdoc`. > > **Still on SDK v1?** Keep using upstream `mcpdoc` and pin `mcp<2` yourself. ## Overview [llms.txt](https://llmstxt.org/) is a website index for LLMs, providing background information, guidance, and links to detailed markdown files. IDEs like Cursor and Windsurf or apps like Claude Code/Desktop can use `llms.txt` to retrieve context for tasks. However, these apps use different built-in tools to read and process files like `llms.txt`. The retrieval process can be opaque, and there is not always a way to audit the tool calls or the context returned. [MCP](https://github.com/modelcontextprotocol) offers a way for developers to have *full control* over tools used by these applications. Here, we create [an open source MCP server](https://github.com/modelcontextprotocol) to provide MCP host applications (e.g., Cursor, Windsurf, Claude Code/Desktop) with (1) a user-defined list of `llms.txt` files and (2) a simple `fetch_docs` tool read URLs within any of the provi…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.