Moxie Docs
io.github.Jackalope-Dev/moxie-docs · v0.3.0
Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.
MCPremoteno credentialsDocuments & PDFKnowledge & docsDeveloper tools
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 12 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 80/100
What it does: 12 tools · 10 read, 2 write · Documents & PDF, Files & storage, Developer tools
Test call moxie.get_conventions: needs a key: rpc error: Unauthorized. Use a valid Moxie Docs repository MCP token. (982 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +2
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://moxiedocs.com/api/mcpTools
12 tools listed at last check
moxie.get_conventionsGet the coding conventions Moxie Docs inferred for the repository. Read-only; no side effects. Returns a Markdown list grouped by category (e.g. testing, structure, docs, review); each convention has a title, summary, confidence score, agent guidance, and the source file paths that evidence it. Usemoxie.search_docsKeyword and semantic search across the connected repository's generated docs, conventions, documentation gaps, AI-context notes, and indexed code. Read-only; no side effects. Returns ranked matches in Markdown grouped into Documentation and Code sections, each with a title, snippet, and source pathsmoxie.list_docsList the repository's generated documentation as a browsable table of contents - every doc page, not a query-filtered subset. Read-only; no side effects. Returns Markdown grouped by section, each entry with its title, slug, repository path, and source paths, plus the total count and a pagination curmoxie.get_doc_gapsList the unresolved documentation gaps Moxie Docs found - areas of the codebase that lack docs. Read-only; no side effects. Returns a Markdown list, each gap with a title, severity, summary, and suggested file paths. This is gaps only; for the full prioritized work queue that also includes drift repmoxie.get_documentation_opportunitiesList the actionable documentation updates Moxie Docs recommends as a prioritized queue: missing docs, drift repairs, and PR-template work. Read-only; no side effects. Returns a Markdown list, each opportunity with a title, kind (documentation_gap | documentation_drift | pr_template), severity, summamoxie.get_documentation_patternsGet Moxie Docs' summary of how THIS repository organizes and maintains documentation - where docs live relative to code and how they are kept current. Read-only; no side effects. Returns a Markdown list of pattern entries, each with a title, explanation, and source citations. Use this to decide WHERmoxie.get_ai_contextGet the compact briefing an agent should read before editing this repository: index status, verified commands, agent tips, top conventions, open documentation gaps, and queued documentation opportunities. Read-only; no side effects. Returns a single Markdown document. Call this first at the start ofmoxie.get_doc_impactGiven the file paths an agent is about to change (and optionally a subset being deleted), return the conventions, documentation gaps, and existing/related docs whose evidence overlaps those paths, plus a net-new/undocumented analysis and any removal candidates. Read-only; no side effects. Returns amoxie.get_api_contextGiven file paths an agent is about to touch, return structured context for any API endpoints they map to: method, path, request/response schema, and known consumers/features. Read-only; no side effects. Call this before editing API route or schema code, alongside get_doc_impact.moxie.review_changeSelf-review a change you are about to commit BEFORE opening the PR. Pass the proposed new state of each changed file (and any deleted paths); Moxie Docs returns a severity-ranked list of violations to fix: convention breaches, docs your change makes factually false, net-new API/surface added withoutmoxie.propose_doc_updatePropose a documentation file to add or update as part of YOUR current change. Records a new proposal each call (not idempotent) and does NOT modify your repository or open a PR - Moxie Docs resolves the target path and returns the path + Markdown for YOU to write into your working branch, so the docmoxie.propose_doc_removalPropose deleting a Moxie Docs-tracked documentation file that your change makes irrelevant, as part of YOUR current change. Moxie Docs validates the path and returns it for you to delete in your working branch; Moxie Docs itself does not delete files or open a PR - the deletion happens in your branc
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.github.Jackalope-Dev/moxie-docs)