Clickup

  Antigravity (IDE & 2.0)

Download from antigravity.google. Covers Antigravity IDE (VS Code-based agentic editor) and Antigravity 2.0 (standalone desktop agent orchestration app). Both share the same configuration file.

Configuration Path: ~/.gemini/config/mcp_config.json

Tip: Open the Agent Panel → ... → Manage MCP Servers → View raw config to open this file directly. Or type /mcp in the prompt panel.

Option A: Remote / Streamable HTTP (Recommended)

{
  "mcpServers": {
    "ClickUp": {
      "serverUrl": "https://clickup-mcp.taazkareem.com/mcp",
      "headers": { "X-License-Key": "your-license-key" }
    }
  }
}

Option B: Local / STDIO

{
  "mcpServers": {
    "ClickUp": {
      "command": "npx",
      "args": ["-y", "@taazkareem/clickup-mcp-server@latest"],
      "env": {
        "CLICKUP_API_KEY": "your-api-key",
        "CLICKUP_TEAM_ID": "your-team-id",
        "CLICKUP_MCP_LICENSE_KEY": "your-license-key"
      }
    }
  }
}

  Antigravity CLI (agy)

A lightweight terminal-based interface (TUI) for Antigravity agents. Install with:

curl -fsSL https://antigravity.google/cli/install.sh | bash

Configuration Path: ~/.gemini/antigravity-cli/mcp_config.json

Tip: Run agy and type /mcp in the interactive session to manage servers from within the TUI.

Option A: Remote / Streamable HTTP (Recommended)

{
  "mcpServers": {
    "ClickUp": {
      "serverUrl": "https://clickup-mcp.taazkareem.com/mcp",
      "headers": { "X-License-Key": "your-license-key" }
    }
  }
}

Option B: Local / STDIO

{
  "mcpServers": {
    "ClickUp": {
      "command": "npx",
      "args": ["-y", "@taazkareem/clickup-mcp-server@latest"],
      "env": {
        "CLICKUP_API_KEY": "your-api-key",
        "CLICKUP_TEAM_ID": "your-team-id",
        "CLICKUP_MCP_LICENSE_KEY": "your-license-key"
      }
    }
  }
}

  Hermes Agent

Single Agent Configuration Path: ~/.hermes/config.yaml

Option A: Remote / Streamable HTTP

hermes mcp add clickup \
  --url https://clickup-mcp.taazkareem.com/mcp \
  --auth oauth && \
hermes config set mcp_servers.clickup.headers.X-License-Key "your-license-key"

Option B: Local / STDIO

hermes mcp add clickup \
  --command npx \
  --args -y @taazkareem/clickup-mcp-server@latest \
  --env CLICKUP_API_KEY="your-api-key" \
        CLICKUP_TEAM_ID="your-team-id" \
        CLICKUP_MCP_LICENSE_KEY="your-license-key"

• Run it: hermes

Multi-Agent Setup (Profiles + Personas)

Run a team of specialized agents on the same workspace (or separate). Each Hermes profile is an isolated agent with its own config and SOUL.md instructions. Configure each profile to match a persona (X-Persona) as needed. This will scope which ClickUp tools is in its context. Guide with examples:

1. Create the profiles

hermes profile create project_manager
hermes profile create task_worker
hermes profile create auditor

Optional: Use --clone to copy the existing config.yaml/.env/SOUL.md, or re-run the commands from above.

2. Set each profile's persona. The profile has the MCP config now, so just add the matching persona:

project_manager config set mcp_servers.clickup.headers.X-Persona "project_manager"
task_worker     config set mcp_servers.clickup.headers.X-Persona "task_worker"
auditor         config set mcp_servers.clickup.headers.X-Persona "auditor"

See → Advanced Configuration for more customized filtering options.

3. Give each agent its instructions in ~/.hermes/profiles/<name>/SOUL.md (auditor shown):

# ClickUp Auditor

