A ClickUp MCP server gives an AI client tools to create and update tasks, navigate spaces and lists, and manage your workspace — so you can run ClickUp from chat. The popular community server uses an API token. Here's the setup.
Step 1 — get an API token + team ID
In ClickUp: Settings → Apps → API Token (personal token). Your team (workspace) ID is the number in your ClickUp URL after /app/.
Step 2 — configure the client
A widely-used community server runs via npx:
{
"mcpServers": {
"clickup": {
"command": "npx",
"args": ["-y", "@taazkareem/clickup-mcp-server@latest"],
"env": {
"CLICKUP_API_KEY": "your_token",
"CLICKUP_TEAM_ID": "your_team_id"
}
}
}
}
Package names vary between community implementations — match the repo you choose. Restart the client; see MCP config file location.
Verify
Ask: "List tasks in my 'Sprint' list and create one titled 'Write release notes'." Real tasks back confirm it works.
Common problems
401/ unauthorized — wrong token or team ID.- Can't find a list/space — names are case-sensitive; or your token lacks access.
- No tools in client — Node 18+ for
npx; see Cursor MCP not working.
Security
A personal token can touch your whole workspace. Keep it out of shared config and review the community server first — see how to vet an MCP server.
Going further
ClickUp pairs with GitHub and Slack for team ops. Compare trackers in Linear MCP vs Jira MCP. Browse the productivity category or curated loadouts.