Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.
Connect Moxie Docs to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge. The moxie docs mcp server is what makes that connection.
The Moxie Docs Model Context Protocol (MCP) server, the agent skills Moxie installs into your repository, and the moxie-docs CLI that wires it all up — npx moxie-docs setup.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
moxie.get_ai_context — Compact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this firstmoxie.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 - andmoxie.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/featuresmoxie.review_change — Self-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docsmoxie.get_conventions — Discovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citationsmoxie.search_docs — Semantic + keyword search over generated docs, conventions, gaps, and AI contextmoxie.get_doc_gaps — Unresolved documentation gaps with severity and the paths they concernmoxie.get_documentation_opportunities — Recommended doc work: missing docs, drift repairs, and PR templatesmoxie.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 docmoxie.propose_doc_update — Add or update a doc as part of your current change; returns the target path + Markdown to write into your branchmoxie.propose_doc_removal — Remove a Moxie-tracked doc your change makes obsolete; returns the path to delete in your branchBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: MOXIE_TOKEN, MOXIE_SITE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Moxie Docs's toolset — moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Jackalope-Dev; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| 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-tracked doc your change makes obsolete; returns the path to delete in your branch. |
| Connection | All write tools are **proposals** — Moxie returns the file path and content for *you* (the agent) to write into your own branch. Moxie never edits your repository directly through MCP, and never merges. Reads return comp |
| Authentication | Moxie stores only the token hash (plus an encrypted copy so you can reveal it), a prefix, scope, and a last-used timestamp. You can reveal, rotate, or revoke tokens from the dashboard at any time. |
**Cursor** — `.cursor/mcp.json`:
```json
{
"mcpServers": {
"moxie-docs": {
"url": "https://moxiedocs.com/api/mcp",
"headers": { "Authorization": "Bearer <MOXIE_TOKEN>" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MOXIE_TOKEN | Credential the server authenticates with. | Yes |
| MOXIE_SITE_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.