Agents rediscover the codebase every prompt
Dozens of exploratory file reads and greps per task, repeated for every new conversation, all billed in tokens.
For teams building with AI agents
Give your agents the repo context they keep guessing at.
Cursor, Claude Code, and Codex re-crawl your codebase on every prompt and infer conventions you've already standardized. That burns tokens and produces code you fix in review. Moxie Docs exposes your conventions, docs, gaps, and verified commands over the Model Context Protocol, already formatted for agents and scoped to the task.
MCP session
read-only→ get_conventions()
12 rules · paths cited
→search_docs("webhook")
top hit: billing webhook behavior
ready to write
Two scoped lookups, not 40 file reads
The problem
Sound familiar?
Generated code ignores your conventions
Without your patterns in context, agents guess, and you catch the mismatches in review instead of shipping.
Context windows fill with the wrong files
Stuffing the whole repo into the prompt is expensive, noisy, and still misses the conventions that actually matter.
The fix
What the MCP layer gives your agents
Two scoped lookups, not 40 file reads
Agents call get_conventions and search_docs and get exactly the context they need, replacing dozens of exploratory reads with structured, source-cited answers.
Code that's right the first time
Agents follow your conventions and respect known boundaries because they're handed them up front, instead of inferring them from a partial crawl.
Docs updated in the same PR as the work
When an agent changes code, Moxie can propose the matching documentation update in the same pull request, so docs ship with the change, not weeks later.
FAQ
Questions, answered
Which agents and tools does Moxie support?+
Any MCP-aware client. Claude Code, Cursor, and Codex can query Moxie's Model Context Protocol server directly for conventions, docs, gaps, and verified commands.
Is the MCP server read-only?+
Yes. It's context-only and scoped per repository: conventions, docs, and citations, never billing, settings, or the merge button.
How much does this actually save?+
One scoped lookup replaces dozens of exploratory file reads per task, repeated across every prompt and conversation. You spend fewer tokens rediscovering the repo, and redo fewer wrong guesses in review.
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.