Common questions about Moxie Docs

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.

For fast-moving dev teams

Ship code faster with docs your AI agents actually trust

  • 0+repos connected
  • 0%of doc PRs merged

  • Living docs from your repo. Architecture, conventions, and walkthroughs - updated on merge.

  • MCP context for agents. Cursor, Claude Code, and Codex read verified repo context - not guesses.

  • You review every docs PR. Nothing merges without your team.

Connect GitHub repoSee the interactive tour

Or try a free no-signup tool first.

14-day trial · No charge today · Scoped GitHub App

moxie workspacejackalope/api
how do webhook retries work?

  • Architecture · billing webhooks

    docs/architecture/webhooks.md

    Current

  • Convention · validate input with Zod

    12 rules · paths cited

    Current

  • Payments retry guide

    docs/billing.md

    Drift · #491
Friday Cleanup
1 docs PR awaiting review
→ get_conventions() · 12 rulesmcp · connected

Already in Cursor or Claude Code? Paste one prompt and your agent sets up Moxie itself.

Set up with a prompt

Works with the agents your team already uses

Works with Claude, Cursor, Gemini, GitHub Copilot, VS Code, Codex, Antigravity, Windsurf, Cline, Zed, JetBrains, Neovim, Warp.

MCP context for agents

Stop paying agents to rediscover your codebase.

Without a context layer, every agent re-reads your repo from scratch. Moxie feeds Cursor, Claude Code, and Codex dense, source-cited context over MCP: your conventions, docs, and verified commands, already scoped to the task. They get it on the first pass instead of burning tokens to rediscover it.

MCP context
first pass · 1 call

→search_docs("webhook retries")

## Billing webhook behaviorFailed webhooks retry **5×** with exponentialbackoff. Idempotency keys prevent double-charges.↳ cited: apps/web/src/app/api/billing/route.ts## Conventions (12)- Validate input with **Zod** at every boundary- Wrap external calls in `withRetry()`↳ cited: src/lib/validation.ts · src/lib/http.ts
Token-denseSource-cited ready to write

  • Fewer tokens.

    One scoped lookup replaces dozens of exploratory file reads.

  • Right the first time.

    Agents follow your conventions instead of guessing them.

  • Read-only and scoped.

    Context only. Never billing, settings, or the merge button.

See the MCP context

The drift tax

AI writes the code. Docs fall behind.

Code ships faster than anyone can document. Every merge widens the gap between the system and the wiki.

  • 75%

    of Google's new code is AI-generated (up from ~25% in 2024).

    Google Cloud Next, 2026

  • 58%

    of developer time goes to understanding existing code.

    Xia et al., IEEE TSE

  • 0

    of that AI-written code updates your docs by itself.

    Every team, every repo

Agents write code faster. Moxie keeps the docs - and the next agent - honest.

How Moxie catches drift

Living documentation

Documentation that notices when it's wrong.

Architecture, conventions, and walkthroughs from your code - re-checked on every merge and rewritten when they go stale.

  • From source. Architecture, conventions, walkthroughs - cited to code.
  • Checked on merge. Each merge is compared to the docs it touches.
  • Fixed, not abandoned. Stale pages regenerate with a reviewable diff.
Connect GitHub repoSee how it works
Billing webhook behavior
docs/billing.md
Drift · code changed in #491 Regenerated

@@ Retry handling @@

- Failed webhooks retry up to 3 times.

+ Failed webhooks retry 5 times with exponential backoff.

+ Idempotency keys prevent double-charges on retry.

Cited to apps/web/src/app/api/billing · updated 4m after merge

Friday Cleanup

A week of drift, fixed in one PR.

Every Friday: one docs-only PR for what documentation missed. You review. You merge.

  • Docs-only. Never your application code.
  • One PR a week. Small enough to review on Friday.
  • You merge. Nothing auto-merges. Ever.
Connect a repoHow PR checks work
Friday Cleanup
Week of Jun 1 · 9 PRs merged
Docs: catch up on this week's merges

moxie/friday-cleanup · docs-only · awaiting your review

  • docs/billing.md+12 −4
  • docs/architecture/webhooks.md+6 −1
Docs-onlySource-citedAwaiting review
Merge it, edit it, or close it. Your call.

Who are you?

Built for how you lead and build.

Same product - framed for your role.

Ready to try it

Connect a repo. The first index runs in minutes.

Living docs, drift detection, and MCP - on as soon as the first index lands. 14-day trial, no charge today.

Connect GitHub repoSee the interactive tour

14-day trial · No charge today · Pick one repo to start

Also in the box

The rest of the toolkit.

