ClickUp MCP Server Cursor IDE Setup 2026

Context switching between your code editor and ClickUp kills momentum. With ClickUp MCP in Cursor, you can create tasks, log updates, and check what's on your plate without touching the browser. Here's the complete setup.

What This Integration Enables

With ClickUp MCP running in Cursor, you can:

Prerequisites

Step 1: Get Your ClickUp API Token

1. Log in to ClickUp and click your avatar in the top-left.
2. Go to Settings → Apps.
3. Under API Token, click Generate (or copy your existing token).
4. Copy the token — it looks like pk_12345678_XXXXXXXXXXXX.

Keep this token private — it has full access to your ClickUp workspace.

Step 2: Find Your Workspace and List IDs (Optional)

For targeted queries, it helps to know your IDs upfront:

You can also discover these dynamically through the MCP server after setup.

Step 3: Install the ClickUp MCP Server

npm install -g @mikearango/mcp-clickup

Or run without installing:

npx @mikearango/mcp-clickup --help

Step 4: Configure Cursor

Edit ~/.cursor/mcp.json (macOS/Linux) or %APPDATA%\Cursor\mcp.json (Windows):

{
  "mcpServers": {
    "clickup": {
      "command": "npx",
      "args": ["-y", "@mikearango/mcp-clickup"],
      "env": {
        "CLICKUP_API_TOKEN": "pk_your_token_here",
        "CLICKUP_TEAM_ID": "your_team_id_here"
      }
    }
  }
}

The CLICKUP_TEAM_ID is optional but helps scope queries faster. If you omit it, the server will auto-discover your workspaces.

Step 5: Restart and Verify

Quit Cursor and reopen. Go to Settings → Features → MCP — the "clickup" server should appear with a green status indicator.

Test in Composer:

List my assigned tasks in ClickUp that are in progress

If you get your task list back, the integration is live.

Real-World Use Cases

Creating a Task While Coding

You spot a bug while working on something else:

Create a ClickUp task in the "Bugs" list titled 
"Fix null pointer in user auth middleware" with priority High 
and assign it to me

Updating Status Without Tab-Switching

Just finished a PR:

Update the ClickUp task "Implement OAuth2 login" status to "In Review"

Checking Your Sprint

List all tasks assigned to me in the "Sprint 14" list 
that are not yet done, sorted by due date

Logging Progress in a Comment

Add a comment to ClickUp task 86abc123: 
"Completed the API integration, waiting on design review before closing"

Creating Subtasks

Create 3 subtasks under ClickUp task "User Dashboard Redesign":
1. "Wireframe approval"
2. "Frontend implementation" 
3. "Mobile responsive QA"

Troubleshooting

Authentication fails with 401

"Team not found" error

Tasks not appearing despite correct list ID

Server starts but returns empty results

Using ClickUp Docs via MCP

Some versions of the ClickUp MCP server also support Docs (ClickUp's native document editor):

Search ClickUp Docs for "deployment checklist"

Create a new ClickUp Doc in the Engineering space titled 
"API Rate Limiting Policy v2"

Check your MCP server's README to confirm which tools are exposed — implementations vary by maintainer.

Combining with GitHub MCP

The natural pairing: use ClickUp MCP to pull task context, then GitHub MCP to reference the related PR.

Get the details for ClickUp task CU-abc123, 
then find the GitHub PR in the "backend" repo that mentions this task ID

This closes the loop between what you're building and why you're building it — all without leaving Cursor.

Security

Browse More MCP Integrations

ClickUp is one piece of a larger productivity stack you can wire into Cursor. See the full MCP server directory for Notion, Linear, Jira, Slack, GitHub, and more.