Configuration Guide

This guide covers all configuration options for the Darbot Deepmind MCP Server, including environment variables, client integrations, and setup procedures.

Environment Variables

Configure the server behavior using these environment variables:

Setting Environment Variables

Linux/macOS

export DISABLE_THOUGHT_LOGGING=true
export LOG_LEVEL=debug
npm start

Windows Command Prompt

set DISABLE_THOUGHT_LOGGING=true
set LOG_LEVEL=debug
npm start

Windows PowerShell

$env:DISABLE_THOUGHT_LOGGING="true"
$env:LOG_LEVEL="debug"
npm start

Claude Desktop Integration

Configure Darbot Deepmind MCP in Claude Desktop by editing the configuration file:

Configuration File Location

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

NPX Configuration

{
  "mcpServers": {
    "darbot-deepmind": {
      "command": "npx",
      "args": [
        "-y",
        "@darbotlabs/darbot-deepmind-mcp"
      ]
    }
  }
}

Docker Configuration

{
  "mcpServers": {
    "darbot-deepmind": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "mcp/darbot-deepmind"
      ],
      "env": {
        "DISABLE_THOUGHT_LOGGING": "false"
      }
    }
  }
}

Local Development Configuration

{
  "mcpServers": {
    "darbot-deepmind": {
      "command": "node",
      "args": [
        "/path/to/darbot-deepmind-mcp/dist/index.js"
      ],
      "env": {
        "DISABLE_THOUGHT_LOGGING": "false",
        "LOG_LEVEL": "debug"
      }
    }
  }
}

VS Code Integration

Configure the server for VS Code's MCP support by creating or editing .vscode/mcp.json:

Quick Install

Click the badge below to install automatically:

Manual Configuration

{
  "servers": {
    "darbot-deepmind": {
      "command": "npx",
      "args": [
        "-y",
        "@darbotlabs/darbot-deepmind-mcp"
      ]
    }
  }
}

Docker Compose Setup

For containerized deployments, use Docker Compose:

version: '3.8'

services:
  darbot-deepmind:
    image: mcp/darbot-deepmind
    container_name: darbot-deepmind-mcp
    environment:
      - DISABLE_THOUGHT_LOGGING=false
      - LOG_LEVEL=info
    stdin_open: true
    tty: false
    restart: unless-stopped

Starting with Docker Compose

docker-compose up -d darbot-deepmind

Advanced Configuration

Custom Logging Configuration

For production deployments, you may want to configure custom logging:

{
  "mcpServers": {
    "darbot-deepmind": {
      "command": "npx",
      "args": ["-y", "@darbotlabs/darbot-deepmind-mcp"],
      "env": {
        "DISABLE_THOUGHT_LOGGING": "true",
        "LOG_LEVEL": "warn"
      }
    }
  }
}

Memory and Performance Tuning

For handling complex reasoning chains, you can adjust Node.js memory limits:

{
  "mcpServers": {
    "darbot-deepmind": {
      "command": "node",
      "args": [
        "--max-old-space-size=4096",
        "/path/to/dist/index.js"
      ]
    }
  }
}

Development Mode

For development with hot-reloading:

{
  "mcpServers": {
    "darbot-deepmind": {
      "command": "npm",
      "args": ["run", "dev"],
      "cwd": "/path/to/darbot-deepmind-mcp",
      "env": {
        "NODE_ENV": "development",
        "LOG_LEVEL": "debug"
      }
    }
  }
}

Verification

After configuration, verify the setup:

1. Restart Claude Desktop or VS Code
2. Check for "darbot-deepmind" in available tools
3. Test with a simple reasoning task
4. Review logs for any errors

Configuration Best Practices

• Use NPX for simplicity: The NPX method requires no local installation
• Docker for isolation: Use Docker when you need environment isolation
• Disable logging in production: Set DISABLE_THOUGHT_LOGGING=true for cleaner output
• Version pinning: For production, consider pinning to a specific version
• Monitor memory usage: For complex reasoning, monitor and adjust memory limits

Troubleshooting Configuration

Server Not Detected

• Verify JSON syntax in configuration files
• Check file paths are correct (especially on Windows)
• Ensure Node.js 18+ is installed
• Restart the MCP client after changes

Environment Variables Not Working

• Ensure environment variables are defined in the env section
• Check for typos in variable names
• Verify the client supports environment variable passing
• Review server logs for loaded configuration

Next Steps