You are a read-only project auditor. Observe and report — never change anything.
- Summarize task status, overdue items, and blockers concisely.
- Surface risks and recommend actions, but never execute them.
- If asked to create or modify a task, decline and explain you are read-only.

Run any agent query by its profile (call by User or Agent):

project_manager chat -q "Break the Q3 launch into a list with subtasks and owners"
auditor         chat -q "Audit the Sprint board and report what's at risk"

-OR-

Run a TUI or Gateway called by User:

project_manager gateway start
auditor         chat

Other (Custom Agents, etc.) For most other MCP-compliant hosts:

• Server URL: https://clickup-mcp.taazkareem.com/mcp
• Auth Header: X-License-Key: your-license-key

  OpenClaw (via mcporter)

1. Enable mcporter in ~/.openclaw/openclaw.json:

{ "skills": { "allowBundled": ["mcporter"] } }

2. Configure & Auth

# Add ClickUp as a remote server
mcporter config add ClickUp https://clickup-mcp.taazkareem.com/mcp --auth oauth --header "X-License-Key=your-license-key"

# Authenticate session
mcporter auth ClickUp

Pro Tip: Use Personas to define multiple isolated configurations (e.g., Auditor vs. Worker) in your agent's mcporter.json.

  Cursor

Configuration Path: <project-root>/.cursor/mcp.json

Option A: Remote / Streamable HTTP (Easiest)

{
  "mcpServers": {
    "ClickUp": {
      "url": "https://clickup-mcp.taazkareem.com/mcp",
      "headers": {
        "X-License-Key": "your-license-key"
      }
    }
  }
}

Option B: Local / STDIO

{
  "mcpServers": {
    "ClickUp": {
      "command": "npx",
      "args": ["-y", "@taazkareem/clickup-mcp-server@latest"],
      "env": {
        "CLICKUP_API_KEY": "your-api-key",
        "CLICKUP_TEAM_ID": "your-team-id",
        "CLICKUP_MCP_LICENSE_KEY": "your-license-key"
      }
    }
  }
}

  VS Code

Configuration Paths:

• Global: ~/Library/Application Support/Code/User/mcp.json
• Local: <project-root>/.vscode/mcp.json

Option A: Remote / Streamable HTTP (Easiest)

{
  "mcpServers": {
    "ClickUp": {
      "url": "https://clickup-mcp.taazkareem.com/mcp",
      "headers": {
        "X-License-Key": "your-license-key"
      }
    }
  }
}

Option B: Local / STDIO

{
  "mcpServers": {
    "ClickUp": {
      "command": "npx",
      "args": ["-y", "@taazkareem/clickup-mcp-server@latest"],
      "env": {
        "CLICKUP_API_KEY": "your-api-key",
        "CLICKUP_TEAM_ID": "your-team-id",
        "CLICKUP_MCP_LICENSE_KEY": "your-license-key"
      }
    }
  }
}

  Roo Code

Configuration Path: <project-root>/.roo/mcp.json

Option A: Remote / Streamable HTTP (Easiest)

{
  "mcpServers": {
    "ClickUp": {
      "url": "https://clickup-mcp.taazkareem.com/mcp",
      "headers": {
        "X-License-Key": "your-license-key"
      }
    }
  }
}

Option B: Local / STDIO

{
  "mcpServers": {
    "ClickUp": {
      "command": "npx",
      "args": ["-y", "@taazkareem/clickup-mcp-server@latest"],
      "env": {
        "CLICKUP_API_KEY": "your-api-key",
        "CLICKUP_TEAM_ID": "your-team-id",
        "CLICKUP_MCP_LICENSE_KEY": "your-license-key"
      }
    }
  }
}

  Claude Desktop

Configuration Path: ~/Library/Application Support/Claude/claude_desktop_config.json

Remote Setup (Requires mcp-remote adapter):

{
  "mcpServers": {
    "ClickUp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://clickup-mcp.taazkareem.com/mcp",
        "--header",
        "X-License-Key: your-license-key"
      ]
    }
  }
}

  Claude Code (CLI)

