Moxie Docs
Automatic codebase documentation and MCP
Last verified:
What is Moxie Docs?
Moxie Docs is an AI-powered codebase documentation platform for GitHub repositories that automatically generates, maintains, and keeps documentation current. It indexes your GitHub repo once to create living documentation including architecture pages, conventions, and walkthroughs directly from your code. When code changes through merges, Moxie Docs detects drift and flags affected documentation for regeneration instead of letting it quietly become outdated.
The platform serves developers and engineering teams who need searchable documentation and AI agents that understand their codebase. It provides MCP (Model Context Protocol) context for AI coding assistants like Cursor, Claude Code, and Codex, allowing them to pull conventions, docs, and verified commands without re-crawling the entire repository on every prompt. This reduces token usage and helps agents follow team conventions instead of guessing.
Key features include automated drift detection on every merge, Friday Cleanup PRs that recap weekly merges and open docs-only updates, searchable docs workspace, PR description alignment, doc-impact checks that flag stale or missing docs before merging, and changelog summaries. Every line of generated documentation cites the source code it came from, and the platform operates in read-only mode with per-repo scoping.
Moxie Docs is designed for solo developers, small teams, and larger engineering teams managing multiple services. It solves pain points like outdated documentation, insufficient context for AI coding tools leading to errors, and the high manual effort required to keep repositories documented. The platform transforms static documentation into dynamic, integrated knowledge that boosts productivity and reduces onboarding time.
Moxie Docs pricing
Pricing model: Freemium
14-day trial with no charge today, cancel anytime. Starter plan: $49/month after trial - includes up to 3 private repos (one flat price), 3 seats, 1,000 indexed files per repo, 10 manual doc update PRs per repo each month, searchable docs, bookmarks and highlights, MCP context for every codebase. Team plan: $199/month after trial - includes up to 10 private repos, unlimited seats, 5,000 indexed files per repo, weekly Friday Cleanup, 25 cleanup PRs per repo each month, Friday Recap reports, incremental doc updates, MCP context. Use code PRODUCTHUNT for 50% off your first month through June 30.
Moxie Docs pros
- Automatic documentation generation from source code
- Drift detection flags outdated docs on every merge
- MCP context for AI agents reduces token usage
- Friday Cleanup PRs consolidate weekly doc updates
- Every line cites the source code it came from
- Read-only by default with scoped per-repo access
- Searchable docs workspace for easy knowledge access
- PR description alignment matches your template
- Doc-impact checks flag missing docs before merge
- No re-crawling repo on every AI prompt needed
- Agents follow team conventions instead of guessing
- 14-day trial with no charge and cancel anytime
- Changelog summaries with internal and external views
- Bookmarks and highlights for important documentation
- Incremental doc updates instead of full regenerations
Moxie Docs cons
- Limited to 3 repos on Starter plan ($49/month)
- 1,000 indexed files per repo limit on Starter
- Only 10 manual doc update PRs per repo monthly on Starter
- Team plan at $199/month may be expensive for small teams
- Friday Cleanup only available on Team plan
- New platform launched recently with limited track record
- Only supports GitHub repositories, not other platforms
- Requires team to manually review and merge doc PRs
Frequently asked questions about Moxie Docs
What happens after I connect a repo?
Moxie indexes the repository, generates searchable docs, summarizes conventions, and starts checking every new pull request for description alignment and doc impact. From then on it re-indexes on every merge to keep documentation current.
Will Moxie change my code automatically?
No. Description alignment edits the PR description on GitHub; doc updates arrive as reviewable docs-only PRs. Branch protection, code review, and merge control all stay with your team. Nothing auto-merges ever.
How does the MCP layer cut agent cost?
Agents pull your conventions, docs, gaps, and verified commands directly instead of re-crawling the codebase on every prompt. Less rediscovery means fewer tokens used and fewer wrong guesses to redo.
How does drift detection work?
Moxie re-checks generated documentation on every merge. When code changes, the affected docs get flagged and rewritten instead of quietly rotting. The diff shows exactly what changed with source citations.
What is Friday Cleanup?
Every Friday, Moxie recaps the week's merges and opens a docs-only PR for anything documentation missed. You review and merge it yourself. It includes source-cited changes to documentation only, never your code, and is small enough to review with Friday coffee.
Can I use Moxie Docs with closed-source/private repos?
Yes. Both Starter and Team plans support private repositories. Starter covers up to 3 private repos and Team covers up to 10 private repos. The platform is scoped per repo with read-only access.
What AI agents work with Moxie Docs?
Cursor, Claude Code, and Codex all pull your conventions, docs, and verified commands over MCP. The context is already formatted for agents and scoped to the task without re-crawling the repo.
How many seats are included in each plan?
Starter includes 3 seats for $49/month. Team includes unlimited seats for $199/month. Both plans provide MCP context for every codebase you connect.
What is the difference between Starter and Team plans?
Starter covers up to 3 repos with 1,000 indexed files per repo and 10 manual doc update PRs monthly. Team covers up to 10 repos with 5,000 indexed files per repo, 25 cleanup PRs monthly, weekly Friday Cleanup, and Friday Recap reports. Friday Cleanup is only on Team.
How do PR checks work for doc impact?
Doc-impact checks flag stale or missing docs on the PR before it merges. This helps catch documentation gaps early so teams can address them as part of the normal PR review process rather than after merging.