ATLAS Task Management System for VS Code: Setup & Config

What you can do with ATLAS Task Management System in VS Code

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

• Track prioritized tasks and prerequisite relationships.
• Keep cited knowledge connected to project work.
• Search across projects, tasks, and knowledge.

Before you start: ATLAS Task Management System in VS Code

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

1. Choose VS Code configuration scope

   For ATLAS Task Management System, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

2. Add ATLAS Task Management System to VS Code

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

3. Check ATLAS Task Management System in VS Code

   ATLAS Task Management System: Start in VS Code’s MCP controls; inspect output and trust prompts.

{
  "servers": {
    "atlas-mcp-server-cyanheads": {
      "type": "stdio",
      "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 VS Code

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

atlas_project_create

Look for atlas_project_create among VS Code's agent-mode tools after starting ATLAS Task Management System through the MCP controls.

Create one project or a batch with metadata and dependencies.

atlas_project_list

Look for atlas_project_list among VS Code's agent-mode tools after starting ATLAS Task Management System through the MCP controls.

atlas_project_update

Look for atlas_project_update among VS Code's agent-mode tools after starting ATLAS Task Management System through the MCP controls.

Update one project or multiple projects in a batch.

atlas_project_delete

Look for atlas_project_delete among VS Code's agent-mode tools after starting ATLAS Task Management System through the MCP controls.

ATLAS Task Management System: full stored tool descriptions

Troubleshooting ATLAS Task Management System in VS Code

• Make node (Node.js) available in the workspace, container, or remote environment hosting ATLAS Task Management System. Start through VS Code's MCP controls; inspect output and trust prompts.
• For ATLAS Task Management System, keep MCP_LOG_LEVEL, MCP_TRANSPORT_TYPE, NEO4J_PASSWORD, NEO4J_URI, NEO4J_USER out of version control; VS Code documents input variables and secret handling.
• ATLAS Task Management System uses stdio here: VS Code 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 VS Code troubleshooting lives in the /clients/vscode guide.

Frequently asked questions