DevDocs by CyberAGI for VS Code: Setup & Config

What you can do with DevDocs by CyberAGI in VS Code

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

• Collect linked technical documentation with controlled crawl depth.
• Give an assistant indexed access to internal documentation.

Before you start: DevDocs by CyberAGI in VS 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 VS Code configuration

1. Choose VS Code configuration scope

   For DevDocs by CyberAGI, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

2. Add DevDocs by CyberAGI to VS Code

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

3. Check DevDocs by CyberAGI in VS Code

   DevDocs by CyberAGI: Start in VS Code’s MCP controls; inspect output and trust prompts.

{
  "servers": {
    "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 VS Code

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

Table Of Contents Tool

Look for Table Of Contents Tool among VS Code's agent-mode tools after starting DevDocs by CyberAGI through the MCP controls.

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

Section Access Tool

Look for Section Access Tool among VS Code's agent-mode tools after starting DevDocs by CyberAGI through the MCP controls.

DevDocs by CyberAGI: full stored tool descriptions

Troubleshooting DevDocs by CyberAGI in VS Code

• Make docker-start.sh available in the workspace, container, or remote environment hosting DevDocs by CyberAGI. Start through VS Code's MCP controls; inspect output and trust prompts.
• For DevDocs by CyberAGI, keep NEXT_PUBLIC_BACKEND_URL out of version control; VS Code documents input variables and secret handling.
• DevDocs by CyberAGI uses stdio here: VS 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 VS Code troubleshooting lives in the /clients/vscode guide.

Frequently asked questions