Posts tagged “MCP”
Measurable documentation for the agent era
Documentation is increasingly read — and acted on — by AI agents, while coding agents ship product changes faster than any team can hand-maintain docs. Accuracy and coverage stop being nice-to-haves and become measurable requirements. How Git2Docs measures documentation against your shipped code via an MCP validation loop that converges to zero findings in an hour — and how repo-health signals let your own coding agent raise fidelity over time.
Connecting your docs to AI agents: MCP, llms.txt, and Markdown
The reader of your documentation is increasingly a coding agent, not a person browsing a page. What that means in practice — MCP servers, llms.txt, and Markdown content negotiation — how to expose your docs to Cursor, Claude Code, and ChatGPT, and why the hard part isn’t the plumbing but keeping the content true enough for an agent to trust.