Skip to content
All guides

Windsurf + AgentDoc

Windsurf MCP entry. Publish docs from Cascade; sync .windsurfrules across projects.

2 min readGuide

Install (pick one line)

Technical — paste in your terminal:

npx -y @agentdoc/cli install windsurf

Writes the agentdoc entry into ~/.codeium/windsurf/mcp_config.json.

Not technical — paste in Cascade:

Set up AgentDoc for me: https://agentdoc.com/install/windsurf.md

Cascade fetches the install markdown, edits the MCP config, and tells you what it did. Restart Windsurf after install either way.

Manual install

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

Paste into ~/.codeium/windsurf/mcp_config.json. First run provisions an anonymous API key at ~/.agentdoc/mcp-key.json.

What Cascade can do once connected

"Publish this architecture doc as arch/event-pipeline." "Fetch the latest runbook and open it alongside the code." "Create an AgentDoc for the migration plan and invite the backend team."

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

Sync .windsurfrules across repos

agentdoc init
agentdoc track .windsurfrules --slug windsurf-rules-acme
agentdoc push

# Any other repo
agentdoc init
agentdoc track .windsurfrules --slug windsurf-rules-acme
agentdoc pull
  • agentdoc status → synced / behind / modified.
  • agentdoc pull → latest version lands in place.
  • agentdoc watch .windsurfrules windsurf-rules-acme → auto-push on save.

One doc, many tools

The same AgentDoc can feed every AI tool's rules file:

agentdoc track .windsurfrules --slug team-ai-rules
agentdoc track .cursorrules --slug team-ai-rules
agentdoc track CLAUDE.md --slug team-ai-rules
agentdoc pull

Write your conventions once. Every tool reads the same markdown.

Every other agent

See agentdoc.com/connect.