Ticketing
ClickUp MCP connector
The ClickUp connector brings your ClickUp workspaces, spaces, folders, lists and tasks to Claude, ChatGPT, Cursor and any MCP client, so each person can find, update and organize their own ClickUp work by asking in plain language.
-
How it connects. OAuth or API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect ClickUp to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect ClickUp once
-
Open Connections, choose Add connection, and pick ClickUp.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in ClickUp. ClickUp's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect ClickUp to 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.
Connect ClickUp to 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 today. The plugin directory lives at chatgpt.com/plugins.
Connect ClickUp to 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.
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.
Use cases
What teams do with ClickUp through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
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.
See it in Elaichi
What connecting ClickUp gets you
6 screens from the product, each doing one job for your ClickUp account.
The agent
Ask about ClickUp tasks, get real answers.
Plain language questions run against live ClickUp spaces, folders and tasks.
- tasks
- lists
- folders
- spaces
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 or Cursor
MCP clients
Claude, ChatGPT and Cursor reach ClickUp.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
174 ClickUp tools ready without custom code.
Teams, groups, spaces, folders and lists, each with its own methods.
- List all ClickUp teams
- List all ClickUp groups
- Create a ClickUp group
- Delete a ClickUp group by ID
Toolboxes
Every team gets its own ClickUp toolbox.
Curate one toolbox per team so each sees only relevant ClickUp tools.
- Engineering
- Support
- Product
- Marketing
Shared connections
Share a ClickUp account, never the credential.
See who connected each ClickUp account and which teams and members use it.
- Engineering
- Support EMEA
- Product
- Marketing
Audit log
Every ClickUp call is written down.
When, who, what happened, type and resource for each ClickUp request.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, ClickUp work gets done.
Fetch tasks, group them, draft a digest, approve, then post back to ClickUp.
ClickUp digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
ClickUp
Queued
Collections and dashboards
ClickUp health numbers arrive on schedule.
Four metrics, 14 days of tasks created and a per team breakdown, computed directly.
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 blocking the deletion of spaces, folders or lists. A blocked action is never shown to Claude, ChatGPT, Cursor or any other client, so no prompt can reach it.
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 and every other client at the same time.
Put ClickUp in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.