MCP For API vs Moxie Docs MCP

MCP For API tools

No tool names declared yet. Check the project README from the listing page.

Moxie Docs MCP tools 12

• moxie.get_ai_contextCompact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.
• moxie.get_doc_impactGiven the paths you're about to change (and any you're deleting), returns the conventions, gaps, and existing docs whose evidence overlaps them - and flags net-new/undocumented surfaces.
• moxie.get_api_contextGiven paths you're about to touch, returns structured context for any API endpoints they map to: method, path, schema, and known consumers/features.
• moxie.review_changeSelf-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docs, undocumented surface, and broken references.
• moxie.get_conventionsDiscovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.
• moxie.search_docsSemantic + keyword search over generated docs, conventions, gaps, and AI context.
• moxie.get_doc_gapsUnresolved documentation gaps with severity and the paths they concern.
• moxie.get_documentation_opportunitiesRecommended doc work: missing docs, drift repairs, and PR templates.
• moxie.get_documentation_patternsHow the repository organizes and maintains its docs (where new docs belong).
• moxie.list_docsPaginated, section-grouped table of contents of every generated doc.
• moxie.propose_doc_updateAdd or update a doc as part of your current change; returns the target path + Markdown to write into your branch.
• moxie.propose_doc_removalRemove a Moxie-tracked doc your change makes obsolete; returns the path to delete in your branch.