DevDocs by CyberAGI for Windsurf: Setup & Config

What you can do with DevDocs by CyberAGI in Windsurf

Consider DevDocs for documentation crawling and MCP retrieval, while accounting for its maintenance notice.

• Export cleaned documentation as Markdown or JSON.
• Retrieve specific documentation sections after topic discovery.

Before you start: DevDocs by CyberAGI in Windsurf

• Docker
• Git
• A cloned DevDocs checkout
• macOS or Linux for the recommended startup path

Run from the cloned repository after copying .env.template to .env. This script starts the complete application stack, not a standalone MCP client entry. Windows uses a separate experimental batch script.

DevDocs by CyberAGI Windsurf configuration

1. Choose Windsurf configuration scope

   For DevDocs by CyberAGI, open macOS/Linux: ~/.codeium/windsurf/mcp_config.json Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json. Merge into mcpServers; remote endpoints use serverUrl.

2. Add DevDocs by CyberAGI to Windsurf

   Use the DevDocs entry below in mcpServers. Keep DevDocs by CyberAGI's documented stdio connection fields and your other Windsurf entries.

3. Check DevDocs by CyberAGI in Windsurf

   DevDocs by CyberAGI: Refresh MCP in Windsurf settings and inspect Cascade’s tools.

{
  "mcpServers": {
    "DevDocs": {
      "command": "./docker-start.sh",
      "args": [],
      "env": {
        "NEXT_PUBLIC_BACKEND_URL": "<backend address reachable by the frontend browser>"
      }
    }
  }
}

DevDocs by CyberAGI tools available to Windsurf

DevDocs by CyberAGI's stored tool list documents 2 tools; compare it with Windsurf's connected tool list, because the stored list is not a live check.

Table Of Contents Tool

After refreshing DevDocs by CyberAGI in Windsurf settings, check Cascade's tool list for Table Of Contents Tool.

Section Access Tool

After refreshing DevDocs by CyberAGI in Windsurf settings, check Cascade's tool list for Section Access Tool.

Retrieve detailed documentation sections after index discovery; the README supplies this descriptive label.

DevDocs by CyberAGI: full stored tool descriptions

Troubleshooting DevDocs by CyberAGI in Windsurf

• Check docker-start.sh on the machine running Windsurf's MCP integration for DevDocs by CyberAGI; refresh MCP and inspect Cascade's tools.
• Check NEXT_PUBLIC_BACKEND_URL for DevDocs by CyberAGI; do not bypass a Windsurf permission error with a broad administrator token.
• DevDocs by CyberAGI uses stdio here: Windsurf must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: The public repository is explicitly marked as not maintained.
• Known limitation: Windows setup is described as experimental and untested.
• Known limitation: Running the documented stack involves several services.
• General Windsurf troubleshooting lives in the /clients/windsurf guide.

Frequently asked questions