ATLAS Task Management System for Windsurf: Setup & Config

What you can do with ATLAS Task Management System in Windsurf

Graph-backed project planning that keeps agent tasks, dependencies, and supporting knowledge connected.

• Plan agent work as projects with completion requirements.
• Track prioritized tasks and prerequisite relationships.
• Create or update projects in bulk.

Before you start: ATLAS Task Management System in Windsurf

• Node.js and npm
• Cloned atlas-mcp-server repository with npm install completed
• Build generated with npm run build
• Reachable Neo4j instance, self-hosted or AuraDB

Replace the absolute entrypoint path after building. The README also provides npm run start:stdio and npm run start:http. HTTP defaults to 127.0.0.1:3010 with a documented /mcp endpoint. Production use is explicitly untested. Only project tool names are visible in the supplied excerpt.

ATLAS Task Management System Windsurf configuration

1. Choose Windsurf configuration scope

   For ATLAS Task Management System, open macOS/Linux: ~/.codeium/windsurf/mcp_config.json Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json. Merge into mcpServers; remote endpoints use serverUrl.

2. Add ATLAS Task Management System to Windsurf

   Use the atlas-mcp-server-cyanheads entry below in mcpServers. Keep ATLAS Task Management System's documented stdio connection fields and your other Windsurf entries.

3. Check ATLAS Task Management System in Windsurf

   ATLAS Task Management System: Refresh MCP in Windsurf settings and inspect Cascade’s tools.

{
  "mcpServers": {
    "atlas-mcp-server-cyanheads": {
      "command": "node",
      "args": [
        "/full/path/to/atlas-mcp-server/dist/index.js"
      ],
      "env": {
        "NEO4J_URI": "<Neo4j connection URI>",
        "NEO4J_USER": "<Neo4j username>",
        "NEO4J_PASSWORD": "<Neo4j password>",
        "MCP_LOG_LEVEL": "<Optional logging level>",
        "MCP_TRANSPORT_TYPE": "<stdio for this local client configuration>"
      }
    }
  }
}

ATLAS Task Management System tools available to Windsurf

ATLAS Task Management System's stored tool list documents 4 tools; compare it with Windsurf's connected tool list, because the stored list is not a live check.

atlas_project_create

After refreshing ATLAS Task Management System in Windsurf settings, check Cascade's tool list for atlas_project_create.

atlas_project_list

After refreshing ATLAS Task Management System in Windsurf settings, check Cascade's tool list for atlas_project_list.

List projects or retrieve details with filters and pagination.

atlas_project_update

After refreshing ATLAS Task Management System in Windsurf settings, check Cascade's tool list for atlas_project_update.

atlas_project_delete

After refreshing ATLAS Task Management System in Windsurf settings, check Cascade's tool list for atlas_project_delete.

Delete a project or a batch of projects.

ATLAS Task Management System: full stored tool descriptions

Troubleshooting ATLAS Task Management System in Windsurf

• Check node (Node.js) on the machine running Windsurf's MCP integration for ATLAS Task Management System; refresh MCP and inspect Cascade's tools.
• Check MCP_LOG_LEVEL, MCP_TRANSPORT_TYPE, NEO4J_PASSWORD, NEO4J_URI, NEO4J_USER for ATLAS Task Management System; do not bypass a Windsurf permission error with a broad administrator token.
• ATLAS Task Management System uses stdio here: Windsurf must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: Current versions require a Neo4j deployment.
• Known limitation: The basic web interface is experimental.
• Known limitation: The README says production environment use has not been tested.
• General Windsurf troubleshooting lives in the /clients/windsurf guide.

Frequently asked questions