Log inSubmit server
Moxie Docs MCP logo

Moxie Docs MCP

Premium

Ground coding agents in repository conventions, API context, documentation gaps, and proposed doc changes.

  • Ownership verifiedThe owner proved control of this listing via a GitHub README, site badge, or DNS TXT record.
  • Featured listingIncluded with this listing’s active Premium subscription — boosted placement across search, category pages, and homepage spotlight rotation.
  • InstallableWe know how to install it, but have not yet seen it complete a handshake.
  • Health: ActiveRecent health check succeeded.Last checked 10/27/2026, 3:00:31 PM
  • Knowledge & Memory
  • 2stars
  • 5.0(1) User RatingsRated 5.0 / 5.0 across 1 user review. Click to view or leave a rating.
  • 25installs
  • UpdatedOct 20, 2026
InstallRepositoryWebsite
Full README Compare alternatives Embed widget

Install Moxie Docs MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "moxie-docs-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "moxie-docs"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y moxie-docs

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 3d ago.

Overview

Moxie-Docs-MCP MCP server exposes live documentation and codebase context from a connected GitHub repository to MCP-capable coding agents. Its tools retrieve conventions, API details, documentation gaps, existing docs, and pre-edit guidance, while review and proposal tools help keep documentation aligned with code changes. Connect through the hosted Streamable HTTP endpoint using OAuth or a dashboard token. Reach for it when an agent needs repository-specific guidance before editing or reviewing a change.

Use cases

  • Review repository conventions before editing code
  • Find documentation affected by changed paths
  • Inspect API context for endpoints mapped to files
  • Identify unresolved documentation gaps
  • Propose documentation updates within a code change

Key features

  • Pre-edit repository briefings
  • Convention discovery with citations
  • Documentation impact analysis
  • API endpoint context lookup
  • Change review with severity-ranked findings
  • Documentation update and removal proposals

Tools12

What Moxie Docs MCP lets your agent do. Expand a tool for its parameters.

Self-reported~402 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

96/96 checks healthy over the last 13d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · moxie-docs (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
npm downloads135Package downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed12Callable tools this server registers over MCP.
Directory activity25 installs · 4 upvotesConfig copies, upvotes, and views on AllMCPs.

How Moxie Docs MCP works

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.

Read the full README View source on GitHub

Reviews1

5.01 rating
51
40
30
20
10

Frequently Asked Questions about Moxie Docs MCP

Moxie-Docs-MCP is an MCP server that connects coding agents to Moxie Docs data for a connected GitHub repository. Its main tools provide AI context, conventions, documentation impact, API context, searches, gap reports, change reviews, documentation listings, and proposed document updates or removals.

Run `npx moxie-docs setup` from your repository directory. The CLI signs you in, configures the MCP client, installs the repository skill and `AGENTS.md` guidance, and verifies the connection. Node 18 or later is required.

Yes, Moxie-Docs-MCP supports Cursor configuration. The CLI can write the server entry to `.cursor/mcp.json`, using the hosted endpoint and either OAuth-based sign-in or a dashboard token.

Moxie-Docs-MCP authenticates with OAuth 2.1 and PKCE for clients that support the flow, or with a dashboard bearer token. The hosted endpoint is `https://moxiedocs.com/api/mcp`; tokens are sent in an `Authorization` header and should not be committed to source control.

No, Moxie-Docs-MCP does not edit repositories or merge changes through MCP. Its write tools return a file path and Markdown content, or a path to remove, for the agent to apply in its own branch.

Related MCP servers

All in Knowledge & Memory All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMoxie Docs MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/moxie-docs-mcp?style=directory)](https://allmcps.com/mcp/moxie-docs-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/moxie-docs-mcp"><img src="https://allmcps.com/api/badge/moxie-docs-mcp?style=directory" alt="Moxie Docs MCP on AllMCPs" /></a>