Clickup MCP Server

by clickup Your server? Claim it

answering

Clickup is answering right now. Last checked 14 min ago.

Uptime history 47 days of history · worst day 98%

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

565 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Clickup missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://mcp.clickup.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.clickup.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://mcp.clickup.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.clickup.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.clickup.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.clickup.com/mcp	streamable-http	sign-in	551 ms	14 min ago

Alternatives to Clickup

same job, measured the same way

Clickup

by pipeworx-io

ClickUp MCP — wraps the ClickUp REST API v2 (BYO API key)

40 tools answering

ClickUp MCP Pro

by helbertparanhos

The most complete ClickUp MCP server — 161 tools + clickup_raw for the full v2/v3 API.

132 installs/wk local only

Clickup MCP

by cvrt-jh

Lightweight ClickUp MCP server - 37 tools, token-optimized (95% smaller responses)

43 installs/wk local only

Pickle

by adityaarsharma

Free, local MCP server that audits ClickUp, Slack & Teams for work that slipped through.

57 installs/wk local only

ClickUp MCP Server

by retailbox-automation

Audit ClickUp workspaces: spaces, folders, lists, custom fields, tasks, and views.

local only

Beans MCP

by selfagency

Interact with the Beans CLI issue tracker agentically

41 installs/wk local only

Rebar

by navapbc

Event-sourced ticket tracker + Jira reconciler, exposed as a Python library, CLI, and MCP server.

580 installs/wk local only

Clickup — questions

Answers built from our own checks of this server.

Why is there no tool list for Clickup?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Clickup working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 565 ms. The bar chart above shows every period we have measured.

How do I connect Clickup?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Clickup?

No API key is involved. Clickup answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Clickup?

It answers our handshake in 565 ms on average, which is faster than 23% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.