How to use ClickUp with VS Code
You want ClickUp inside VS Code so it can triage overdue work, turn project notes into tasks, review blocked tasks and assign follow-up, and coordinate task updates — without you copy-pasting between tabs. Here is the whole setup, once.
Create your ClickUp gateway
The gateway is the thing VS 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 VS Code
-
Add the server
VS Code 1.107.0 or higher. Command Palette → MCP: Add Server… → choose HTTP, paste your gateway URL, and name it something like mcp-arcade.
-
Start it and authenticate
Click Start next to the server in mcp.json or under Extensions → MCP Servers - Installed, then approve the Arcade sign-in and consent screens.
-
Try it out
Open the chat pane, switch to Agent mode, and ask it to use one of your ClickUp tools.
Full VS Code guide in the docs steps verified 2026-08-13
Try these ClickUp prompts
VS 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.