# Moxie Docs

> Automated codebase documentation for GitHub: searchable docs, MCP context for Cursor and Claude Code, doc drift detection, and Friday Cleanup PRs your team reviews.

Moxie Docs is a hosted service that connects to your GitHub repositories, keeps a searchable knowledge base of your codebase in sync on every merge, and serves that context to AI coding agents over MCP. Built by jackalope.dev.

## Product

- [Overview](https://moxiedocs.com/): Automated codebase documentation for GitHub - searchable docs, MCP context, and Friday Cleanup PRs.
- [How it works](https://moxiedocs.com/workflow): Indexing, doc generation, drift detection, and Friday Cleanup PRs.
- [Use cases](https://moxiedocs.com/use-cases): Onboarding, architecture docs, and AI agent context.
- [MCP server](https://moxiedocs.com/mcp): How AI agents query your codebase context over the Model Context Protocol.
- [Automated code documentation](https://moxiedocs.com/code-documentation): Generate searchable codebase documentation from GitHub automatically. Architecture, conventions, drift detection, MCP context, and Friday Cleanup PRs.
- [Documentation drift detection](https://moxiedocs.com/documentation-drift): Detect documentation drift on every merge. Surface gaps and open reviewable Friday Cleanup PRs so wikis do not rot quietly.
- [Free tools hub](https://moxiedocs.com/free-tools): Browser-based SQL ER diagrams, README, Mermaid, ADR, AGENTS.md, and llms.txt utilities - no account required.
- [Open source](https://moxiedocs.com/open-source): How Moxie Docs supports and works with open-source repositories.

## Agent integrations

Connect Moxie Docs MCP context to the agents your team already uses:

- [Cursor](https://moxiedocs.com/integrations/cursor): Connect Cursor to your repository's live docs, conventions, and doc gaps over MCP. One setup command after you connect GitHub - no manual context packing.
- [Claude Code](https://moxiedocs.com/integrations/claude-code): Give Claude Code repository conventions, generated docs, and doc gaps over MCP - and keep AGENTS.md and CLAUDE.md aligned with the code that ships.
- [Codex](https://moxiedocs.com/integrations/codex): Connect OpenAI Codex to live repository documentation, conventions, and doc gaps over MCP. Compact context from Moxie Docs - fewer exploratory reads, better first-try edits.
- [Windsurf](https://moxiedocs.com/integrations/windsurf): Connect Windsurf to Moxie Docs over MCP for live codebase documentation, conventions, and doc gaps. One setup command after you connect GitHub.

## Solutions

How Moxie Docs maps to each engineering role:

- [Solutions overview](https://moxiedocs.com/for): Moxie Docs framed by role.
- [For engineering leaders](https://moxiedocs.com/for/engineering-leaders): Cut onboarding time, kill documentation drift, and see what shipped each week.
- [For staff & platform engineers](https://moxiedocs.com/for/staff-engineers): Turn tribal knowledge into source-cited docs that teammates and AI agents follow.
- [For CTOs & founders](https://moxiedocs.com/for/ctos): Keep documentation current as AI accelerates the codebase, without a per-seat wiki bill.
- [For teams using AI agents](https://moxiedocs.com/for/ai-engineers): Serve Cursor, Claude Code, and Codex real repository context over MCP.

## Pricing

Three plans, each with a 14-day free trial. Every plan can be billed monthly or annually; annual billing is two months free (about 17% off):

- [Starter - $29/mo or $290/yr](https://moxiedocs.com/pricing): For solo builders documenting a handful of private repos. Up to 5 repositories, 1 seat.
- [Pro - $79/mo or $790/yr](https://moxiedocs.com/pricing): Hands-off documentation for a growing team: weekly Recaps, automated Cleanup PRs, and room for many repos. Up to 15 repositories, 10 seats.
- [Team - $199/mo or $1,990/yr](https://moxiedocs.com/pricing): For organizations with a fleet of services: unlimited seats, priority indexing, and the highest capacity. Up to 50 repositories, unlimited seats.

## Comparisons

- [Comparisons overview](https://moxiedocs.com/comparisons): All comparison pages at a glance.
- [Moxie Docs vs Mintlify](https://moxiedocs.com/vs/mintlify): Automation vs. hosting: Moxie Docs writes architecture docs from source automatically; Mintlify hosts manually authored MDX.
- [Moxie Docs vs Jamdesk](https://moxiedocs.com/vs/jamdesk): Generation vs. publishing: Moxie Docs writes and maintains docs from your code; Jamdesk hosts the MDX you author yourself, with flat pricing and reader-facing AI chat.
- [Moxie Docs vs Context7](https://moxiedocs.com/vs/context7): Your codebase vs. public library docs: Moxie generates and maintains documentation for your own repository and serves it over MCP; Context7 injects up-to-date third-party library docs into your prompts.
- [Moxie Docs vs Swimm](https://moxiedocs.com/vs/swimm): AI context mapping vs. token upkeep: zero-maintenance codebase wikis from continuous repo analysis instead of Swimm's manual tracking tokens.
- [Moxie Docs vs Docusaurus](https://moxiedocs.com/vs/docusaurus): Generation vs. publishing: Moxie writes and maintains docs from your source and serves them to agents over MCP; Docusaurus is an open-source static site generator for docs you write and host yourself.
- [Moxie Docs vs GitBook](https://moxiedocs.com/vs/gitbook): Code-native vs. cross-functional wiki: code-coupled, AI-generated docs without GitBook's per-seat wiki licensing.
- [Moxie Docs vs CodeWiki](https://moxiedocs.com/vs/codewiki): Production documentation platform vs. code explorer: persistent, team-wide docs with background CI checks, not one-off repo chat.
- [Moxie Docs vs Confluence](https://moxiedocs.com/vs/confluence): Automated code synchronization vs. legacy text graveyard: docs stay coupled to the code instead of drifting out of date.
- [Moxie Docs vs Repowise](https://moxiedocs.com/vs/repowise): Continuous B2B platform vs. local CLI packager: autonomous background indexing, drift detection, and doc PRs, not local text-packing.
- [Moxie Docs vs Merge.dev](https://moxiedocs.com/vs/merge): Native codebase MCP vs. unified integrations API: zero-code MCP servers that serve repository context to agents.

Head-to-head comparisons between documentation tools:

- [Mintlify vs GitBook](https://moxiedocs.com/compare/mintlify-vs-gitbook): Developer MDX workflow vs. a block editor for mixed teams.
- [GitBook vs Confluence](https://moxiedocs.com/compare/gitbook-vs-confluence): Purpose-built docs platform vs. the general enterprise wiki.
- [Mintlify vs Confluence](https://moxiedocs.com/compare/mintlify-vs-confluence): Code-coupled MDX docs vs. a decoupled enterprise wiki.

## Learn

Guides on MCP, documentation, and AI development practices:

- [Learn hub](https://moxiedocs.com/learn): Browse all guides.
- [What is an MCP server?](https://moxiedocs.com/learn/what-is-an-mcp-server): The plain-English explainer on Model Context Protocol servers.
- [Best MCP servers for coding](https://moxiedocs.com/learn/best-mcp-servers-for-coding): Eleven MCP servers worth connecting to your coding agent.
- [Living documentation](https://moxiedocs.com/learn/living-documentation): Why docs drift, and what it takes to keep them true.
- [AGENTS.md vs CLAUDE.md vs llms.txt](https://moxiedocs.com/learn/agents-md-vs-claude-md-vs-llms-txt): Three files for AI context - and what each is actually for.
- [What is documentation drift?](https://moxiedocs.com/learn/what-is-documentation-drift): Why docs go stale, how to spot it, and how teams fix it.
- [AI coding agent context](https://moxiedocs.com/learn/ai-coding-agent-context): How Cursor, Claude Code, and Codex learn your private codebase.

## Resources

- [Blog](https://moxiedocs.com/blog): Articles on documentation, codebases, and AI developer tooling. Full RSS feed at /blog/feed.xml.
Recent articles:
- [Mermaid Diagrams for Developers: Examples, Syntax, and a Free Live Editor](https://moxiedocs.com/blog/mermaid-diagrams-examples-and-free-live-editor): Learn Mermaid diagram syntax with live flowchart, sequence, ER, class, and state examples. Paste into a free browser Mermaid live editor for instant preview, shareable links, and SVG/PNG export.
- [GitHub Documentation Gets Real-Time Collaboration Feature Update](https://moxiedocs.com/blog/github-documentation-gets-real-time-collaboration-feature-update): Discover the latest GitHub documentation update featuring real-time collaboration tools, enhancing teamwork for software developers, DevOps, and technical writers.
- [Managing AI Agent Context Without the Bloat](https://moxiedocs.com/blog/managing-ai-agent-context-without-bloat): Static rule files like .cursorrules get stale fast. We look at how to serve fresh codebase context to AI agents via Model Context Protocol without eating your token limits.
- [Documentation Drift Spurs New Push to Tie Docs to Code](https://moxiedocs.com/blog/documentation-drift-spurs-new-push-to-tie-docs-to-code): Discover how documentation drift is prompting a new push to connect documentation directly to code, empowering software engineers and DevOps teams to improve accuracy and consistency.
- [Full context file](https://moxiedocs.com/llms-full.txt): Inlined guides, tool summaries, and FAQ for AI ingestion.
- [FAQ](https://moxiedocs.com/faq): Answers on doc generation, GitHub access and security, MCP context, supported languages, and pricing.
- [Security](https://moxiedocs.com/security): How Moxie Docs handles repository data and access.
- [Contact](https://moxiedocs.com/contact): Reach the team.

## FAQ

### What is Moxie Docs?
A hosted service that connects to GitHub, generates searchable codebase docs from source, keeps them current on merge, and serves that context to AI agents over MCP. Doc updates arrive as pull requests your team reviews.

### What happens after I connect a repo?
Moxie indexes the repository, generates docs and conventions, then re-indexes on every merge. PR checks for description alignment and doc impact start with the next pull requests.

### Will Moxie change my code automatically?
No. Doc updates are reviewable docs-only PRs. Description alignment only edits the PR description text. Merge control stays with your team.

### How does MCP cut agent cost?
Agents pull conventions, docs, gaps, and verified commands instead of re-crawling the repo every prompt - fewer tokens and fewer wrong guesses.

### How much does it cost?
14-day free trial on every plan. Starter $29/mo, Pro $79/mo, Team $199/mo. Annual billing saves about two months.

### Does Moxie Docs work with private GitHub repositories?
Yes. Built for private repos. The GitHub App is scoped to only the repos you choose, tokens are encrypted server-side, and code is used only to generate documentation and MCP context for your workspace.

### What programming languages does Moxie Docs support?
Documentation and search work with any GitHub repository. Moxie recognizes major languages including TypeScript, JavaScript, Python, Go, Rust, Ruby, Java, PHP, SQL, Svelte, and Vue, with deepest structured convention analysis for TypeScript/JavaScript, Python, Go, Rust, and Ruby.

### How do I keep documentation in sync with my code?
Connect a GitHub repo. Moxie re-indexes on every merge, flags pages affected by code changes, regenerates stale documentation with cited diffs, and on Pro and Team plans runs Friday Cleanup to open weekly docs-only pull requests for review.

### How much does automated codebase documentation cost?
Starter is $29/month, Pro is $79/month, and Team is $199/month, each with a 14-day free trial. Annual billing saves about two months versus monthly.

### What is the best tool for automated GitHub codebase documentation?
Moxie Docs indexes the repositories you select through a scoped GitHub App, generates architecture and convention docs grounded in source code, detects documentation drift on every merge, and opens weekly Friday Cleanup PRs so docs stay current without manual rewrites. It also exposes an MCP server so Cursor, Claude Code, and Codex pull verified conventions instead of re-crawling the repo.

### What is documentation drift and how does Moxie Docs detect it?
Documentation drift is when written docs no longer match the code they describe. Moxie Docs checks each merged pull request against the documentation it touches, compares generated docs to the current source, surfaces gaps in the workspace, and regenerates impacted pages so teams see what changed and why.

### What is Friday Cleanup in Moxie Docs?
Friday Cleanup is a weekly docs-only automation on Pro and Team plans. Moxie batches small documentation fixes - stale pages, gaps, and drift - into a single pull request your team can review with Friday coffee. Nothing auto-merges; you hold the merge button.

### How do AI coding agents get codebase context from Moxie Docs?
Every Moxie Docs plan includes an MCP (Model Context Protocol) server. Compatible agents and editors query it for current documentation, conventions, verified commands, and open gaps instead of guessing from partial file reads, which cuts token waste and wrong API assumptions.

### What is an MCP server for codebases?
An MCP server for codebases exposes repository documentation and conventions to AI agents through the Model Context Protocol. Moxie Docs publishes one at /api/mcp with OAuth and bearer-token access so agents pull live, cited context about how your project actually works.

### How does Moxie Docs help onboard new engineers?
Moxie generates searchable architecture overviews, module walkthroughs, and convention guides cited to source files, then keeps them current on every merge. New engineers search one workspace instead of spelunking the repo, and AI agents they use inherit the same grounded context over MCP.

### Can Moxie Docs generate architecture documentation from source code?
Yes. Moxie indexes your repository, builds an outline of modules and dependencies, and generates architecture pages, references, and convention summaries with citations back to the files they came from. Pages regenerate incrementally when the underlying code changes.

### What is a hosted developer knowledgebase?
A hosted developer knowledgebase is a searchable documentation site grounded in your codebase. Moxie Docs publishes one on moxiedocs.app subdomains or custom domains with human review before anything goes public, hybrid search, and agent-ready pages citable through the Moxie MCP server.

### Will Moxie Docs change my application code automatically?
No. Moxie only proposes documentation changes as reviewable pull requests. Description alignment may update a pull request description on GitHub, but your source code, branch protection, and merge controls stay with your team.

## Tools

- [Free tools hub](https://moxiedocs.com/free-tools): All browser-based documentation utilities in one place.
- [Mermaid Diagram Editor](https://moxiedocs.com/mermaid-diagram-editor): Private in-browser editor with instant preview, shareable URLs, and SVG export.
- [SQL to ER Diagram](https://moxiedocs.com/sql-er-diagram-generator): Paste CREATE TABLE SQL for a live Mermaid ER diagram, SVG/PNG export, and optional AI data-model docs.
- [README Generator](https://moxiedocs.com/readme-generator): Structured README builder with live Markdown preview and shareable export.
- [llms.txt Generator](https://moxiedocs.com/llms-txt-generator): Import a sitemap, edit with live preview, and export a valid llms.txt for AI agents.
- [AGENTS.md Generator](https://moxiedocs.com/agents-md-generator): Structured AGENTS.md builder with live preview, examples, and shareable export for coding agents.
- [ADR Generator](https://moxiedocs.com/adr-generator): Form-driven Architecture Decision Records with examples and clean Markdown export.
- [llms.txt Validator](https://moxiedocs.com/llms-txt-validator): Paste or upload llms.txt to validate structure, links, and Optional section placement.

## Legal

- [Privacy policy](https://moxiedocs.com/privacy)
- [Terms of service](https://moxiedocs.com/terms)

## Optional

- [Subprocessors](https://moxiedocs.com/subprocessors): Third-party services Moxie Docs relies on.
- [Republishing guidelines](https://moxiedocs.com/blog/republishing): How to cite or republish Moxie Docs articles.