ClickUp Project Management

Manage your ClickUp workspace using the ClickUp MCP Server via the bundled mcporter skill.

External Endpoints

Security & Privacy

• What stays local: Your CLICKUP_MCP_LICENSE_KEY is stored in ~/.openclaw/openclaw.json (or your shell environment). OAuth tokens are cached locally by mcporter in ~/.mcporter/.
• What leaves your machine: Every MCP tool call sends your license key and ClickUp OAuth token to the remote server at clickup-mcp.taazkareem.com. Tool call payloads (task data, workspace hierarchy, etc.) are also transmitted.
• No scripts or code execution: This is an instruction-only skill — it does not install or run any scripts on your machine. It relies on the bundled mcporter client.
• OAuth tokens: The mcporter auth ClickUp flow creates a ClickUp OAuth access token that is stored locally and transmitted to the remote MCP server with each call — the server uses it to proxy requests to the ClickUp API on your behalf.

Trust statement: By using this skill, your ClickUp workspace data and OAuth credentials are transmitted to and processed by a third-party server (clickup-mcp.taazkareem.com) operated by Talib Kareem. Only install this skill if you trust this operator and have reviewed the project repository.

Prerequisites

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

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

2. Configure ClickUp (one-time setup):

   # Use the $CLICKUP_MCP_LICENSE_KEY env provided by the skill metadata
   mcporter config add ClickUp https://clickup-mcp.taazkareem.com/mcp \
     --auth oauth \
     --header "X-License-Key=$CLICKUP_MCP_LICENSE_KEY"
   

3. Authenticate (tokens are cached):

   mcporter auth ClickUp
   

Optimization: Tool Filtering Personas

\x3C!-- Last updated: v0.12.14 -->

To reduce context noise and improve AI accuracy, you can limit the tools available to your agent using the X-Enabled-Tools header in your mcporter config.

Proactive Agent Rule: If the current task aligns with one of these personas, you should dynamically apply the filtering header by re-running the mcporter config add command with the appropriate X-Enabled-Tools or X-Disabled-Tools flag.

Recommended Presets

How to Apply

To switch to a persona (e.g., Task Worker), run:

mcporter config add ClickUp https://clickup-mcp.taazkareem.com/mcp \
  --header "X-License-Key=$CLICKUP_MCP_LICENSE_KEY" \
  --header "X-Enabled-Tools=get_workspace_hierarchy,..."

Personalization & Workflows

Following the OpenClaw standard, do not modify this skill for environment-specific details. Instead, use your agent's workspace/TOOLS.md file to define:

• Custom Workflows: Define multi-step orchestrations (e.g., "Daily Wrap-up").
• Specific IDs: Store commonly used team_id, list_ids, folder_ids, etc.
• Structures or Conventions: Any rules or consistent behavior (e.g., common custom fields, tag rules, etc.)

Usage

Use the standard mcporter command pattern:

mcporter call ClickUp.\x3Ctool_name> [parameters]