You answer the same questions every week
Where does this live, why is it built this way, what's the convention here? The context exists only in your head and your Slack history.
For staff & platform engineers
Stop being the codebase's human cache.
Staff and platform engineers carry the architecture in their heads, and pay for it in interrupt-driven questions and review comments that explain the same conventions over and over. Moxie Docs turns that tribal knowledge into source-cited documentation and serves it to teammates and AI agents alike, so the context lives in the repo instead of your DMs.
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?
AI agents ignore your conventions
Cursor and Claude Code rediscover the codebase on every prompt and guess at patterns you've already standardized, so you catch them in review.
Architecture docs are always out of date
The one diagram you drew is six refactors stale, and keeping it current is never the priority over real work.
The fix
What Moxie Docs gives senior engineers
Architecture captured from source
Moxie maps module dependencies and writes architecture pages and walkthroughs, each cited line-by-line to the code it came from, then regenerates them when the code moves.
Conventions agents actually follow
The MCP layer serves your conventions, verified commands, and known boundaries to coding agents before they write, so they follow house patterns the first time instead of guessing.
Answers that aren't in your DMs
Teammates search one workspace of generated docs plus your existing Markdown, so the repeat questions resolve themselves before they reach you.
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.