ClickUp MCP connector
The ClickUp connector brings your ClickUp workspaces, spaces, folders, lists and tasks to Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so each person can find, update and organize their own ClickUp work by asking in plain language.
- OAuth or API key
- Free 14-day trial
- No credit card
Which tasks in the Engineering space are overdue this week?
Working in ClickUp with Elaichi
-
List all ClickUp teams
-
List all ClickUp groups
-
List all ClickUp spaces
How to connect ClickUp to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
ClickUp MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
ClickUp MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
ClickUp MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
ClickUp MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
ClickUp MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect ClickUp to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with ClickUp through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in ClickUp is logged.
-
Operations
Catch a task up after a meeting
Say what was decided and the ClickUp task gets its status, assignee, due date and description updated to match, without opening the app.
-
Support
Find every open task for one customer
Ask which ClickUp tasks mention a customer or a problem and get the list back with current status, so the desk knows what is already in progress.
-
Marketing
Set up a campaign in one ask
Describe the new campaign and ClickUp gets a folder and the lists inside it created and named the way the team already works.
-
Product
Review what is overdue this week
Pull the ClickUp tasks past their due date across a space, see who owns each one, and push dates or priorities in a single conversation.
-
Engineering
Reorganize a space before a new quarter
Rename folders, retire lists that are finished and add the ones the next quarter needs, then check the ClickUp space reads the way it should.
-
People
Keep team groups current
Create a ClickUp group for a new squad, add or remove members as people change roles, and see at a glance which groups exist across the workspace.
Try asking
- “Which tasks in the Engineering space are overdue this week?”
- “Create a folder for Q3 onboarding in the Sales space.”
- “Summarize task activity across all ClickUp spaces since Monday.”
What connecting ClickUp gets you
6 screens from Elaichi, each doing one job for your ClickUp account.
Ask Elaichi to work across your apps.
Which tasks in the Engineering space are overdue this week?
Create a folder for Q3 onboarding in the Sales space.
Summarize task activity across all ClickUp spaces since Monday.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about ClickUp tasks, get real answers.
Plain language questions run against live ClickUp spaces, folders and tasks.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach ClickUp.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
174 ClickUp tools ready without custom code.
Teams, groups, spaces, folders and lists, each with its own methods.
Toolboxes
Every team gets its own ClickUp toolbox.
Curate one toolbox per team so each sees only relevant ClickUp tools.
Shared connections
Share a ClickUp account, never the credential.
See who connected each ClickUp account and which teams and members use it.
Audit log
Every ClickUp call is written down.
When, who, what happened, type and resource for each ClickUp request.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
ClickUp digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch tasks
ClickUp
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
ClickUp
Queued
Automations
A schedule fires, ClickUp work gets done.
Fetch tasks, group them, draft a digest, approve, then post back to ClickUp.
ClickUp health
Refreshed 4 minutes ago · every 15 minutes · from the tasks collection
Tasks
1,284 ↓ 12%
Lists
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Tasks created
Last 14 days
By team
Share of activity
Engineering 34%
Support EMEA 27%
Product 21%
Marketing 18%
Collections and dashboards
ClickUp health numbers arrive on schedule.
Four metrics, 14 days of tasks created and a per team breakdown, computed directly.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for ClickUp
All three can connect ClickUp to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over ClickUp tools | Allow or restrict single ClickUp tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per ClickUp call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
ClickUp tools for your AI agents
174 tools are ready to call through Elaichi's MCP endpoint the moment you connect ClickUp, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect ClickUp to Claude?
Connect ClickUp in Elaichi first: you either sign in through ClickUp's own login window or paste an API key from your ClickUp settings, and there is no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude asks you to sign in to Elaichi once, and ClickUp is ready to use in your chats.
Does ClickUp work with ChatGPT and Cursor as well as Claude?
Yes. Once ClickUp is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect ClickUp once and every client you use picks it up.
What can an AI agent actually do with my ClickUp data?
With ClickUp connected, an agent can look up tasks, tell you their status and owner, and update a task's details when you describe what changed. It can also create, rename and remove spaces, folders and lists, and manage the groups that organize your people in ClickUp. Because ClickUp has a lot of possible actions, short concrete asks like "mark the onboarding task done" work better than long sentences.
Does connecting ClickUp give the AI access to my whole workspace?
No. Every ClickUp call runs as the person who signed in, so the agent sees only the spaces, folders, lists and tasks that person can already open in ClickUp. Elaichi can narrow that further with roles and restrictions, but it can never give the AI more than the person already has.
Can I stop an agent from deleting or changing things in ClickUp?
Yes. Restrictions in Elaichi work per action, so you can allow reading and updating ClickUp tasks while restricting the deletion of spaces, folders or lists. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.
What happens to a ClickUp connection when someone leaves?
Offboarding that person in Elaichi ends their ClickUp access through every client at once, and the audit log keeps the record of what they did. If they shared a ClickUp connection, it keeps working for everyone else on the team. Disconnecting ClickUp once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the ClickUp MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. ClickUp is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for ClickUp?
Yes. Both let Claude, ChatGPT or Cursor use ClickUp. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every ClickUp call.
How is Elaichi different from Composio for ClickUp?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to ClickUp: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put ClickUp in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot