Not able to use w/ Roo Cline

[TotalLag]

Just following the instructions to install and bring docker up, I am able to connect manually if using npm run start:stdio or npm run start:http but when using the MCP settings I cannot connect with the server it brings up. I do have redirects setup so localhost passes through from Win to WSL.

Environment:

• Win11
• WSL2
• VSCode
• Roo Cline

[ParryManta]

Solution: Update MCP Client Configuration (e.g., mcp_settings.json)

The solution involves ensuring bash is used in a way that sources profile files and that environment variables are explicitly exported within the command string executed by wsl.

Here’s an example configuration snippet:

{
  "mcpServers": {
    "atlas-mcp-server-stdio":
      "command": "wsl",
      "args": [
        "-e",
        "bash", "-ic", // Use 'bash -ic' to ensure .bashrc is sourced (for NVM, etc.)
        // The following is one long command string:
        "export NEO4J_URI='bolt://localhost:7687' && " +
        "export NEO4J_USER='YOUR_NEO4J_USERNAME' && " +         // <-- REPLACE
        "export NEO4J_PASSWORD='YOUR_NEO4J_PASSWORD' && " +   // <-- REPLACE
        "export LOG_LEVEL='info' && " +                       // Or 'debug'
        "export NODE_ENV='development' && " +                 // Or 'production'
        "cd /path/to/your/atlas-mcp-server/in/wsl && " + // <-- REPLACE with actual WSL path
        "node dist/index.js"
      ],
      // Optional: Redundant 'env' block if vars are in 'args'.
      // Can be useful if client needs them for other reasons or as documentation.
      "env": {
        "NEO4J_URI": "bolt://localhost:7687",
        "NEO4J_USER": "YOUR_NEO4J_USERNAME",          // <-- REPLACE
        "NEO4J_PASSWORD": "YOUR_NEO4J_PASSWORD",    // <-- REPLACE
        "LOG_LEVEL": "info",
        "NODE_ENV": "development"
      },
      "enabled": true,
      "type": "stdio" // Assuming stdio transport
    }
    // ... other configured servers ...
  }
}

Explanation:

"command": "wsl": Directs the client to use WSL.
"args": ["-e", "bash", "-ic", "...command..."]:
bash -ic: Invokes bash as an interactive command shell, which helps in loading ~/.bashrc and making node (especially if installed via NVM) available in the PATH.
The long command string (joined by &&):
export VAR='value': Sets each environment variable directly within the WSL shell before the node script runs. Use single quotes for values, especially for passwords with special characters.
cd /path/to/...: Navigates to the server's directory. This path must be the correct absolute path within your WSL filesystem.
node dist/index.js: Executes the server.
Important Considerations:

Replace Placeholders: Critically, replace YOUR_NEO4J_USERNAME, YOUR_NEO4J_PASSWORD, and /path/to/your/atlas-mcp-server/in/wsl with your actual values.
Neo4j in WSL: This assumes Neo4j (e.g., Dockerized) is running within the same WSL2 environment and is accessible via localhost:7687 from other WSL processes.
Node.js in WSL: Node.js and npm must be correctly installed and configured in your WSL2 distribution.
This method ensures the atlas-mcp-server starts within WSL with the correct execution context and all necessary environment variables.