Skip to content
MCP server

ClickUp (full API)

MCP server giving AI clients access to the full ClickUp API through four tools

Runs locally
Install

ClickUp (full API) is an open-source MCP server for productivity. It runs locally on your machine and is started by your AI client.

Pricing
Open source
Platforms
CLI, API, Self-hosted
Runs
Locally
Version
2.1.1
Listing updated

Similar MCP servers

Install

Run in a terminal

claude mcp add clickup-full-mcp --env CLICKUP_API_TOKEN='<CLICKUP_API_TOKEN>' -- npx -y clickup-full-mcp

Add to claude_desktop_config.json

{
  "mcpServers": {
    "clickup-full-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "clickup-full-mcp"
      ],
      "env": {
        "CLICKUP_API_TOKEN": "<CLICKUP_API_TOKEN>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "clickup-full-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "clickup-full-mcp"
      ],
      "env": {
        "CLICKUP_API_TOKEN": "<CLICKUP_API_TOKEN>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "clickup-full-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "clickup-full-mcp"
      ],
      "env": {
        "CLICKUP_API_TOKEN": "<CLICKUP_API_TOKEN>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "clickup-full-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "clickup-full-mcp"
      ],
      "env": {
        "CLICKUP_API_TOKEN": "<CLICKUP_API_TOKEN>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "clickup-full-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "clickup-full-mcp"
      ],
      "env": {
        "CLICKUP_API_TOKEN": "<CLICKUP_API_TOKEN>"
      }
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • CLICKUP_API_TOKENClickUp personal API token (pk_...) or OAuth access tokenRequired
  • CLICKUP_WORKSPACE_IDDefault Workspace (team) ID, auto-filled into team_id / workspace_id
  • CLICKUP_TOOL_MODEmeta (default: 4 tools for the whole API) or full (one tool per endpoint)
  • CLICKUP_TOOLSETSComma-separated toolsets to expose, e.g. tasks,comments,time_tracking
  • CLICKUP_READ_ONLYtrue to expose only read (GET) operations
  • CLICKUP_RESPONSE_FORMATcompact (default: minified, null/empty fields removed), json (every field) or pretty (indented)

About ClickUp (full API)

Runs locally over stdio and lets MCP-compatible assistants reach every ClickUp v2 and v3 operation, covering tasks, time tracking, Docs and Chat. Instead of registering one tool per endpoint, it exposes a small meta layer that searches operations by keyword, describes their schemas on demand and calls them by name, which keeps the context cost of the tool list very low.

Scope can be narrowed with environment variables: a read-only mode that only allows GET requests, toolset filters, and a deny-list for specific operations such as deleting a space. A default workspace ID can be set so assistants do not need to look it up on every call, and responses are returned in a compact form with empty fields removed, with options for full or indented JSON.

It suits developers and project managers who want an assistant to create and update tasks, log time, comment or post to ClickUp Chat from Claude, Cursor or VS Code, and who prefer that access to stay on their own machine.

Tools this server provides (4)

Taken from the project documentation; the running server may differ.

clickup_search_operations
Finds operations by keyword.
clickup_describe_operation
Returns an operation's description and JSON input schema.
clickup_call_operation
Calls any ClickUp operation by name.
clickup_request
Raw request to any /api/v2 or /api/v3 path.

What it does

Full API coverage
Exposes 173 ClickUp operations across API v2 and v3, generated from the official OpenAPI specs.
Four-tool meta mode
Keeps the tool list small by searching, describing and calling operations through a few generic tools.
Read-only option
An environment flag restricts the server to GET operations so nothing can be changed.
Toolset and operation filters
Limit exposed areas such as tasks or time tracking, or hide individual operations by name.
Compact responses
Default output is minified with null and empty fields removed, with full or pretty formats available.
Local stdio operation
Runs on the user's machine and sends the API token only to the ClickUp API host.

Good for

  • Create and update tasks, subtasks and checklists from an AI assistant
  • Log or review time entries for a date range
  • Summarise or post messages in ClickUp Chat channels
  • Generate Docs pages from task data written in Markdown
  • Give an agent limited, read-only access to a ClickUp workspace

Pricing

Open source

Free and MIT-licensed; runs locally.

ClickUp (full API) FAQ

Does ClickUp (full API) work with clients other than Claude and Cursor?

Yes. It runs as a standard stdio MCP server, so any client or agent framework that can launch local stdio servers can use it.

Can the server be restricted so ClickUp (full API) cannot modify data?

Setting CLICKUP_READ_ONLY to true exposes only GET operations and limits the raw request tool to GET.

What credentials are needed?

A ClickUp personal API token starting with pk_, or an OAuth access token, set as CLICKUP_API_TOKEN.

Is ClickUp (full API) an official ClickUp product?

No. It is an independent MIT-licensed community project and is not affiliated with or endorsed by ClickUp.

Is ClickUp (full API) free?

Yes. ClickUp (full API) is open source, so you can use and self-host it for free.

How do I add ClickUp (full API) to Claude Code?

Run this command in your terminal: claude mcp add clickup-full-mcp --env CLICKUP_API_TOKEN='<CLICKUP_API_TOKEN>' -- npx -y clickup-full-mcp

What are the best alternatives to ClickUp (full API)?

The closest alternatives to ClickUp (full API) are Clickup, Clickup, IterDone, Orangescrum MCP Server and GetItDone.

Where this comes from

  • Description: written from the project's README and its MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers