ATLAS Task Management System for Cursor: Setup & Config

What you can do with ATLAS Task Management System in Cursor

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

• Plan agent work as projects with completion requirements.
• Search across projects, tasks, and knowledge.
• Create or update projects in bulk.

Before you start: ATLAS Task Management System in Cursor

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

1. Choose Cursor configuration scope

   For ATLAS Task Management System, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

2. Add ATLAS Task Management System to Cursor

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

3. Check ATLAS Task Management System in Cursor

   ATLAS Task Management System: Enable in Cursor’s MCP settings; inspect 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 Cursor

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

atlas_project_create

Find atlas_project_create under ATLAS Task Management System in Cursor's MCP settings; inspect its arguments when the agent requests a call.

atlas_project_list

Find atlas_project_list under ATLAS Task Management System in Cursor's MCP settings; inspect its arguments when the agent requests a call.

atlas_project_update

Find atlas_project_update under ATLAS Task Management System in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Update one project or multiple projects in a batch.

atlas_project_delete

Find atlas_project_delete under ATLAS Task Management System in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Delete a project or a batch of projects.

ATLAS Task Management System: full stored tool descriptions

Troubleshooting ATLAS Task Management System in Cursor

• Cursor must find node (Node.js) for ATLAS Task Management System. Enable the project/user entry in MCP settings and inspect its tools.
• Review MCP_LOG_LEVEL, MCP_TRANSPORT_TYPE, NEO4J_PASSWORD, NEO4J_URI, NEO4J_USER for ATLAS Task Management System before sharing project .cursor/mcp.json; project scope travels with the repository.
• ATLAS Task Management System uses stdio here: Cursor 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 Cursor troubleshooting lives in the /clients/cursor guide.

Frequently asked questions