DevDocs by CyberAGI for Claude Code: Setup & Config

What you can do with DevDocs by CyberAGI in Claude Code

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

• Collect linked technical documentation with controlled crawl depth.
• Retrieve specific documentation sections after topic discovery.

Before you start: DevDocs by CyberAGI in Claude Code

• 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 Code configuration

1. Choose Claude Code configuration scope

   For DevDocs by CyberAGI, open Project scope: .mcp.json at the repository root. Project JSON: merge into mcpServers; user scope: use the CLI.

2. Add DevDocs by CyberAGI to Claude Code

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

3. Check DevDocs by CyberAGI in Claude Code

   DevDocs by CyberAGI: Inspect claude mcp list and /mcp status.

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

claude mcp add-json --scope project 'DevDocs' '{"type":"stdio","command":"./docker-start.sh","args":[],"env":{"NEXT_PUBLIC_BACKEND_URL":"<backend address reachable by the frontend browser>"}}'

DevDocs by CyberAGI tools available to Claude Code

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

Table Of Contents Tool

For DevDocs by CyberAGI's Table Of Contents Tool, review the permission request and arguments in Claude Code before approval.

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

Section Access Tool

For DevDocs by CyberAGI's Section Access Tool, review the permission request and arguments in Claude Code before approval.

DevDocs by CyberAGI: full stored tool descriptions

Troubleshooting DevDocs by CyberAGI in Claude Code

• If DevDocs by CyberAGI fails to start, check docker-start.sh, the working directory, and Claude Code's selected scope; inspect claude mcp list and /mcp.
• DevDocs by CyberAGI: check NEXT_PUBLIC_BACKEND_URL; keep credentials out of shared .mcp.json.
• DevDocs by CyberAGI uses stdio here: Claude Code 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 Code troubleshooting lives in the /clients/claude-code guide.

Frequently asked questions