The docs MCP server may be the most powerful AI integration on the site but it's buried at the bottom of llms.txt. Add a /docs/for-ai section (index, choosing-an-interface, terminology, mcp, llms-txt, openapi, schemas, retrieval-guidance) plus a navbar entry. The MCP page should cover what the server provides, transports, auth, client configuration for Claude Desktop, Claude Code, Cursor, VS Code, and generic clients, tool inventory, example questions, and troubleshooting. Audit §6.
The choosing-an-interface and terminology pages are published views of #562's manifest and #561's registry, not independently authored routing content, and the llms-txt page documents #560's format — so those pages come after that work. The MCP guide half has no dependencies and can start anytime.
The section also needs the two remaining pages from the audit's tree: a citation policy (which URL form to cite — canonical HTML or .md, and how to reference a specific identifier) and a changelog (what changed in the docs between versions, so a model can tell whether its cached copy is stale). Both are small, and neither depends on #561 or #562.
The docs MCP server may be the most powerful AI integration on the site but it's buried at the bottom of llms.txt. Add a /docs/for-ai section (index, choosing-an-interface, terminology, mcp, llms-txt, openapi, schemas, retrieval-guidance) plus a navbar entry. The MCP page should cover what the server provides, transports, auth, client configuration for Claude Desktop, Claude Code, Cursor, VS Code, and generic clients, tool inventory, example questions, and troubleshooting. Audit §6.
The choosing-an-interface and terminology pages are published views of #562's manifest and #561's registry, not independently authored routing content, and the llms-txt page documents #560's format — so those pages come after that work. The MCP guide half has no dependencies and can start anytime.
The section also needs the two remaining pages from the audit's tree: a citation policy (which URL form to cite — canonical HTML or
.md, and how to reference a specific identifier) and a changelog (what changed in the docs between versions, so a model can tell whether its cached copy is stale). Both are small, and neither depends on #561 or #562.