// MCP
Give agents the context they keep trying to rediscover.
Moxie exposes repo-specific documentation, conventions, known gaps, and verified commands through compact MCP tools — formatted for agents, backed by the same index your team reads.
- Fewer tokens. One scoped lookup replaces dozens of exploratory file reads, every prompt.
- Never stale. The index re-checks on every merge, so agents read what the code does now.
- Read-only and scoped. Context only — never billing, settings, or the merge button.
Task: add retry handling to the billing webhook
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
→ get_conventions()
12 rules · paths cited
→ get_doc_impact(billing/route.ts)
2 docs to update in this PR
→ search_docs("webhook retries")
top hit: billing webhook behavior
ready to write
Three scoped lookups
The toolbox
Eight tools, one continuously updated index.
Everything an agent should know before editing — and the tools to land doc updates in the same PR as the code change.
moxie.get_conventions
Returns categorized repo conventions, confidence, and evidence paths agents should follow before editing.
moxie.search_docs
Searches generated docs and source-linked explanations for implementation details, APIs, flows, and patterns.
moxie.get_doc_gaps
Lists missing or stale documentation areas with severity, summaries, and suggested doc paths.
moxie.get_documentation_opportunities
Lists recommended documentation updates agents should consider while planning or finishing code changes.
moxie.get_documentation_patterns
Explains where this repo keeps docs today so generated updates follow the team's existing structure.
moxie.get_ai_context
Provides compact agent-ready context: setup status, commands, conventions, docs, gaps, and team notes.
moxie.get_doc_impact
Given the file paths an agent plans to change, returns the matching conventions, doc gaps, and existing docs to update in the same PR, and flags net-new or undocumented paths.
moxie.propose_doc_update
Resolves where a doc should live and returns the path and content for the agent to write into its own branch, so docs land in the same PR as the code change.
Setup
Works where your agents already work.
- Cursor
- Claude Code
- VS Code / Copilot
- Codex
- Gemini CLI
- 01
Create a repo token
Stored encrypted. Reveal, rotate, or revoke it anytime.
- 02
Add the endpoint
Copy-paste configs for each client are generated in your dashboard.
- 03
Agents read first
Conventions, docs, and gaps land in context before the first edit.
Your agents are re-reading the repo right now.
Connect a repo and the MCP endpoint goes live with the first index.