Moxie Docs

Moxie Docs turns a GitHub repository into source-cited documentation that updates as code changes, and exposes the same context to AI agents over MCP. Doc fixes arrive as human-reviewed pull requests, with an optional hosted public knowledgebase and a weekly Friday Cleanup recap on paid plans.

Moxie Docs is a documentation layer for GitHub repositories. It reads the source code, produces explanations of architecture, key flows and conventions, and attaches citations back to the files and tests each explanation draws on. When code changes, the tool detects the resulting documentation drift and proposes updates as pull requests rather than silently rewriting pages. The stated purpose is to give teammates and AI coding agents a shared, current picture of how a codebase actually works. The agent angle is the differentiator. Moxie Docs exposes repository context over MCP, so assistants such as Claude, Cursor and Codex can pull current conventions and architecture at the start of a session instead of rediscovering them. The site frames this as reduced rediscovery cost and fewer tokens spent re-learning the same patterns. For humans, the same knowledge base becomes a searchable onboarding path: architecture explained, key flows mapped, conventions captured with source references. In daily use the workflow is deliberately conservative. After a repository is connected through a scoped GitHub App, the tool indexes it and generates docs. Documentation fixes arrive as pull requests that a person reviews and merges; application code is not touched and nothing auto-merges. On Pro and Team plans a weekly Friday Recap batches the drift into a Cleanup PR, and users still receive the recap even when no useful doc changes were found. A separate public knowledgebase can be published to a hosted subdomain with search, a changelog and llms.txt, gated behind human approval. It fits teams that treat documentation as maintenance work nobody owns, and smaller groups already using AI coding agents that lack repository context. It is not a general wiki or a writing tool: the product is bound to GitHub, and the value depends on accepting a pull request review habit. Compared with hand-written docs sites it trades editorial control for continuous freshness; the pricing ladder from a free single-repo tier through Starter, Pro and Team scales by repositories, seats, indexed files and monthly doc PRs.