robots.txt but MCP for Documentations
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…
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.
已收录讨论
Do you mean https://llmstxt.org/ ?
Hey! This is what I'm looking for. It seems that Google is adapting this on their SEO already. edit: Thank you for the info
This seems to be an automated websearch and saving it as md for context. My itch was that it is not managed by the documentation maintainers and it only as good by the efforts of the Context7 team on this MCP. The pricing however... Kinda hope that tech will not move in this direction imo.
Exactly the pain point, If you use new versions of framework/libraries that isn't in the realm of the training data of the model. it will always opt in on what current version it knows. I tried having it get the latest documentation with web search and saving the result locally. More often it is hit or miss, worse new session only inherit much less from the saved context unless your framework/libraries is loved by the LLM like NextJS and Tailwind
Yeah I heard that because grok is more often retrained with new datas. However for making llm override stale context rather than having to wait for the next model iteration. There seems to be already many attempts for standardization from the replies here, I saw that there is already effort on this via llmstxt.org shared by u/CorpT. But I can see now that it may take long before we have a decent LLM that can update its context. For now it is just matter of making your current session rich as possible with MCPs ex. Context7 shared by u/TheBigLewinski.
I am starting to think that I am in the Survivor Bias here the negative version. Probably because of the major releases last year, ex. Nuxt 4, AdonisJS 7, especially BullMQ I keep seeing last year commits from my peers with the deprecated implementations. As for local context for me, would only go as much. Works on few prompts then back to deprecated patterns again.
It's pretty easy (for me at least) to just drop in the latest docs / change logs. Some will even do a quick web search for you to pull in the latest data, if you turn on that functionality. Or just use slightly older libraries. I haven't really found it to be a big blocker, or problem that needs to be solved beyond just 60 seconds of additional effort once or twice a week.
I don’t see it happening. LLMs need training data first.
Have you tried deepwiki MCP? If the framework is there as a public repo you will get up to date answers on how to use it from your LLM. https://deepwiki.com/ Example nextjs https://deepwiki.com/vercel/next.js
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.
a lot of ai will use old data. I use https://grok.com because their data is very recent
You're looking for Context7 MCP.