Moxie Docs
Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.
https://moxiedocs.com/api/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- moxie-docs
- Version
- 0.4.0
- Capability keys
- tools, resources, prompts
- Tool names
- moxie.get_conventions, moxie.search_docs, moxie.list_docs, moxie.get_doc_gaps, moxie.get_documentation_opportunities, moxie.get_documentation_patterns, moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context, moxie.review_change, moxie.propose_doc_update, moxie.propose_doc_removal
Use Moxie Docs BEFORE writing code so any required documentation updates land in the same pull request as the change. Recommended flow: 1. Call `moxie.get_ai_context` to load repo status, verified commands, top conventions, and open gaps. 2. Before editing a file, call `moxie.get_doc_impact` with the file paths you intend to change. It returns the docs/gaps/conventions that apply AND flags paths that are net-new or undocumented (e.g. a new API surface) so you can document them in the same PR. 3. Use `moxie.get_documentation_patterns` to decide where new docs belong, and `moxie.get_conventions` for category-specific rules. 4. After you make the change and BEFORE you commit, call `moxie.review_change` with the new contents of the files you changed (and any deletedPaths). It flags convention breaches, docs your change makes false, undocumented new surface, and broken references. Fix every must-fix finding and re-run until the verdict is clean. 5. When you add or update a doc, call `moxie
Reported Aug 17, 2026, 05:05 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 210ms
- respondsMCP initialize · 8s limit · HTTP 200 · 1,316ms
- respondsMCP initialize · 8s limit · HTTP 200 · 66ms
- respondsMCP initialize · 8s limit · HTTP 200 · 1,956ms