DevDocs by CyberAGI for Claude Desktop: Setup & Config

What you can do with DevDocs by CyberAGI in Claude Desktop

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

• Collect linked technical documentation with controlled crawl depth.
• Export cleaned documentation as Markdown or JSON.

Before you start: DevDocs by CyberAGI in Claude Desktop

• 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 Claude Desktop configuration

1. Choose Claude Desktop configuration scope

   For DevDocs by CyberAGI, open macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json. Merge under mcpServers via Settings → Developer → Edit Config when available.

2. Add DevDocs by CyberAGI to Claude Desktop

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

3. Check DevDocs by CyberAGI in Claude Desktop

   DevDocs by CyberAGI: Fully quit and reopen Claude Desktop; check developer diagnostics.

{
  "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 Claude Desktop

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

Table Of Contents Tool

When Claude Desktop requests Table Of Contents Tool from DevDocs by CyberAGI, review the action before approving it.

Find documentation topics through a full or filtered index; the README supplies this descriptive label.

Section Access Tool

When Claude Desktop requests Section Access Tool from DevDocs by CyberAGI, review the action before approving it.

DevDocs by CyberAGI: full stored tool descriptions

Troubleshooting DevDocs by CyberAGI in Claude Desktop

• Fully quit and reopen Claude Desktop for DevDocs by CyberAGI. If docker-start.sh is missing, check the desktop process's PATH, which may differ from your terminal.
• In Claude Desktop's DevDocs by CyberAGI entry, check NEXT_PUBLIC_BACKEND_URL. Keep secrets out of shared screenshots and repositories.
• DevDocs by CyberAGI uses stdio here: Claude Desktop 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 Claude Desktop troubleshooting lives in the /clients/claude-desktop guide.

Frequently asked questions