Skip to main content
MCP SERVER

ClickUp MCP Server

Connect ClickUp to your AI coding tool to manage tasks, Docs, and time tracking.

Community · Productivity · The Codegen Team · Updated Jul 2026

The ClickUp MCP server is ClickUp's official hosted endpoint for connecting AI coding tools to a workspace. Your agent can create and update tasks, set assignees and due dates, read and write Docs, post comments, and log time, all in natural language from inside your editor.

The practical wins are workflow orchestration and reporting. An agent can pull overdue tasks and draft a standup summary, turn a finished feature into a status update in Docs, or triage incoming work with priorities and assignees. Because ClickUp hosts the server, there is nothing to run locally and no package to install.

The server is in public beta and available on every ClickUp plan. It exposes many of the actions in the ClickUp API, though not the full surface, so a few features still live only in the UI or the REST API.

Get ClickUp at the source

View on GitHub

Community server documented by Codegen. The canonical source is the repo above, and any install below is from the project's own docs.

How do you connect it?

$ npx -y mcp-remote https://mcp.clickup.com/mcp

How do you configure it per tool?

Pick your tool, copy the snippet into its MCP config file, and restart the tool.

.mcp.json json
{
  "mcpServers": {
    "clickup": {
      "type": "http",
      "url": "https://mcp.clickup.com/mcp"
    }
  }
}
.cursor/mcp.json json
{
  "mcpServers": {
    "clickup": {
      "url": "https://mcp.clickup.com/mcp"
    }
  }
}
.vscode/mcp.json json
{
  "servers": {
    "clickup": {
      "type": "http",
      "url": "https://mcp.clickup.com/mcp"
    }
  }
}

What can it do once connected?

What the server exposes to your AI through MCP.

Capability Type Description
Search Workspace Tool Search across tasks, Lists, Folders, and Docs in a single query.
Create Task Tool Create a task in a List with assignees, a due date, and priority.
Update Task Tool Change status, assignees, due dates, or description on an existing task.
Create Task Comment Tool Post a comment on a task, including at-mentions of teammates.
Add Time Entry Tool Log time against a task or start and stop a running timer.
Create Document Tool Create a ClickUp Doc and add or edit its pages.
Get Workspace Hierarchy Tool Read the full Space, Folder, and List structure of the workspace.

How do you authenticate?

This server uses OAuth. Set it up once and the AI tool injects it on every call.

The ClickUp MCP server uses OAuth, so there is no API key to paste. The first time your tool connects, it opens a browser window to sign in to ClickUp and authorize the workspace you want to expose. After that, the client reuses the credentials.

Authorize in your tool

In Claude Code, run /mcp after adding the server and follow the authorization link. In VS Code, open the MCP servers list, start the ClickUp server, and follow the sign-in prompts. In Cursor and Windsurf, the authorization window opens the first time the agent calls a ClickUp tool.

Confirm the connection

Check that the server shows as connected and authorized before relying on it. In Claude Code, claude mcp list should show clickup, and /mcp should report it as authenticated. Then ask the agent to run a read-only action, such as listing your Spaces, to confirm it can reach the workspace.

How the ClickUp MCP chains tools in one request

The server’s strength is combining several tools in a single call. Ask it to find overdue tasks and post a summary, and it runs a workspace search, reads the matching tasks, then sends a chat message without you scripting each step. That chaining is what separates it from hitting the ClickUp REST API one endpoint at a time.

When to use the ClickUp MCP versus the REST API

Reach for the MCP server when you want an AI agent to act inside a coding session in natural language, scoped to your own permissions. Reach for the REST API when you need deterministic scripts, server-to-server automation, webhooks, or a feature the MCP server does not expose. The MCP server is built for interactive, agent-driven work. The API is built for pipelines.

What does it not expose?

  • The MCP server exposes tasks, Docs, time tracking, chat, and workspace hierarchy, but it does not cover every ClickUp feature. Goals, Dashboards, and Automations are not available as MCP tools, so building or reporting on those still runs through the ClickUp UI or the REST API. Connected Search across third-party apps is also unavailable through the server.

Other servers in this category.

Frequently Asked Questions

Build faster with AI agents

Assemble skills, rules, and MCP servers into agents that run on every commit. ClickUp is where the output they ship gets tracked and managed.

Get Started →