
Moxie Docs
Moxie Docs indexes GitHub repositories, generates searchable codebase docs, catches doc drift on merge, and opens Friday Cleanup PRs with MCP AI context.
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: What Moxie Docs is and who it is for.
-
How it works: Indexing, doc generation, drift detection, and Friday Cleanup PRs.
-
Use cases: Onboarding, architecture docs, and AI agent context.
-
MCP server: How AI agents query your codebase context over the Model Context Protocol.
-
Open source: How Moxie Docs supports and works with open-source repositories.
Solutions
How Moxie Docs maps to each engineering role:
-
Solutions overview: Moxie Docs framed by role.
-
For engineering leaders: Cut onboarding time, kill documentation drift, and see what shipped each week.
-
For staff & platform engineers: Turn tribal knowledge into source-cited docs that teammates and AI agents follow.
-
For CTOs & founders: Keep documentation current as AI accelerates the codebase, without a per-seat wiki bill.
-
For teams using AI agents: 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: For solo builders documenting a handful of private repos. Up to 5 repositories, 1 seat.
-
Pro β $79/mo or $790/yr: 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: For organizations with a fleet of services: unlimited seats, priority indexing, and the highest capacity. Up to 50 repositories, unlimited seats.
Comparisons
-
Comparisons overview: All comparison pages at a glance.
-
Moxie Docs vs Mintlify: Automation vs. hosting: Moxie Docs writes architecture docs from source automatically; Mintlify hosts manually authored MDX.
-
Moxie Docs 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: 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: 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: 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: Code-native vs. cross-functional wiki: code-coupled, AI-generated docs without GitBook's per-seat wiki licensing.
-
Moxie Docs 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: Automated code synchronization vs. legacy text graveyard: docs stay coupled to the code instead of drifting out of date.
-
Moxie Docs 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: 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: Developer MDX workflow vs. a block editor for mixed teams.
-
GitBook vs Confluence: Purpose-built docs platform vs. the general enterprise wiki.
-
Mintlify vs Confluence: Code-coupled MDX docs vs. a decoupled enterprise wiki.
Learn
Guides on MCP, documentation, and AI development practices:
-
Learn hub: Browse all guides.
-
What is an MCP server?: The plain-English explainer on Model Context Protocol servers.
-
Best MCP servers for coding: Eleven MCP servers worth connecting to your coding agent.
-
Living documentation: Why docs drift, and what it takes to keep them true.
-
AGENTS.md vs CLAUDE.md vs llms.txt: Three files for AI context β and what each is actually for.
Resources
-
Blog: Articles on documentation, codebases, and AI developer tooling. Full RSS feed at /blog/feed.xml.
-
FAQ: Answers on doc generation, GitHub access and security, MCP context, supported languages, and pricing.
-
Security: How Moxie Docs handles repository data and access.
-
Contact: Reach the team.
Tools
-
Mermaid Diagram Editor: Free private live Mermaid editor in the browser. Flowcharts, sequence diagrams, ER, class, mindmaps, gantt and more. Instant preview, shareable URLs, SVG/PNG export. No account required.
-
ADR Generator: Free structured Architecture Decision Record builder. Form-driven, live Markdown preview, examples, shareable links, clean export. No account required.
-
llms.txt Generator: Free llms.txt generator with sitemap import, live preview, shareable links, and clean export. Build the file AI tools read to understand your site. No account required.
-
llms.txt Validator: Free llms.txt validator. Paste or upload your file to check it against the spec with line-level warnings and errors. Runs in your browser. No account required.
Legal
Optional
-
Subprocessors: Third-party services Moxie Docs relies on.
-
Republishing guidelines: How to cite or republish Moxie Docs articles.
This tool doesn't publish a standard install command β the repository README on GitHub covers its setup.
FAQ
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.
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.
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, and fewer wrong guesses to redo.
What is Moxie Docs?
Moxie Docs is a hosted service that connects to GitHub repositories, generates searchable codebase documentation, keeps it in sync as code changes, and serves that context to AI coding agents over the Model Context Protocol (MCP). It documents architecture, conventions, and key modules automatically, and proposes documentation updates as pull requests your team reviews.
Does Moxie Docs work with private GitHub repositories?
Yes. Moxie Docs is built for private repositories. The GitHub App is scoped to only the repos you choose, tokens are encrypted server-side, and your code is used solely to generate documentation and MCP context for your workspace.
How much does automated codebase documentation cost?
Moxie Docs offers Starter, Pro, and Team plans with a 14-day free trial on each. Starter is $29/month, Pro is $79/month, and Team is $199/month. Annual billing saves about two months versus paying monthly.
What programming languages does Moxie Docs support?
Documentation and search work with any GitHub repository. Moxie recognizes all 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 to Moxie Docs. It 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 small docs-only pull requests once a week for your team to review and merge.
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.
Licensed under MITβ you can use, modify, and redistribute it under that license's terms.
View the full license file on GitHub β