Moxie Docs MCP Server

Automatic documentation updates from agents, and codebase conventions to reduce token usage.

View on moxiedocs.com

Documentation

Live on Product Hunt

Use code PRODUCTHUNT for 50% off your first month, through June 30.

Continuously indexed · always current

Docs that write themselves. Agents that already know your repo.

Connect a GitHub repo and Moxie writes the documentation, flags drift when code changes, and serves your conventions to AI agents over MCP.

Connect GitHub repoStart 14-day free trial

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

  • Read-only by default
  • Scoped per repo
  • Source-cited

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 · #491Regenerated

Friday Cleanup

1 docs PR awaiting review

→ get_conventions() · 12 rulesmcp · connected

Living documentation

Documentation that notices when it's wrong.

Moxie generates architecture pages, conventions, and walkthroughs from your code, then re-checks them on every merge. When the code moves, the affected docs get flagged and rewritten instead of quietly rotting.

  • Generated from source. Architecture, conventions, and walkthroughs. Every line cites the code it came from.
  • Drift caught on merge. Each merge is checked against the docs it touches.
  • Updated, not abandoned. Stale pages are regenerated, with the diff to prove it.

See how the index stays current

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

MCP context for agents

Stop paying agents to rediscover your codebase.

Cursor, Claude Code, and Codex pull your conventions, docs, and verified commands over MCP, already formatted for agents and scoped to the task. No re-crawling the repo on every prompt.

  • 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

Without Moxie

read package.json

grep "webhook" · 38 matches

read api/billing/route.ts

read lib/billing/stripe.ts

read 11 more files…

grep "retry" · 24 matches

still inferring conventions

Every prompt, every task

With Moxieread-only

→ get_conventions()

12 rules · paths cited

→ search_docs("webhook")

top hit: billing webhook behavior

ready to write

Two scoped lookups

Friday Cleanup

A week of drift, fixed in one reviewable PR.

Every Friday, Moxie recaps the week's merges and opens a docs-only PR for anything documentation missed. You review, you merge.

  • Docs-only. Source-cited changes to documentation, never your code.
  • One PR, once a week. Small enough to review with Friday coffee.
  • You hold the merge button. 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.

Also in the box

The rest of the toolkit.

Explore all features

  • Changelog

Every merge summarized, with internal and external views you can paste anywhere.

  • Searchable workspace

Generated docs and your Markdown in one place, so new engineers skip the scavenger hunt.

  • Description alignment

PR descriptions rewritten to match your template. Your code stays untouched.

  • Doc-impact checks

Stale or missing docs flagged on the PR before it merges.

FAQ

The questions every team asks first.

Short version: Moxie reads code, writes docs, checks PRs, and asks before changing anything.

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.

Pricing

Try it on a real repo before the first charge.

Compare plans

Solo / small team

Starter

$49

/ month after trial

Up to 3 private repos, one flat price.

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

Up to 3 active private repositories

3 seats

1,000 indexed files per repo

10 manual doc update PRs per repo each month

Searchable docs

Bookmarks and highlights

Start 14-day trial

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

Most useful

Team

$199

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

For teams with a fleet of services that need weekly review, not the occasional cleanup.

Up to 10 active private repositories

Unlimited seats

5,000 indexed files per repo

Weekly Friday Cleanup

25 cleanup PRs per repo each month

Friday Recap reports

Incremental doc updates

Start the trial

Connect a repo. The first index runs in minutes.

Drift detection, MCP context, and Friday Cleanup turn on as soon as the first index lands.

Connect GitHub repoTrial details

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