Same questions every week
Where it lives, why it is built that way, what the convention is - only in your head and Slack.
For staff & platform engineers
Stop being the codebase's human cache.
Architecture lives in your head; teammates and agents keep asking. Moxie turns that into source-cited docs and MCP context so the repo holds the answers.
Conventions
12 rules- Errors use AiUnavailableError
lib/ai/errors.ts
- Webhooks are idempotent by key
api/billing/route.ts
- Timestamps via parseTimestampMs
lib/time.ts
Served to teammates and agents
The problem
Sound familiar?
Agents ignore conventions
They rediscover the repo each prompt and guess - you catch it in review.
Architecture docs go stale
The diagram is six refactors old; updating it is never the priority.
The fix
What you get
Architecture from source
Module maps and walkthroughs, cited to code, regenerated when code moves.
Conventions agents follow
MCP serves house rules and verified commands before the first edit.
Answers outside your DMs
One workspace for generated docs and Markdown - fewer interrupts.
FAQ
Questions, answered
How does the MCP layer cut agent cost?+
Agents pull your conventions, docs, gaps, and verified commands directly over MCP instead of re-crawling the codebase on every prompt. One scoped lookup replaces dozens of exploratory file reads. That means fewer tokens, and fewer wrong guesses to redo in review.
Is the MCP server read-only?+
Yes. The MCP layer is context-only and scoped per repository. It exposes conventions, docs, and citations, never billing, settings, or the merge button.
Does it work with my agent?+
Moxie exposes a standard Model Context Protocol server, so Claude Code, Cursor, Codex, and other MCP-aware tools can query repository context directly.
Get started
See what the first index finds.
Connect a repository and review your first source-cited docs in minutes. 14-day trial, no charge today, cancel anytime.