Explore all features
  • Changelog
    this week
    1. Add per-repo billing+212#491
    2. Cache dashboard claims+64#488
    3. Emit cancellation events+38#485

    Changelog

    Every merge summarized - paste internal or external views.

  • Ask this codebase
    8 sources
    how does auth work?
    Session tokens & rotationguide
    lib/auth/session.tssource

    Searchable workspace

    Generated docs and your Markdown in one place.

  • docs.mycompany.com
    public kb
    Getting Started GuideActive
    API AuthenticationActive

    Public Knowledgebases

    Publish docs on a moxiedocs.app subdomain or your domain.

    Knowledgebases
  • eng-updates
    Slack
    M
    Moxieapp

    Friday Recap - 12 PRs merged this week, docs updated for 4 of them.

    🎉 4✅ 6

    Slack

    Friday Recap and doc PRs posted where the team already works.

    Slack integration

The trust zone

Enterprise-grade security by design.

Moxie connects through a scoped GitHub App and keeps your code server-side. Here's exactly what that means.

  • Repository access
    you choose
    • acme/web-appshared
    • acme/apishared
    • acme/payrollprivate

    Scoped access

    GitHub App on only the repos you pick. Nothing else on the account.

  • Indexing
    auto-skip
    • src/server.tsindexed
    • .env.productionskipped
    • id_rsaskipped

    Code & secret privacy

    Encrypted tokens. Secrets, env files, and dependency folders skipped.

  • docs: update auth guide
    draft
    1. Opened as draft
    2. Awaiting your review
    3. You merge - never us
    Ready for review

    Human-in-the-loop

    Docs arrive as draft PRs. Your team reviews and merges.

Read the full security model

Free developer tools

Try Moxie before you connect a repo.

No account required. Useful on their own - and a fast on-ramp when you are ready for living docs grounded in your codebase.

View all free tools

  • Mermaid Diagram Editor

    Private in-browser editor with instant preview, shareable URLs, and SVG export.

    Open tool

  • SQL to ER Diagram

    Paste CREATE TABLE SQL for a live Mermaid ER diagram, SVG/PNG export, and optional AI data-model docs.

    Open tool

  • README Generator

    Structured README builder with live Markdown preview and shareable export.

    Open tool

Also free: llms.txt Generator, AGENTS.md Generator, ADR Generator, llms.txt Validator.

Need docs that stay true on every merge? Connect a repo - living docs, MCP context, and reviewable Cleanup PRs.

Connect GitHub

FAQ

The questions every team asks first.

Short version: Moxie reads your code, writes the docs, and keeps them current on every merge.

See all 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.

Pricing

Try it on a real repo before the first charge.

14-day trial. No charge today. Cancel anytime.

No subscription

Not wanting to commit to a subscription?

Grab a one-time $5 pass for two full weeks of Moxie Pro. Nothing auto-renews - and if you convert to any plan, your $5 comes off your first month.

One per workspace · counts as your trial

2 months free
Compare plans

Solo / small team

Starter

$29

/ month after trial

Up to 5 private repos, one flat price.

Search, generated docs, bookmarks, and MCP context for every codebase you connect.

Up to 5 active private repositories

1 seat

2,000 indexed files per repo

10 doc update PRs per repo each month

Searchable docs

Bookmarks and highlights

14 days to try it on a real repo. Cancel anytime.

Most popular

Pro

$79

/ month after trial

Up to 15 private repos with Friday Recaps and Cleanup PRs.

For a growing team that wants hands-off docs: weekly review and automated cleanup, not the occasional pass.

Up to 15 active private repositories

10 seats

5,000 indexed files per repo

Weekly Friday Cleanup

25 cleanup PRs per repo each month

Friday Recap reports

Incremental doc updates

14 days to try it on a real repo. Cancel anytime.

For organizations

Team

$199

/ month after trial

Up to 50 private repos with priority indexing and the highest capacity.

Unlimited team seats (bring product and QA in, not just engineers), plus priority indexing and everything in Pro.

Up to 50 active private repositories

Unlimited team seats

15,000 indexed files per repo

Weekly Friday Cleanup

50 cleanup PRs per repo each month

Priority indexing queue

Friday Recap reports

14 days to try it on a real repo. Cancel anytime.

Open-source maintainer? Request free access

Team & enterprise

Pilot Moxie across a fleet of services.

Team includes priority indexing, unlimited seats, and up to 50 repositories. We will help you scope a rollout on real repos, walk through security, and align on cadence.

Book a callSend a message

Start the trial

Connect a repo. The first index runs in minutes.

First index in minutes. 14-day trial, no charge today. Cancel anytime if it isn't a fit.

Connect GitHub repoTrial details

Pick one repository. First index in minutes. You review every docs PR.

  • Docs generated, then kept current on every merge
  • MCP context ready for Claude, Cursor, and Codex
  • Friday Cleanup PRs that wait for your review