Skip to main content
MCP server CX Codex

moxie-docs — Claude Code MCP server: conventions, docs, install

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.

no license 729 installs updated 2026-06-25

Install into Claude Code · Platform CLI: remote server All methods and platforms ↓
claude mcp add --transport http moxie-docs https://moxie-docs.run.tools
Open on GitHub

What moxie-docs 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.

What it helps with

  • 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 for the agent

  • 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.

How to install moxie-docs

Platform CLI: remote server

claude mcp add --transport http moxie-docs https://moxie-docs.run.tools

Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more

Questions about moxie-docs

How do I install moxie-docs in Claude Code?

Run claude mcp add --transport http moxie-docs https://moxie-docs.run.tools. The server is remote over http, so nothing runs locally.

What does moxie-docs do?

It gives the agent context about your repository: coding conventions, a documentation map, gaps and stale pages. Two more tools let it propose a doc update or removal as part of the current change.

Does the repository need to be indexed first?

Yes. The tools return data only for repositories indexed with Moxie Docs.

Similar MCP servers

All MCP servers for Agent setup: memory, context, orchestration →

Project sponsors

Companies that keep this analytics open