# Moxie-Docs-MCP [Verified] [Health: Active]

**Category:** 🧠 Knowledge & Memory  
**Repository:** https://github.com/Jackalope-Dev/Moxie-Docs-MCP  
**GitHub Stars:** 2  
**npm Downloads (last month):** 135  
**Views:** 46  
**Installs:** 25  
**Upvotes:** 4  
**Directory Page:** https://allmcps.com/mcp/moxie-docs-mcp

## Description
MCP & Agent Skills for Automated Documentation, and codebase conventions + context

## Tools
Capabilities this server exposes over MCP:

- **moxie.get_ai_context** — Compact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.
- **moxie.get_doc_impact** — Given 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_context** — Given 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_change** — Self-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_conventions** — Discovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.
- **moxie.search_docs** — Semantic + keyword search over generated docs, conventions, gaps, and AI context.
- **moxie.get_doc_gaps** — Unresolved documentation gaps with severity and the paths they concern.
- **moxie.get_documentation_opportunities** — Recommended doc work: missing docs, drift repairs, and PR templates.
- **moxie.get_documentation_patterns** — How the repository organizes and maintains its docs (where new docs belong).
- **moxie.list_docs** — Paginated, section-grouped table of contents of every generated doc.
- **moxie.propose_doc_update** — Add or update a doc as part of your current change; returns the target path + Markdown to write into your branch.
- **moxie.propose_doc_removal** — Remove a Moxie Docs-tracked doc your change makes obsolete; returns the path to delete in your branch.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "moxie-docs-mcp": {
    "command": "npx",
    "args": ["-y","moxie-docs"]
  }
}
```

## Documentation

## What Moxie-Docs-MCP MCP server does

Moxie-Docs-MCP MCP server connects coding agents to the documentation and repository context indexed by Moxie Docs for a connected GitHub repository. It exposes generated documentation, discovered coding conventions, documentation gaps, API information, and repository status through MCP tools. The service is intended for agents that need evidence-backed guidance about how a particular codebase is organized and maintained.

The repository contains the setup CLI, MCP interface definitions, prompts, metadata, and skill renderers. The hosted service keeps the indexing pipeline and generated repository documentation; they are not stored in this GitHub repository.

## How it works

The hosted MCP endpoint uses Streamable HTTP at `https://moxiedocs.com/api/mcp`. Tools can receive an optional repository identifier such as `owner/name`. A repository argument is needed when the authenticated token covers multiple repositories and no single default is available.

Read operations return compact context with citations rather than raw code dumps. `moxie.get_ai_context` provides a pre-edit briefing containing repository status, verified commands, conventions, open gaps, and team notes. Other read tools locate relevant documentation, conventions, API endpoints, documentation patterns, and unresolved gaps. `moxie.review_change` evaluates a proposed change for convention violations, stale or missing documentation, undocumented surfaces, and broken references.

Write-related operations are proposals only. `moxie.propose_doc_update` returns a target path and Markdown content for the agent to write into its own branch, while `moxie.propose_doc_removal` identifies a tracked document to delete. The service does not edit the repository or merge changes through MCP.

## Setup and configuration

From a repository directory, run `npx moxie-docs setup`. The CLI signs the user in, configures the MCP client, installs the `moxie-docs` skill and `AGENTS.md` guidance, and checks the connection. It requires Node 18 or later and can also be installed globally with `npm i -g moxie-docs`.

The CLI supports Claude Code, Cursor, and VS Code configuration. It can use browser authentication with OAuth 2.1 and PKCE, or a dashboard token supplied with `--token`. The default configuration writes a URL-only server entry so the client performs OAuth when supported. Browser login credentials used by the CLI are stored under `~/.moxie-docs/`; static tokens should remain out of source control.

## Tools and capabilities

The Moxie-Docs-MCP MCP server provides tools for:

- Retrieving pre-edit repository context and discovered conventions with confidence scores and source citations.
- Finding documentation affected by changed or deleted paths, including API mappings and known consumers.
- Searching generated docs, conventions, gaps, and AI context with semantic and keyword queries.
- Listing generated documentation and identifying documentation opportunities, patterns, and unresolved gaps.
- Reviewing changes and proposing Markdown updates or removals for the current branch.

This makes the server relevant to the 💻 Developer Tools category, especially workflows where documentation maintenance is part of code review rather than a separate manual task.

_Full upstream README: https://allmcps.com/mcp/moxie-docs-mcp/readme_