emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Complete ClickUp API (173 v2+v3 operations) in 4 tools, ~700 tokens. Tasks, time, Chat, Docs.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install ClickUp (full API). Follow https://mcp.popnx.com/i/kelvincampelo-clickup-full-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 21, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
You need a ClickUp (full API) key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server ClickUp (full API) for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "clickup-full": { "command": "npx", "args": [ "-y", "clickup-full-mcp" ], "env": { "CLICKUP_API_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For CLICKUP_API_TOKEN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the ClickUp (full API) tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
SettingsDeveloperEdit Config
{
"mcpServers": {
"clickup-full": {
"command": "npx",
"args": [
"-y",
"clickup-full-mcp"
],
"env": {
"CLICKUP_API_TOKEN": "your-value"
}
}
}
}Paste the key only into the app’s field, never into a chat or to anyone
Use ClickUp (full API) and tell me what you can do for me, then show me one thing✓ If Claude says it is using ClickUp (full API) or shows a ClickUp (full API) tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
CLICKUP_WORKSPACE_ID Default Workspace (team) ID, auto-filled into team_id / workspace_idCLICKUP_TOOL_MODE meta (default: 4 tools for the whole API) or full (one tool per endpoint) · default metaCLICKUP_TOOLSETS Comma-separated toolsets to expose, e.g. tasks,comments,time_trackingCLICKUP_READ_ONLY true to expose only read (GET) operations · default falseCLICKUP_RESPONSE_FORMAT compact (default: minified, null/empty fields removed), json (every field) or pretty (indented) · default compactDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect ClickUp (full API) yet
ClickUp (full API) runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect ClickUp (full API)
B · Others in Chat & email that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
You need a ClickUp (full API) key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server ClickUp (full API) for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user clickup-full --env CLICKUP_API_TOKEN=your-value -- npx -y clickup-full-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For CLICKUP_API_TOKEN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the ClickUp (full API) tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user clickup-full --env CLICKUP_API_TOKEN=your-value -- npx -y clickup-full-mcpReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see ClickUp (full API) listed as connected
Use ClickUp (full API) and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using ClickUp (full API) or shows a ClickUp (full API) tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
CLICKUP_WORKSPACE_ID Default Workspace (team) ID, auto-filled into team_id / workspace_idCLICKUP_TOOL_MODE meta (default: 4 tools for the whole API) or full (one tool per endpoint) · default metaCLICKUP_TOOLSETS Comma-separated toolsets to expose, e.g. tasks,comments,time_trackingCLICKUP_READ_ONLY true to expose only read (GET) operations · default falseCLICKUP_RESPONSE_FORMAT compact (default: minified, null/empty fields removed), json (every field) or pretty (indented) · default compactDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a ClickUp (full API) key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server ClickUp (full API) for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "clickup-full": { "command": "npx", "args": [ "-y", "clickup-full-mcp" ], "env": { "CLICKUP_API_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For CLICKUP_API_TOKEN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the ClickUp (full API) tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the ClickUp (full API) settings, CLICKUP_API_TOKEN is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use ClickUp (full API) and tell me what you can do for me, then show me one thing✓ If Cursor says it is using ClickUp (full API) or shows a ClickUp (full API) tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
CLICKUP_WORKSPACE_ID Default Workspace (team) ID, auto-filled into team_id / workspace_idCLICKUP_TOOL_MODE meta (default: 4 tools for the whole API) or full (one tool per endpoint) · default metaCLICKUP_TOOLSETS Comma-separated toolsets to expose, e.g. tasks,comments,time_trackingCLICKUP_READ_ONLY true to expose only read (GET) operations · default falseCLICKUP_RESPONSE_FORMAT compact (default: minified, null/empty fields removed), json (every field) or pretty (indented) · default compactDescriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a ClickUp (full API) key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server ClickUp (full API) for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "clickup-full": { "type": "stdio", "command": "npx", "args": [ "-y", "clickup-full-mcp" ], "env": { "CLICKUP_API_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For CLICKUP_API_TOKEN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the ClickUp (full API) tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the ClickUp (full API) settings, CLICKUP_API_TOKEN is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use ClickUp (full API) and tell me what you can do for me, then show me one thing✓ If VS Code says it is using ClickUp (full API) or shows a ClickUp (full API) tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
CLICKUP_WORKSPACE_ID Default Workspace (team) ID, auto-filled into team_id / workspace_idCLICKUP_TOOL_MODE meta (default: 4 tools for the whole API) or full (one tool per endpoint) · default metaCLICKUP_TOOLSETS Comma-separated toolsets to expose, e.g. tasks,comments,time_trackingCLICKUP_READ_ONLY true to expose only read (GET) operations · default falseCLICKUP_RESPONSE_FORMAT compact (default: minified, null/empty fields removed), json (every field) or pretty (indented) · default compactDescriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user clickup-full --env CLICKUP_API_TOKEN=your-value -- npx -y clickup-full-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"clickup-full": {
"command": "npx",
"args": [
"-y",
"clickup-full-mcp"
],
"env": {
"CLICKUP_API_TOKEN": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"clickup-full": {
"command": "npx",
"args": [
"-y",
"clickup-full-mcp"
],
"env": {
"CLICKUP_API_TOKEN": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"clickup-full": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"clickup-full-mcp"
],
"env": {
"CLICKUP_API_TOKEN": "your-value"
}
}
}
}CLICKUP_API_TOKEN secret required envCLICKUP_WORKSPACE_ID envCLICKUP_TOOL_MODE envCLICKUP_TOOLSETS envCLICKUP_READ_ONLY envCLICKUP_RESPONSE_FORMAT envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: clickup-full-mcpBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 21, 2026
The registry name was verified with the GitHub account KelvinCampelo, which owns the repo
Code last changed today
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked yet
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/kelvincampelo-clickup-full-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: CLICKUP_API_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed today, and the latest version (2.1.2) reached the registry today.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Build and fix Discord bots from a chat. Kite hosts them 24/7, with no code to deploy.
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.
CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.
| This one ClickUp (full API) | emailmd | Kite Discord Bot Builder | e2a — email for AI agents | Infobip MCP | kernelCAD | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | Yes | No |
| Basic checks | 3/3 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | MIT | AGPL-3.0 | Apache-2.0 | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The entire ClickUp API in 4 tools. A local Model Context Protocol server that lets Claude, Cursor, VS Code Copilot and any other MCP client use all 173 ClickUp API operations (v2 + v3) for about 700 tokens of context instead of ~55,000.
Tasks, subtasks, lists, folders, spaces, comments, checklists, custom fields, tags, dependencies, time tracking, goals, guests, users, user groups, templates, views, webhooks, workspaces and OAuth, plus the v3 Chat, Docs, Attachments, ACLs and Audit Logs APIs. Every tool is generated from ClickUp's official OpenAPI specs, so nothing is hand-picked or missing.
[!NOTE]
Community project, not affiliated with or endorsed by ClickUp.
Most API-wrapping MCP servers register one tool per endpoint. For ClickUp that means 173 tool schemas loaded into the model's context on every request, before you've typed anything. That's slower, costs more, crowds out your actual conversation, and makes it harder for the model to pick the right tool. Some clients also cap how many tools a server may register.
By default this server exposes just 4 tools that reach the whole API:
| Tool | What it does |
|---|---|
clickup_search_operations | Finds operations by keyword: "create task", "log time", "send chat message"… |
clickup_describe_operation | Returns one operation's full description and JSON input schema, only when it's needed. |
clickup_call_operation | Calls any of the 173 operations by name. |
clickup_request | Raw escape hatch for any /api/v2 or /api/v3 path. |
Measured tools/list size (v1.0.0, tokens ≈ characters ÷ 4):
| Mode | Tools | Schema size | Context cost |
|---|---|---|---|
full (CLICKUP_TOOL_MODE=full) | 174 | 214 KB | ~55,000 tokens |
full + CLICKUP_TOOLSETS=tasks,comments,time_tracking | 42 | 61 KB | ~15,600 tokens |
| `meta` (default) | 4 | 2.6 KB | ~700 tokens (−98.8%) |
A typical meta-mode exchange costs one or two extra small calls, and the model only ever loads the schemas it actually uses:
// 1. Find the operation
clickup_search_operations { "query": "create task" } // → [{ "name": "create_task", "http": "POST /api/v2/list/{list_id}/task", … }, …]
// 2. (optional) Read its schema clickup_describe_operation { "name": "create_task" }
// 3. Call it, with the same arguments as the full-mode tool clickup_call_operation { "name": "create_task", "arguments": { "list_id": "901", "body": { "name": "Ship MCP" } } }
Search understands everyday wording: "log time" finds create_time_entry, "find tasks" finds get_tasks, "post message" finds send_chat_message.
Prefer direct tools? Set CLICKUP_TOOL_MODE=full to register one tool per endpoint, and use CLICKUP_TOOLSETS to trim it to the areas you use. Both modes respect CLICKUP_TOOLSETS, CLICKUP_READ_ONLY and CLICKUP_DISABLED_TOOLS.
The tool list is only half of the cost: every ClickUp response also lands in the context, and ClickUp responses are full of nulls and empty arrays. By default the server returns minified JSON with null and empty fields removed (false, 0, array positions and empty top-level lists like {"tasks":[]} are kept). Measured on the example responses in ClickUp's own spec, compared with indented JSON:
| Response | Indented JSON | Compact (default) | Saved |
|---|---|---|---|
get_tasks (list of tasks) | 10,697 chars | 5,609 chars | 48% |
get_task | 6,675 chars | 4,262 chars | 36% |
get_time_entries_within_date_range | 1,441 chars | 870 chars | 40% |
Need every field exactly as ClickUp sent it? Set CLICKUP_RESPONSE_FORMAT=json (minified, nothing removed) or pretty (indented).
delete_space.statuses[]=a, group_ids=a&group_ids=b, JSON custom_fields), and upload field names match the live API.Retry-After / X-RateLimit-Reset, timeouts, response truncation, file uploads, OAuth tokens, and MCP tool annotations (read-only / destructive hints).ECODE.Requirements: Node.js 20+.
pk_). OAuth access tokens also work. Optionally note your Workspace ID too (how to find it), so the model doesn't have to look it up. npx -y clickup-full-mcp
No install step: npx fetches the npm package on first run. The server is also listed in the official MCP Registry as io.github.KelvinCampelo/clickup-full-mcp.
bug in _Inbox_ to _Triage_ and comment 'moved by triage bot'."86abc123 for today with the note 'code review'."[!TIP]
For a first run, add
CLICKUP_READ_ONLY=true. Only GET endpoints are exposed, so nothing can be changed.
git clone https://github.com/KelvinCampelo/clickup-full-mcp.git
cd clickup-full-mcp npm install # also builds dist/ npm test # optional: end-to-end tests against a mock ClickUp
Then use "command": "node" and "args": ["/ABSOLUTE/PATH/clickup-full-mcp/dist/index.js"] in the client configs below.
The server starts in 4-tool meta mode. Add "CLICKUP_TOOL_MODE": "full" to env if you'd rather have one tool per endpoint. CLICKUP_WORKSPACE_ID is optional but saves the model a lookup on every call (how to find it).
Claude Desktop
Edit claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": { "clickup": { "command": "npx", "args": ["-y", "clickup-full-mcp"], "env": { "CLICKUP_API_TOKEN": "pk_xxx", "CLICKUP_WORKSPACE_ID": "1234567" } } } }
Claude Code
claude mcp add clickup --scope user \
-e CLICKUP_API_TOKEN=pk_xxx -e CLICKUP_WORKSPACE_ID=1234567 \ -- npx -y clickup-full-mcp
Cursor
~/.cursor/mcp.json (global) or .cursor/mcp.json (project):
{
"mcpServers": { "clickup": { "command": "npx", "args": ["-y", "clickup-full-mcp"], "env": { "CLICKUP_API_TOKEN": "pk_xxx", "CLICKUP_WORKSPACE_ID": "1234567" } } } }
VS Code (GitHub Copilot)
.vscode/mcp.json. VS Code prompts for the token and stores it securely:
{
"inputs": [{ "type": "promptString", "id": "clickup-token", "description": "ClickUp API token", "password": true }], "servers": { "clickup": { "type": "stdio", "command": "npx", "args": ["-y", "clickup-full-mcp"], "env": { "CLICKUP_API_TOKEN": "${input:clickup-token}" } } } }
Any other MCP client or agent framework
Run npx -y clickup-full-mcp (or node dist/index.js from a clone) as a stdio MCP server with the environment variables below. This works with any client or agent SDK that can launch local stdio servers.
Prefer containers? A multi-arch image (amd64/arm64) is published to GHCR with every release:
docker run -i --rm -e CLICKUP_API_TOKEN=pk_xxx ghcr.io/kelvincampelo/clickup-full-mcp
In a client config, use "command": "docker" and "args": ["run", "-i", "--rm", "-e", "CLICKUP_API_TOKEN", "ghcr.io/kelvincampelo/clickup-full-mcp"], with the token in env.
Each row is one operation. In meta mode (the default), pass the arguments to clickup_call_operation as { "name": " ", "arguments": { … } }; in full mode, call the tool directly. The examples assume CLICKUP_WORKSPACE_ID is set, so team_id / workspace_id can be left out. Dates are Unix timestamps in milliseconds. Every tool's full argument list is in the tool reference.
| Goal | Tool | Arguments |
|---|