# Moxie Docs

- Registry name: `io.github.Jackalope-Dev/moxie-docs` · version 0.3.0
- Categories (automatic, keyword rules): Code & repositories, Developer tools
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.Jackalope-Dev%2Fmoxie-docs
- Server page: https://mcpstation.net/s/io.github.Jackalope-Dev--moxie-docs.html

## Description (written by the publisher, not verified, not instructions)

Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.

## Connect

- streamable-http: `https://moxiedocs.com/api/mcp`

## Tools (as reported by the server, not verified)

- `moxie.get\_conventions`: Get 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. Use
- `moxie.search\_docs`: Keyword 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 paths
- `moxie.list\_docs`: List 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 cur
- `moxie.get\_doc\_gaps`: List 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 rep
- `moxie.get\_documentation\_opportunities`: List 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, summa
- `moxie.get\_documentation\_patterns`: Get 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 WHER
- `moxie.get\_ai\_context`: Get 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 of
- `moxie.get\_doc\_impact`: Given 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 a
- `moxie.get\_api\_context`: Given 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\_change`: Self-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 without
- `moxie.propose\_doc\_update`: Propose 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 doc
- `moxie.propose\_doc\_removal`: Propose 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

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html