Moxie-Docs-MCP

<p align="center">
  <img src="https://moxiedocs.com/moxie-fox.svg" alt="Moxie Docs" width="120" />
  <br />
  <a href="https://moxiedocs.com">Visit Moxie Docs</a>
</p>

# Moxie Docs — MCP & Agent Tools

[![npm version](https://img.shields.io/npm/v/moxie-docs.svg)](https://www.npmjs.com/package/moxie-docs)
[![Smithery](https://img.shields.io/badge/Smithery-moxie--docs-purple)](https://smithery.ai/servers/jackalope-digital/moxie-docs)
[![AllMCPs](https://allmcps.com/api/badge/moxie-docs-mcp?metric=views)](https://allmcps.com/mcp/moxie-docs-mcp)
[![LobeHub Marketplace](https://img.shields.io/badge/LobeHub-Marketplace-1677ff)](https://lobehub.com/mcp/jackalope-dev-moxie-docs-mcp)
[![Moxie-Docs-MCP MCP server](https://glama.ai/mcp/servers/Jackalope-Dev/Moxie-Docs-MCP/badges/score.svg)](https://glama.ai/mcp/servers/Jackalope-Dev/Moxie-Docs-MCP)

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

This repo is also the open-source home of the **`moxie-docs` npm package**: a setup CLI plus the MCP *interface* (tool catalog, prompts, server metadata, and skill renderers) you can import. The hosted server, indexing pipeline, and your generated docs stay in the private Moxie service.

Moxie Docs indexes a connected GitHub repository and keeps its documentation alive — generating docs, discovering conventions, tracking documentation gaps and drift, and opening pull requests that keep docs in sync with code. The MCP server exposes that living context to coding agents (Claude Code, Cursor, VS Code, Codex, and any MCP-capable client) so they ground their work in how *your* repository actually does things — and keep the docs current as they change code.

- **Website / dashboard:** https://moxiedocs.com
- **Human docs for the MCP server:** https://moxiedocs.com/mcp
- **MCP endpoint:** `https://moxiedocs.com/api/mcp`

This repository is documentation and distribution assets only. The hosted server, indexing pipeline, and your repositories' documentation are not stored here.

---

## Contents

- [Quick start](#quick-start)
- [CLI](#cli)
- [The MCP server](#the-mcp-server)
  - [Connection](#connection)
  - [Authentication](#authentication)
  - [Client configuration](#client-configuration)
  - [Tools](#tools)
  - [Prompts](#prompts)
- [Claude plugin](#claude-plugin)
- [Skills](#skills)
  - [The `moxie-docs` skill](#the-moxie-docs-skill)
  - [What Moxie installs into your repository](#what-moxie-installs-into-your-repository)
- [Use as a library](#use-as-a-library)
- [Find the server](#find-the-server)
- [Discovery endpoints](#discovery-endpoints)
- [License](#license)

---

## Quick start

The fastest path — from your repository's directory:

```bash
npx moxie-docs setup
```

This signs you in (OAuth in your browser), writes the MCP config for your editor, installs the `moxie-docs` skill + `AGENTS.md` guidance, and verifies the connection. After that, your agent reads live context with `moxie.get_ai_context` before editing and proposes doc updates that land in the same PR.

Prefer to do it by hand? Connect a repository at https://moxiedocs.com, then add the server to your agent with a [config block](#client-configuration).

---

## CLI

The `moxie-docs` CLI (Node ≥ 18, zero runtime dependencies) sets up and manages the connection. Run it with `npx moxie-docs <command>` or install it globally (`npm i -g moxie-docs`).

| Command | What it does |
| --- | --- |
| `moxie-docs setup` | End-to-end: sign in, configure your MCP client, install the skill + `AGENTS.md` block, and smoke-test. |
| `moxie-docs login` | Sign in via the browser (OAuth 2.1 + PKCE) and store credentials in `~/.moxie-docs/`. |
| `moxie-docs status` | Show your scope, connected repositories, and available tool count. |
| `moxie-docs config <client>` | Write the `moxie-docs` server entry into a client config (`claude-code`, `cursor`, or `vscode`). |
| `moxie-docs install-skill` | Install the `moxie-docs` skill and `AGENTS.md` guidance into the current repo. |
| `moxie-docs logout` | Remove stored credentials. |

Useful flags: `--client <name>`, `--token <dashboard-token>`, `--repo owner/name`, `--no-browser`, `--yes`.

**How authentication is written.** By default `setup`/`config` write a **URL-only** server entry and let your editor perform its own OAuth sign-in on first use — so nothing in your committed config expires. The CLI's own browser sign-in (used for `status` and the setup smoke-test) stores a short-lived token plus a refresh token under `~/.moxie-docs/` (file mode `0600`); it is **never** written into a client config. If you'd rather pin a static `Authorization` header, pass a long-lived dashboard token with `--token` and the CLI writes that instead. The CLI never logs token values, and it refuses to overwrite a client config it can't safely parse rather than discarding your other MCP servers.

---

## The MCP server

### Connection

| | |
| --- | --- |
| **Transport** | Streamable HTTP MCP |
| **Endpoint** | `https://moxiedocs.com/api/mcp` |
| **Protocol version** | `2025-06-18` |
| **Repository selection** | Tools accept an optional `repository` argument (`owner/name`, e.g. `acme/app`). It is required only when a token serves multiple repositories and no single default applies. Matching is case-insensitive. |

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 compact, citation-backed context rather than raw code dumps.

### Authentication

**Bearer token (available today).** Create a token in the dashboard and send it as a header:

```
Authorization: Bearer <MOXIE_TOKEN>
```

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.

**OAuth 2.1 sign-in (for clients that support it).** MCP clients that implement the OAuth authorization flow can connect by signing in through the browser instead of pasting a token — the client discovers the server's OAuth metadata, registers itself dynamically (RFC 7591), and obtains a token via the authorization-code + PKCE flow. Discovery documents:

- Protected resource metadata: `https://moxiedocs.com/.well-known/oauth-protected-resource`
- Authorization server metadata: `https://moxiedocs.com/.well-known/oauth-authorization-server`

Both authentication paths resolve to the same token model, so either works with the same tools. Connected applications can be reviewed and revoked from the dashboard.

### Client configuration

Most agents accept a remote MCP server with a URL and headers. Replace `<MOXIE_TOKEN>` with a token from the dashboard.

**Claude Code** — `.mcp.json` (or `claude mcp add`):

```json
{
  "mcpServers": {
    "moxie-docs": {
      "url": "https://moxiedocs.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <MOXIE_TOKEN>"
      }
    }
  }
}
```

**Cursor** — `.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "moxie-docs": {
      "url": "https://moxiedocs.com/api/mcp",
      "headers": { "Authorization": "Bearer <MOXIE_TOKEN>" }
    }
  }
}
```

**VS Code** — `.vscode/mcp.json`:

```json
{
  "servers": {
    "moxie-docs": {
      "type": "http",
      "url": "https://moxiedocs.com/api/mcp",
      "headers": { "Authorization": "Bearer <MOXIE_TOKEN>" }
    }
  }
}
```

> Keep tokens out of source control. Reference an environment variable where your client supports it, or paste the token only into local, untracked config.

## Tools

- **`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.
- **`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.
- **`moxie.review_change`**: Self-review a change before opening the PR; returns a severity-ranked list of 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 target path + Markdown to write into branch.
- **`moxie.propose_doc_removal`**: Remove a Moxie-tracked doc your change makes obsolete; returns path to delete in branch.

| Tool | Purpose |
| --- | --- |
| `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 open