Moxie Docs MCP

What Moxie-Docs-MCP MCP server does

Moxie-Docs-MCP MCP server exposes repository-aware documentation and codebase context to MCP clients. It works with a GitHub repository connected through Moxie Docs and organizes generated documentation, discovered conventions, unresolved gaps, API relationships, and documentation maintenance recommendations.

The tools are designed for coding workflows rather than general-purpose code search. An agent can request a short pre-edit briefing, identify documentation affected by planned file changes, inspect API endpoints associated with paths, and search the indexed repository context. It can also run a change review that reports convention violations, stale documentation, undocumented surfaces, and broken references with severity levels.

Write-oriented operations return proposals. The agent receives a target path and Markdown content, or a path to remove, and applies the change in its own branch. The MCP service does not directly edit the repository or merge pull requests.

How it works

The hosted MCP endpoint is https://moxiedocs.com/api/mcp and uses Streamable HTTP. Moxie Docs indexes a connected GitHub repository, then serves compact results backed by source-file citations. Repository selection can be supplied as an owner/name argument when a credential covers multiple repositories and no default repository is available.

A typical coding sequence starts with moxie.get_ai_context, followed by tools such as moxie.get_doc_impact, moxie.get_api_context, or moxie.get_conventions for the files under consideration. After editing, moxie.review_change can identify issues before a pull request is opened. Search, gap, opportunity, pattern, and document-listing tools provide additional ways to navigate the indexed material.

Moxie-Docs-MCP MCP server supports bearer authentication with a dashboard token. MCP clients that implement the relevant OAuth flow can instead sign in through the browser using OAuth 2.1 with PKCE.

Setup and configuration

Connect a repository at Moxie Docs, then configure an MCP client with the hosted endpoint. A bearer-token configuration sends an Authorization: Bearer ... header. Tokens should remain in local, untracked configuration or be supplied through a client-supported environment-variable reference.

The repository also publishes the moxie-docs npm package, whose CLI can configure clients and install repository guidance. Running npx moxie-docs setup performs browser sign-in, writes client configuration, installs the moxie-docs skill and AGENTS.md guidance, and checks the connection. The CLI requires Node.js 18 or newer. Supported CLI configuration targets listed in the material include Claude Code, Cursor, and VS Code.

Tools and capabilities

• Retrieve repository status, verified commands, conventions, gaps, and team notes.
• Find documentation affected by paths being changed or deleted.
• Resolve API methods, paths, schemas, and known consumers for relevant files.
• Search generated docs, conventions, gaps, and AI context using semantic and keyword search.
• List documentation and inspect repository documentation patterns.
• Return recommended documentation work, including missing documentation and drift repairs.
• Propose Markdown additions, updates, or removals for the agent to apply.
• Review changes for convention breaches, stale docs, undocumented surfaces, and broken references.

Limitations and notes

Moxie-Docs-MCP MCP server is not a local repository index or a direct file-editing service. The hosted server, indexing pipeline, connected repositories, and generated documentation are not stored in this source repository. Results depend on the repository connected to the Moxie Docs service and the scope of the authenticated account.

The server provides context and proposed file changes, but the client or agent must write those changes to its branch. It does not merge changes. The material identifies a hosted service and authentication requirements, but does not specify subscription pricing or a license for the repository.