ATLAS Task Management System for Claude Desktop: Setup

What you can do with ATLAS Task Management System in Claude Desktop

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.
• Keep cited knowledge connected to project work.

Before you start: ATLAS Task Management System in Claude Desktop

• 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 Claude Desktop configuration

1. Choose Claude Desktop configuration scope

   For ATLAS Task Management System, open macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json. Merge under mcpServers via Settings → Developer → Edit Config when available.

2. Add ATLAS Task Management System to Claude Desktop

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

3. Check ATLAS Task Management System in Claude Desktop

   ATLAS Task Management System: Fully quit and reopen Claude Desktop; check developer diagnostics.

{
  "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 Claude Desktop

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

atlas_project_create

When Claude Desktop requests atlas_project_create from ATLAS Task Management System, review the action before approving it.

Create one project or a batch with metadata and dependencies.

atlas_project_list

When Claude Desktop requests atlas_project_list from ATLAS Task Management System, review the action before approving it.

List projects or retrieve details with filters and pagination.

atlas_project_update

When Claude Desktop requests atlas_project_update from ATLAS Task Management System, review the action before approving it.

atlas_project_delete

When Claude Desktop requests atlas_project_delete from ATLAS Task Management System, review the action before approving it.

ATLAS Task Management System: full stored tool descriptions

Troubleshooting ATLAS Task Management System in Claude Desktop

• Fully quit and reopen Claude Desktop for ATLAS Task Management System. If node (Node.js) is missing, check the desktop process's PATH, which may differ from your terminal.
• In Claude Desktop's ATLAS Task Management System entry, check MCP_LOG_LEVEL, MCP_TRANSPORT_TYPE, NEO4J_PASSWORD, NEO4J_URI, NEO4J_USER. Keep secrets out of shared screenshots and repositories.
• ATLAS Task Management System uses stdio here: Claude Desktop 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 Claude Desktop troubleshooting lives in the /clients/claude-desktop guide.

Frequently asked questions