MCP Reference

The published-docs MCP tools that let agents inspect and operate on the Documint self-dogfood project.

Transport

V1 exposes an HTTP JSON-RPC style MCP surface at POST /mcp plus a manifest at GET /mcp.

Tools

• analyze_repository
• detect_doc_drift
• generate_doc_patch
• review_doc_patch
• publish_preview
• explain_doc_trace

Why this exists

The goal is not just “AI chat on docs.” The MCP layer gives coding agents a structured way to inspect which pages are stale, why they are stale, and what repo files justify the next documentation update.

The GitHub App webhook path is upstream of this surface: repository events feed drift checks, and the MCP tools expose the resulting traces, findings, and preview actions back to agents.

Source trace principle

Every documentation artifact in V1 should be explainable:

• what files drive it,
• what doc page publishes it,
• what revision it was last verified against.