Cursor + Moxie Docs

MCP server for Cursor - context from your real codebase

Cursor agents work better when they read your conventions before editing. Moxie Docs indexes your GitHub repository and serves citation-backed context through MCP so Cursor stops re-exploring the repo on every prompt.

  • One-command setup. npx moxie-docs setup writes Cursor's MCP config and smoke-tests the connection.
  • Fresh on every merge. The index updates when code changes - agents read current architecture, not stale notes.
  • Read-only context. MCP tools expose docs and conventions only. Billing, settings, and merges stay in your control.
Set up with one promptConnect GitHub repoMCP overview

Set up Cursor with Moxie

  1. Step 1

    Connect GitHub

    Start a trial and connect the repository you want Cursor to understand.

  2. Step 2

    Run setup

    Run npx moxie-docs setup - it signs you in, writes Cursor's MCP entry, and installs the moxie-docs skill.

  3. Step 3

    Let agents read first

    Ask Cursor to pull conventions and doc gaps via MCP before making edits.

$ npx moxie-docs setup

Sign in, configure your editor, and install the skill - one command.

FAQ

Does Moxie work with Cursor out of the box?+

Yes. Moxie exposes a standard MCP endpoint. Run npx moxie-docs setup after connecting a repository, or copy the MCP config from your dashboard once the first index finishes.

What context do agents receive?+

Conventions, generated docs, open doc gaps, verified commands, and doc-impact hints for the files an agent plans to change - all scoped to the repository you selected.

Can I use a repository token instead of OAuth?+

Yes. Pass --token to moxie-docs setup if you prefer a static repo token over OAuth sign-in in Cursor.