Moxie Docs
Moxie Docs - Living Documentation for Coding Agents
Moxie Docs is a hosted Model Context Protocol (MCP) server that keeps your GitHub repository's documentation alive and gives coding agents the context they need to write code — and update docs — the way your team actually works.
Instead of dumping raw source files into the context window, Moxie indexes your connected repository, discovers real conventions, tracks documentation gaps and drift, and exposes compact, citation-backed context through MCP. Agents read that context before editing, follow your repo's verified commands and patterns, and propose documentation changes that ship in the same pull request as the code.
- Website: https://moxiedocs.com
- MCP docs: https://moxiedocs.com/mcp
- MCP endpoint:
https://moxiedocs.com/api/mcp - GitHub (CLI + interface): https://github.com/Jackalope-Dev/Moxie-Docs-MCP
- npm CLI:
npx moxie-docs setup
What it does
Moxie Docs solves a common problem: agents either ignore documentation entirely, or they invent generic filler that doesn't match how the repository actually works.
Moxie connects to your GitHub repo and continuously maintains a living documentation layer — generated docs, discovered conventions, gap tracking, and drift detection. That context is served to any MCP-capable client (Claude Code, Cursor, VS Code, Codex, and others) so agents can:
- Read before they edit — get a compact briefing on repo status, conventions, open gaps, and verified commands
- Check doc impact — see which docs and conventions overlap the files they're about to change
- Propose doc updates — receive the exact file path and Markdown to write into their branch, landing in the same PR as the code change
All write operations are proposals only. Moxie never edits your repository directly through MCP and never merges on your behalf. The agent applies changes locally in its own branch.
Quick start
From your repository directory:
npx moxie-docs setup
This signs you in via OAuth, writes the MCP config for your editor, installs the moxie-docs agent skill and AGENTS.md guidance block, and verifies the connection. After setup, your agent calls moxie.get_ai_context before editing and uses the propose tools to keep docs in sync.
You can also connect manually at https://moxiedocs.com and add the server to your MCP client config.
Connection details
| Transport | Streamable HTTP MCP |
| Endpoint | https://moxiedocs.com/api/mcp |
| Protocol version | 2025-06-18 |
| Repository selection | Optional repository argument (owner/name). Required only when a token serves multiple repos with no default. |
Authentication
Two paths, same token model:
OAuth 2.1 (recommended) — MCP clients that support OAuth can sign in through the browser. No token pasting required. Discovery endpoints:
https://moxiedocs.com/.well-known/oauth-protected-resourcehttps://moxiedocs.com/.well-known/oauth-authorization-server
Bearer token — Create a long-lived token in the Moxie dashboard and send:
Authorization: Bearer <MOXIE_TOKEN>
Tokens can be revealed, rotated, and revoked from the dashboard at any time.
MCP tools
| Tool | Purpose |
|---|---|
moxie.get_ai_context | Pre-edit briefing: repo status, verified commands, top conventions, open gaps. Read this first. |
moxie.get_doc_impact | Given paths you're changing, returns overlapping conventions, gaps, and docs — plus net-new surfaces. |
moxie.get_conventions | Discovered coding conventions with confidence scores, agent guidance, and source citations. |
moxie.search_docs | Semantic + keyword search over docs, conventions, gaps, and AI context. |
moxie.get_doc_gaps | Unresolved documentation gaps with severity and affected paths. |
moxie.get_documentation_opportunities | Recommended doc work: missing docs, drift repairs, PR templates. |
moxie.get_documentation_patterns | How the repo organizes docs and where new docs belong. |
moxie.list_docs | Paginated table of contents of every generated doc. |
moxie.propose_doc_update | Returns target path + Markdown for the agent to write into its branch. |
moxie.propose_doc_removal | Returns the path to delete when a change makes a doc obsolete. |
MCP prompts
| Prompt | Purpose |
|---|---|
document-this-change | Runs doc-impact on changed paths and walks through proposing updates for the same PR. |
fix-stale-docs | Finds open gaps and drift, then repairs them through Moxie. |
Agent skills
Moxie ships a moxie-docs agent skill that teaches agents when and how to use the MCP server. On repo connect, Moxie opens a single PR adding:
AGENTS.md— always-on pointer block for any agent.claude/skills/moxie-docs/SKILL.md— skill for Claude Code.agents/skills/moxie-docs/SKILL.md— skill for.agents-aware clients
The skill is also published at:
https://moxiedocs.com/.well-known/agent-skills/moxie-docs/SKILL.md
Who it's for
- Teams that want agents to follow real repo conventions, not generic advice
- Repos where docs drift behind code and nobody has time to chase it
- Developers using Cursor, Claude Code, VS Code, or any MCP client who want documentation updates bundled into every code change
- Anyone building agent workflows that need source-cited, compact context instead of full codebase dumps
Also available
- Official MCP Registry:
io.github.Jackalope-Dev/moxie-docs - Smithery: https://smithery.ai/servers/caden/moxie-docs
- Open-source npm package:
moxie-docs— CLI, tool catalog, prompts, and skill renderers (the hosted server and indexing pipeline are not in the repo)
MIT licensed. Built by Jackalope Dev.
Server Config
{
"mcpServers": {
"moxie-docs": {
"url": "https://moxiedocs.com/api/mcp"
}
}
}Recommend Servers
View AllA Serper MCP Server
summarize chat message
Write notes to Flomo