Clickup

Grok Bot is the Cursor / xAI cloud agent harness. Custom MCP servers connect to Grok Bot conversationally via remote public HTTPS endpoints.

Note: This configuration is specifically for the Grok Bot agent harness (Cursor / xAI), distinct from grok.com web connectors.

Remote MCP Endpoint: https://clickup-mcp.taazkareem.com/mcp (Streamable HTTP)

1. Add via Chat: Grok Bot typically has no manual settings form for custom MCP servers. Instruct the Bot directly in chat:
   text

   Add a custom MCP server named ClickUp at https://clickup-mcp.taazkareem.com/mcp using streamable HTTP.

2. Public HTTPS Requirement: The endpoint must be public HTTPS (https://clickup-mcp.taazkareem.com/mcp). Localhost or stdio running on your local machine will not work because Grok Bot runs in the cloud.
3. Authentication: Connectors authenticate via MCP OAuth 2.1 (preferred). If a license header is supported by the client prompt, provide X-License-Key: your-license-key. Never paste secret license keys directly into the chat transcript—only provide them if prompted by a dedicated secure secret dialog.
4. Cloud Computer Stdio (Alternative): You can optionally run stdio directly on the Bot's cloud computer (not your local Mac) using:
   bash

   npx -y @taazkareem/clickup-mcp-server@latest

   (Do not store credentials in command arguments on shared or team bots).
5. Usage: Once connected, attach the server in chat with @ClickUp or reference tasks directly. Built-in catalog plugins can also be managed in the Connect Apps sidebar (formerly Marketplace).

Meta Muse is Meta's cloud AI assistant supporting tool integrations via Model Context Protocol connectors.

Remote MCP Endpoint: https://clickup-mcp.taazkareem.com/mcp (Streamable HTTP)

Important: The MCP server must be hosted on a public HTTPS endpoint because Muse executes in Meta's cloud infrastructure. Meta does not review custom connectors—grant permissions with caution.

1. Create Custom Connector via Chat: While built-in connectors can be found in Settings → Connectors, custom MCP connectors are created conversationally. Send Muse the following request in chat:
   text

   Create a Custom Connector for ClickUp MCP.Transport: remote streamable HTTPURL: https://clickup-mcp.taazkareem.com/mcpAuth: OAuth (preferred) or license key via Secure Credentials as header X-License-Key

   (Alternatively, if your client interface exposes it, navigate to Settings → Connectors → Add custom connector and paste the server URL).
2. Authentication & Credentials: Connect via OAuth 2.1 (preferred). If configuring a license key header (X-License-Key: your-license-key), store it in Muse's Secure Credentials Store when prompted—never post raw secret keys into conversational chat.
3. Usage: Ask Muse to interact with your ClickUp workspace (e.g. "List all high-priority tasks in my Sprint").

Dots are OpenAI's always-on autonomous agents operating within ChatGPT. Rather than configuring MCP servers directly inside an individual Dot's settings, Dots execute through supported plugins and custom MCP connectors installed and enabled on your ChatGPT account.

Note: This section covers OpenAI's native ChatGPT Dots agent feature (not the unrelated GetDot analytics product). For standard ChatGPT setup, see ChatGPT (Developer Mode).

Remote MCP Endpoint: https://clickup-mcp.taazkareem.com/mcp (Streamable HTTP)

1. Add Custom MCP Server in ChatGPT:
   • In ChatGPT on the web, navigate to Plugins → + → Add custom MCP server (or via Settings → Connectors).
   • Set Name: ClickUp
   • Set Server URL: https://clickup-mcp.taazkareem.com/mcp
2. Authentication:
   • Configure authentication using OAuth 2.1 (preferred) or add HTTP header X-License-Key: your-license-key when the form allows.
   • Acknowledge the risk warning and click Create as a plugin.
3. Account & Workspace Requirements:
   • Install and enable the plugin on your ChatGPT account.
   • Developer Mode and workspace administrative permissions apply (typically requires a ChatGPT Business, Enterprise, or Edu workspace for full read/write MCP capability; Pro accounts may have limited access).
4. Enable & Verify with your Dot:
   • Prompt your Dot in chat to access ClickUp (e.g. "Review active sprint tasks on ClickUp").
   • Documentation Gap Note: OpenAI documentation states that Dots utilize supported plugins on the account, but does not explicitly document whether every custom third-party MCP connector is universally recognized as "supported" across all Dot capabilities. Verify tool availability directly in your Dot chat session to confirm ClickUp actions trigger properly.

Claude Duet is Anthropic's proactive, always-on personal AI agent (research preview for Pro/Max users). Operating continuously in the cloud, Duet surfaces morning briefs, triages incoming items, and coordinates workflows across integrated apps without requiring synchronous chat prompting. Because Claude Duet inherits its connected apps, memory, and skills directly from your Claude account, adding the ClickUp MCP connector equips Duet to monitor and manage your tasks, sprints, docs, and comments.

Remote MCP Endpoint: https://clickup-mcp.taazkareem.com/mcp (Streamable HTTP)

Important: The MCP server must be hosted on a public HTTPS endpoint because Claude Duet executes in Anthropic's cloud environment. Duet incorporates built-in confirmation safeguards: it proactively organizes and drafts updates, but pauses for your explicit sign-off before executing high-impact modifications.

1. Add Custom Connector in Claude:
   • In Claude on the web or desktop, click your profile / customize menu and navigate to Customize → Connectors (or click the + icon in any active chat and choose Manage connectors).
   • Click + next to Connectors and select Add custom connector.
   • Set Name: ClickUp
   • Set Server URL: https://clickup-mcp.taazkareem.com/mcp
2. Authentication & Permissions:
   • Configure authentication using OAuth 2.1 (preferred) or supply your license key via HTTP header X-License-Key: your-license-key.
   • Click Add to complete registration. (For Claude Team and Enterprise workspaces, custom connectors are added and approved by an Owner/Admin in Organization Settings before team members enable them).
3. Usage & Proactive Routines:
   • Instruct Claude Duet in chat to track ClickUp activity (e.g. "Include high-priority ClickUp tasks in my daily morning brief" or "Alert me when blocked sprint dependencies clear").
   • Verify tool availability directly in your Duet session to ensure proactive ClickUp actions execute with proper approval prompts.

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"      }    }  }}

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"      }    }  }}

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_managerhermes profile create task_workerhermes 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 startauditor         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

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

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

2. Configure & Auth

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

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

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"      }    }  }}

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"      }    }  }}

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"      ]    }  }}

Tip for Claude Duet: To use ClickUp with Anthropic's autonomous background agent, see the Claude Duet Setup section.

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"

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 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.

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.

Tip for OpenAI Dots: To use ClickUp with autonomous background agents in ChatGPT, see the Dots Setup section.

Option A: IDE Settings (VS Code / JetBrains)

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

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

Option B: Auggie CLI (Terminal)

Run this command in your terminal:

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

See full documentation for parameters and advanced usage.