What an agent can do in ClickUp
Manage ClickUp work: create and update tasks, search tasks and docs, track time, and post comments and chat messages. It has no delete tools.
Jobs on Rush that use ClickUp
- Which Client Deliverables Are Stuck in Review? A Video Production Studio's Monday List From ClickUp
- What's Still Open Before the Wedding? A Planner App Drafts Each Couple's Weekly Checklist From the Planner's ClickUp
- Report Retainer Hours Used per Client From ClickUp Time Tracking
- Which Clients' Month-End Close Is Behind? A Bookkeeping Firm's ClickUp Report
How ClickUp connects
ClickUp is a remote MCP server, published by ClickUp, at https://mcp.clickup.com/mcp. Connecting it signs in through the MCP OAuth flow on ClickUp's side.
From ClickUp: ClickUp's MCP documentation.
Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.
After that, a run that names clickup in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.
POST https://api.phoenix.so/me/connections
{
"type": "mcp",
"name": "ClickUp",
"url": "https://mcp.clickup.com/mcp"
}Whose ClickUp account the agent uses
Your ClickUp connection is personal: it belongs to the person who signed in. A run started in the console uses that person's ClickUp, and a run started with an API key uses the ClickUp of the member who created the key.
To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own ClickUp, and that agent's runs use their account and nothing else: never yours, never another user's.
More Project Management integrations
Frequently asked questions
How do I connect ClickUp to Rush?
Open Settings → Connections in the console and connect ClickUp, or send POST /me/connections with {"type":"mcp","name":"ClickUp","url":"https://mcp.clickup.com/mcp"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.
Does every run get my ClickUp account?
No. A run gets your ClickUp connection only when it names it in connections ("connections": ["clickup"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.
What can an agent do in ClickUp?
Manage ClickUp work: create and update tasks, search tasks and docs, track time, and post comments and chat messages. It has no delete tools. 4 published jobs use it; this page lists them.
Can my app's users connect their own ClickUp?
Yes. Make each user an agent from your template, and they sign in to their own ClickUp through the link POST /o/{org}/agents/{agent}/connections returns. That agent's runs use their account alone.
Keep reading
- AI agents for product and project management teams: every job and app for them
- How connections work: sign in once, then every run that names a connection gets it
- Start your first run from the developer API quickstart
- Pricing: one price per member, hours shared by the team
- How Rush compares with other cloud agents
- Every app and MCP server Rush connects to