Cursor + agentdocs

Install the MCP server

Add to .cursor/mcp.json (per-project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "agentdoc": {
      "command": "npx",
      "args": ["-y", "@agentdoc/mcp"]
    }
  }
}

Restart Cursor. First run provisions an anonymous API key at ~/.agentdoc/mcp-key.json. No email, no OAuth.

What Cursor can do once connected

"Publish the current spec as design/auth-spec." "Pull the latest team rules AgentDoc for this repo into .cursor/rules/." "Create an AgentDoc changelog entry for the PR I just shipped."

Cursor creates, updates, publishes, forks, and searches via MCP.

Sync .cursorrules across repos

Cursor loads AI instructions from .cursorrules or .cursor/rules/*.mdc. Those files drift across repos. Store them on AgentDoc and pull:

# First repo — push it once
agentdoc init
agentdoc track .cursorrules --slug cursor-rules-acme
agentdoc push

# Any other repo
agentdoc init
agentdoc track .cursorrules --slug cursor-rules-acme
agentdoc pull

• Modular .mdc rules work the same: track each file, pull them all.
• agentdoc status → shows synced / behind / modified.
• agentdoc history cursor-rules-acme → see who changed what.
• agentdoc watch .cursorrules cursor-rules-acme → auto-push every local save.

Share rules across your whole team

Write conventions once, map to every repo:

.cursor/rules/typescript.mdc → cursor-typescript-standards
.cursor/rules/testing.mdc    → cursor-testing-standards
.cursor/rules/security.mdc   → cursor-security

Team lead edits at agentdoc.com/@yourteam/cursor-typescript-standards. Every repo picks up the change via agentdoc pull.

Quick start

echo '{"mcpServers":{"agentdoc":{"command":"npx","args":["-y","@agentdoc/mcp"]}}}' > .cursor/mcp.json
# Restart Cursor. Ask: "Publish the current spec as design/auth-spec."