# moxie-docs

moxie-docs — a remote MCP server that hands your agent the repo's coding conventions and a map of its documentation, so edits start with context.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · 729 installs
- Author: jackalope-digital
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://smithery.ai/server/jackalope-digital/moxie-docs
- Updated: 2026-06-25
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/mcp/moxie-docs

## What it does

moxie-docs is a remote MCP server at `https://moxie-docs.run.tools`. It supplies what a fresh context window usually lacks: conventions inferred from the code, a map of the docs, the gaps, and the pages that drifted. It only works for a repository already indexed with Moxie Docs; pointed at anything else, the tools have nothing to return.

Start with `moxie.get_ai_context`. One Markdown briefing covers index status, verified commands, top conventions, open gaps and queued doc work. From there: `moxie.search_docs` for keyword and semantic lookup across docs and indexed code, `moxie.list_docs` for the full table of contents, plus `moxie.get_conventions`, `moxie.get_doc_gaps` and `moxie.get_documentation_opportunities` for a prioritized queue.

Before touching files, `moxie.get_doc_impact` takes the paths you plan to change and returns the conventions and docs whose evidence overlaps them. The two proposal tools record suggestions only. `moxie.propose_doc_update` hands back a path and Markdown for you to write into your branch, and every call creates a new record rather than replacing the last one. Neither tool edits the repository or opens a PR.

## Requirements
- Remote server: `https://moxie-docs.run.tools`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http moxie-docs https://moxie-docs.run.tools
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add moxie-docs --url https://moxie-docs.run.tools
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "moxie-docs": {
            "url": "https://moxie-docs.run.tools"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "moxie-docs": {
            "type": "http",
            "url": "https://moxie-docs.run.tools"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http moxie-docs https://moxie-docs.run.tools
```

## When to use it
- pull the repo's coding conventions before a first edit
- find which docs a file change touches
- pick the stale pages worth rewriting
- spot documentation nothing points at anymore
- get a short repo briefing at the start of a session

## Example prompts
- Read `moxie.get_ai_context` and summarize the repo conventions before you change anything.
- I'm about to edit `src/auth/session.ts`; run `moxie.get_doc_impact` on that path and list the docs it affects.
- Take the top item from `moxie.get_documentation_opportunities` and draft it with `moxie.propose_doc_update`.

## Similar
- [Ontology Atlas](https://affpapa.org/en/nevibecode/mcp/ontology-atlas.md) — MCP server · ★ 170 repo stars
- [tailwind-4-docs](https://affpapa.org/en/nevibecode/skills/tailwind-4-docs.md) — skill · 19300 installs
- [developer-troubleshooting-docs](https://affpapa.org/en/nevibecode/skills/developer-troubleshooting-docs.md) — skill · 13400 installs
- [coding-agent-docs-optimization](https://affpapa.org/en/nevibecode/skills/coding-agent-docs-optimization.md) — skill · 13400 installs
- [openai-docs](https://affpapa.org/en/nevibecode/skills/openai-docs.md) — skill · 7300 installs

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
