ClickUp MCP Server

Apify-hosted MCP server for ClickUp with 20 tools. Tasks, spaces, folders, lists, views, docs, and custom fields. No local setup needed.

Local serverstdioPython

What is the ClickUp MCP server?

Connect ClickUp to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Apify-hosted MCP server for ClickUp with 20 tools. Tasks, spaces, folders, lists, views, docs, and custom fields. No local setup needed. The clickup mcp server is what makes that connection.

What the server does

A Model Context Protocol server for ClickUp API interaction and automation. This server provides tools for AI systems to read, create, and update tasks, lists, and spaces in ClickUp.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Input — None
  • Returns — List of workspaces with IDs and names
  • Inputs — - workspace_id (string): ID of the workspace/team
  • Prerequisites — The Prerequisites tool exposed by this server

Installation

The server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Credentials and setup notes

Configuration is passed through the environment: CLICKUP_API_KEY, YOUR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Python 3.10 or higher - A ClickUp account with an API key

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. ClickUp's toolset — Input, Returns, Inputs and 1 more — is a fair guide to whether it matches your workflow.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
InputNone
ReturnsList of workspaces with IDs and names
Inputs- workspace_id (string): ID of the workspace/team
PrerequisitesThe Prerequisites tool exposed by this server.

How to install the ClickUp MCP server

{
  "mcpServers": {
    "apify-com-minutecontest-clickup": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/inspector"],
      "env": {
        "CLICKUP_API_KEY": "your-value",
        "YOUR_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Python 3.10 or higher - A ClickUp account with an API key
VariableDescriptionRequired
CLICKUP_API_KEYCredential the server authenticates with.Yes
YOUR_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use ClickUp to Input.
  • Use ClickUp to Returns.
  • Use ClickUp to Inputs.

Frequently asked questions

It connects ClickUp to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (Input, Returns, Inputs, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with ClickUp directly.