Run this command in your terminal:

claude mcp add --transport http ClickUp https://clickup-mcp.taazkareem.com/mcp \
  --header "X-License-Key: your-license-key"

  n8n

Option A: Remote / Streamable HTTP (Recommended)

1. In n8n, add an "MCP Client" node.
2. Set Connection Type to Streamable HTTP.
3. Auth Type: Multiple Headers Auth.
4. Header: X-License-Key Value: your-license-key
5. URL: https://clickup-mcp.taazkareem.com/mcp

Option B: Self-Hosted Docker Run the container:

docker run -d -p 3231:3231 ghcr.io/taazkareem/clickup-mcp-server:latest

In n8n, use URL: http://host.docker.internal:3231/mcp

  Codex (CLI, Desktop, IDE)

Codex clients (CLI, Desktop App, and VS Code extension) share a single source of truth for configuration.

Configuration Paths:

• Global: ~/.codex/config.toml
• Local: <project-root>/.codex/config.toml

Option A: Remote / Streamable HTTP (Easiest)

[mcp_servers.ClickUp]
url = "https://clickup-mcp.taazkareem.com/mcp"
http_headers = { "X-License-Key" = "your-license-key" }

Option B: Local / STDIO

[mcp_servers.ClickUp]
command = "npx"
args = ["-y", "@taazkareem/clickup-mcp-server@latest"]
env = {
  CLICKUP_API_KEY = "your-api-key",
  CLICKUP_TEAM_ID = "your-team-id",
  CLICKUP_MCP_LICENSE_KEY = "your-license-key"
}

Quick Tips:

• Codex CLI: Run codex mcp list to verify. Use codex mcp add ... as a CLI alternative to editing the file.
• VS Code Extension: Click ⚙ → MCP settings → Open config.toml.
• Desktop App: Go to Settings → Integrations & MCP.

  ChatGPT (Developer Mode)

Note: Requires a Business, Enterprise, or Edu workspace with Developer Mode enabled.

1. Enable Developer Mode: Ask your workspace admin to enable this under Workspace Settings → Permissions & Roles → Connected Data.
2. Connect MCP: Go to Settings → Connectors and toggle Developer Mode on.
3. Add Custom Connector:
   • Click Add connector (or "Create custom connector").
   • Choose MCP as the source type.
4. Configure:
   • Server URL: https://clickup-mcp.taazkareem.com/mcp
   • Authentication: Add HTTP header X-License-Key: your-license-key.
5. Use: Start a Developer Mode chat and select your ClickUp connector via Add sources.

  Augment Code

Configuration Path: <project-root>/.augment/settings.json

{
  "mcpServers": {
    "ClickUp": {
      "url": "https://clickup-mcp.taazkareem.com/mcp",
      "headers": {
        "X-License-Key": "your-license-key"
      }
    }
  }
}

  Auggie CLI

Run this command in your terminal:

auggie mcp add ClickUp --url https://clickup-mcp.taazkareem.com/mcp \
  --header "X-License-Key: your-license-key"

  Windsurf

Configuration Path: <project-root>/.codeium/windsurf/mcp_config.json

Option A: Remote / Streamable HTTP (Easiest)

{
  "mcpServers": {
    "ClickUp": {
      "url": "https://clickup-mcp.taazkareem.com/mcp",
      "headers": {
        "X-License-Key": "your-license-key"
      }
    }
  }
}

Option B: Local / STDIO

{
  "mcpServers": {
    "ClickUp": {
      "command": "npx",
      "args": ["-y", "@taazkareem/clickup-mcp-server@latest"],
      "env": {
        "CLICKUP_API_KEY": "your-api-key",
        "CLICKUP_TEAM_ID": "your-team-id",
        "CLICKUP_MCP_LICENSE_KEY": "your-license-key"
      }
    }
  }
}

See full documentation for parameters and advanced usage.