Claude Code How to use ClickUp with Claude Code
You want ClickUp inside Claude Code so it can triage overdue work, turn project requests into assigned tasks, prepare a project status update, and resolve conversations on blocked tasks — without you copy-pasting between tabs. Here is the whole setup, once.
Create your ClickUp gateway
The gateway is the thing Claude Code connects to, and it is where you decide which ClickUp tools an agent may use. You create it once and every client reuses it.
-
Create an Arcade account
Sign up and open the dashboard. The free tier is enough to follow this through.
-
Create an MCP Gateway and select your ClickUp tools
In the dashboard, create a gateway and pick the ClickUp tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.
-
Copy your gateway URL
Every client below needs it.
https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>
Connect the gateway to Claude Code
-
Add the gateway as a remote HTTP MCP server
claude mcp add arcade --transport http "<YOUR_ARCADE_GATEWAY_URL>"
-
Verify it was added
claude mcp get arcade claude mcp list
-
Try it out
Open Claude Code in your project and ask it to use one of your ClickUp tools.
Full Claude Code guide in the docs steps verified 2026-08-13
Try these ClickUp prompts
Claude Code can now act on your ClickUp account. Click a prompt to copy it.
Use per-user authorization and scoped permissions to control which ClickUp workspaces and task changes an agent can access. Pair it with Contextual Access policies so an agent can find project status without being allowed to create or reassign tasks.
