The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Agentdocs listing page.
Fresh, source-verified docs for building MCP servers and Claude agents — served straight to your AI coding agent over MCP.
Coding agents hallucinate on fast-moving APIs like the Model Context Protocol and the Claude Agent SDK: training data lags the spec, so you get plausible-but-wrong imports, deprecated patterns, and invented options. agentdocs is a local MCP server that gives your agent a curated, source-verified corpus to search instead of guessing.
list_topics, search_docs, get_docverified flag set only after human review against the sourceRequires Node.js 18+.
mcp.json)Then ask your agent things like "check agentdocs for how MCP stdio handles logging" or "search agentdocs for the Streamable HTTP session header" — it will call the tools and answer from the verified corpus.
| Tool | Use it to |
|---|---|
list_topics | See every curated doc, its topic, source URL, and verified status |
search_docs(query, topic?) | Get ranked, source-attributed snippets for a question |
get_doc(id) | Read the full verified markdown of one document |
The Model Context Protocol (spec 2025-11-25) and building MCP servers / Claude agents.
Corpus grows over time; run list_topics for the current set.
Every document records the date it was last verified against its primary source. Sources
are diffed on a regular cadence; when one drifts, the affected doc is re-verified and a new
version is published. Using mcp-agentdocs@latest (as above) keeps you on the current corpus.
See CHANGELOG.md for what changed and when.
Curation is the point: npm run ingest fetches upstream sources for review but never
silently overwrites a curated doc — a human diffs, promotes, and sets verified: true
in corpus/manifest.json only after checking the content against its source. Run
npm run check-freshness to flag docs that have drifted or are due for re-verification.
MIT