Connect ClickUp to Claude Code

Make Claude create tasks and move work across statuses in ClickUp. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect ClickUp to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect ClickUp, you add a ClickUp MCP server: a small hosted service that exposes ClickUp's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own ClickUp account. No API keys pasted into config files.

claude mcp add --transport http clickup https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in ClickUp once connected?

Full read-write ClickUp access lets Claude create tasks in the right list, set assignees and due dates, move items across statuses, update custom fields, and post comments, then leave deletes for you to approve. The triage and updating that used to mean clicking through ClickUp happen where the work already lives.

Create a task in a specific list with description, assignees, and due date
Move a task across statuses as work progresses
Update custom fields, priority, and tags on existing tasks
Add a comment or checklist item to keep a task current
Find every task matching a query and propose batched updates
Create a subtask under an existing parent task

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same ClickUp access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the ClickUp API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when ClickUp changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build ClickUp connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same ClickUp connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own ClickUp account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on ClickUp's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to ClickUp?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the ClickUp account it signs in with. Revoking access is one click in ClickUp.

More on the ClickUp connector

ClickUp connector for claude.ai Asana + Claude Code Monday.com + Claude Code Jira + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us