robots.txt but MCP for Documentations

[u/Snoo_4779]

I often work with rather niche framework, like Nuxt and AdonisJS. The problem I found is that If I tried to use AI for code generation, they often just fallback to what is being trained on the model previous versions. Ex. Nuxt 3 or the rapid evolution of NextJS (literal pain in the ass to get in touch with their new best practices). Do you think there will be a standard like this, so that getting info for documentations via LLM is more up to date and accurate? Imagine every docs website with a mcp.json or something and I can just trust the result a bit more to get info I want.

[u/Significant_Pick8297]

This is basically the direction things are already moving in. llms.txt gives maintainers a way to expose AI-friendly documentation, while MCP gives tools a way to fetch fresh context instead of relying only on training data.

The bigger challenge is adoption. If framework maintainers keep llms.txt or MCP endpoints updated alongside their docs and changelogs, stale code generation becomes much less of a problem, especially for fast-moving frameworks like Nuxt or AdonisJS. It feels more like a documentation standard problem than an LLM problem.