Skip to content
llms.txt Generator logo

llms.txt Generator MCP server

Which servers in the official MCP registry are llms.txt Generator's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to llms.txt Generator

Whose server it is
  • Registry namede.llms-txt-generator/llms-txtverified in the MCP registry

The registry name sits under llms-txt-generator.de. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools4
  • Server calls itselfde.llms-txt-generator/llms-txt
  • Server version1.1.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 124 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: generate an llms.txt draft from a site's public pages; validate an llms.txt file against Lighthouse agentic browsing checks.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • For "generate an llms.txt draft from a site's public pages", the likely first call is generate_llms_txt.
  • For "validate an llms.txt file against Lighthouse agentic browsing checks", the likely first call is check_lighthouse_agentic_browsing.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer151 ms
  • Space in an agent's context≈ 891 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results4 of 4 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · generate an llms.txt draft from a site's public pages
  • not sure · review which pages are included before downloading
  • can do · validate an llms.txt file against Lighthouse agentic browsing checks

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-26
  • generate_llms_txt

    Use this when the user wants a new llms.txt file for a public website they name. Reads up to 15 public HTML pages of that one domain (start page, XML sitemap, internal links) and returns a ready-to-publish llms.txt draft in Markdown, plus…

  • validate_llms_txt

    Use this when the user pastes the text of an llms.txt file and wants it checked or improved. Checks the text against the llmstxt.org format proposal: H1 title, summary blockquote, H2 sections, absolute Markdown links, duplicates, links to…

  • check_published_llms_txt

    Use this when the user asks whether a website already has an llms.txt, whether it is served correctly, or why PageSpeed Insights / Lighthouse flags it. Requests exactly one URL, https://<domain>/llms.txt, and reports HTTP status, content…

  • check_lighthouse_agentic_browsing

    Use this when the user only wants to know whether a given llms.txt text passes the Lighthouse 13.3 "Agentic Browsing" audit (llms-txt). Applies exactly its three rules: an H1 exists, at least one Markdown link, more than 50 characters. On…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "llms-txt": {
      "type": "http",
      "url": "https://www.llms-txt-generator.de/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http llms-txt-generator https://www.llms-txt-generator.de/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://www.llms-txt-generator.de/api/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.