1. Home
  2. DevDocs by CyberAGI
  3. DevDocs by CyberAGI for Cursor: Setup & Config

Data as of

DevDocs by CyberAGI for Cursor: Setup & Config

Cursor: Crawl technical documentation into organized Markdown, JSON, and MCP-accessible content for development assistants.

What you can do with DevDocs by CyberAGI in Cursor

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

  • Give an assistant indexed access to internal documentation.
  • Retrieve specific documentation sections after topic discovery.

Before you start: DevDocs by CyberAGI in Cursor

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

  1. Choose Cursor configuration scope

    For DevDocs by CyberAGI, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add DevDocs by CyberAGI to Cursor

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

  3. Check DevDocs by CyberAGI in Cursor

    DevDocs by CyberAGI: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

JSON
{
  "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 Cursor

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

Table Of Contents Tool

Find Table Of Contents Tool under DevDocs by CyberAGI in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Section Access Tool

Find Section Access Tool under DevDocs by CyberAGI in Cursor's MCP settings; inspect its arguments when the agent requests a call.

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 Cursor

  • Cursor must find docker-start.sh for DevDocs by CyberAGI. Enable the project/user entry in MCP settings and inspect its tools.
  • Review NEXT_PUBLIC_BACKEND_URL for DevDocs by CyberAGI before sharing project .cursor/mcp.json; project scope travels with the repository.
  • DevDocs by CyberAGI uses stdio here: Cursor 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 Cursor troubleshooting lives in the /clients/cursor guide.

DevDocs by CyberAGI — details. Cursor guide

Frequently asked questions

Cursor's DevDocs by CyberAGI entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's DevDocs example uses stdio.

DevDocs by CyberAGI's Cursor configuration invokes docker-start.sh.

Cursor's DevDocs by CyberAGI example references NEXT_PUBLIC_BACKEND_URL. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

DevDocs by CyberAGI's stored list contains 2 tools, including Table Of Contents Tool, Section Access Tool. Compare those names with Cursor's connected tool list; the stored list is not a live check.

The README lists Markdown and JSON, as well as MCP integration for AI retrieval.

No. The Windows Docker instructions are labeled experimental and untested.