ClickUp MCP
ClickUp MCP lets agents search and manage tasks, lists, folders, docs, comments, chat, and time-tracking workflows in a ClickUp workspace.
Verdict
Common use cases
- Generate sprint summaries from active tasks
- Triage overdue tasks and reassign owners
- Draft client status updates from task progress
- Create subtasks from meeting notes
- Pull task dependencies for planning discussions
Integration
- Vendor
- ClickUp MCP
- Category
- other
- Auth
- OAUTH2
- Composio slug
clickup_mcp
Tools
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > Add MCP Server. 2. Select ClickUp MCP from the directory and click Connect. 3. You'll be redirected to ClickUp's OAuth consent screen — log in with your ClickUp account. 4. Grant the requested scopes: read access to workspaces, lists, and tasks; write access to create and update tasks. 5. After authorizing, you'll return to Switchy and see a green Connected badge next to ClickUp MCP. 6. Open any Project in Switchy and type '@ClickUp list my open tasks' to test the connection. 7. If the MCP returns your tasks, the integration is live and ready to use in any conversation.
What teammates see: by default, memories from ClickUp MCP are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Sprint Summary
@ClickUp list all tasks in the current sprint, then write a two-paragraph summary of what's done, in progress, and blocked.
Overdue Task Triage
@ClickUp show me all overdue tasks, then recommend which ones to reassign or push to next sprint based on priority.
Client Update Draft
@ClickUp find all tasks tagged 'ClientX' updated this week, then draft a status email highlighting completed work and next steps.
Meeting Action Items
@ClickUp create tasks from these meeting notes: assign the API integration to Jordan by Friday, the design review to Sam by Tuesday, and the QA pass to Alex by next Monday.
Dependency Check
@ClickUp list all tasks blocking the Q1 launch milestone, then identify which dependencies are at risk of missing their deadlines.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@ClickUp show me all tasks assigned to me that are due this week, grouped by priority
Based on your ClickUp workspace, here are your tasks due this week: **Urgent (3 tasks)** - Complete Q1 budget review (due Wed) - Ship v2.1 hotfix (due Thu) - Finalize vendor contracts (due Fri) **High (5 tasks)** - Draft marketing brief for launch - Review design mockups - Update project timeline - Schedule team retrospective - Close out support tickets **Normal (2 tasks)** - Update documentation - Prepare monthly report This reflects your current assignments across 3 active spaces. Tasks marked 'Urgent' have been flagged by workspace owners.
This read-heavy query demonstrates the MCP's ability to filter and organize task data by assignee, date range, and priority. Requires OAuth scope covering task read access across all spaces where you're a member. Results depend on how your team structures priorities in ClickUp.
@ClickUp create a new task in the 'Website Redesign' list: 'Audit accessibility compliance' with high priority, due next Friday, and assign it to Sarah
Task created successfully in the Website Redesign list: **Audit accessibility compliance** - Priority: High - Due date: Friday, January 17, 2025 - Assignee: Sarah Chen - Status: To Do - Task ID: #8472 The task is now visible to all members of the 'Website Redesign' space. Sarah will receive a notification about the assignment. You can view or edit this task at: [clickup.com/t/8472]
This write action shows task creation with metadata assignment. Requires OAuth scope for task creation and user assignment in the target space. The MCP must resolve 'Sarah' to a valid workspace member — ambiguous names may fail. Side-effect: immediate notification sent to assignee.
@ClickUp review all comments on tasks in the 'Product Launch' folder from the last 3 days and summarize the main blockers the team is discussing
I reviewed 47 comments across 12 tasks in the Product Launch folder. Here are the recurring blockers: **API integration delays (mentioned in 6 tasks)**: The third-party payment API is returning inconsistent responses in staging. Team is waiting on vendor support ticket resolution. **Design asset dependencies (4 tasks)**: Marketing needs final logo variations and social media templates before scheduling campaigns. Design team estimates delivery by Wednesday. **QA resource constraints (3 tasks)**: Only one QA engineer available this week due to PTO. Several features are code-complete but awaiting test coverage. Most urgent: The API blocker affects 3 critical-path tasks due before launch date.
This synthesis example pairs the MCP's comment-fetching capability with AI reasoning to extract patterns from unstructured discussion. Requires read access to comments and tasks in the specified folder. Accuracy depends on how explicitly team members document blockers — vague comments may be missed.
Use-case deep-dives
ClickUp MCP works when your team lives in ClickUp already
A 6-person engineering team runs two-week sprints entirely in ClickUp — tasks, docs, time tracking, everything. They want an AI agent that can pull sprint velocity, flag overdue subtasks, and draft retrospective summaries without leaving Switchy. ClickUp MCP is the right call here because OAuth2 means each team member authenticates once and the agent respects their workspace permissions. The trade-off: if your team uses ClickUp lightly (just task lists, no custom fields or automations), you're adding auth overhead for features you won't use. This MCP pays off when ClickUp is your single source of truth and you need the agent to read or write across multiple views — lists, boards, timelines — in one conversation.
When ClickUp MCP replaces manual status reporting
A 3-person agency manages 12 client projects in ClickUp, each with its own Space and custom statuses. Every Friday, they compile a status email: what shipped, what's blocked, what's next. ClickUp MCP lets the agent query all active tasks by client, filter by status, and draft the update in 90 seconds. The win is speed and consistency — no one forgets to check a Space. The boundary: if your clients demand screenshots or visual proof-of-progress, the MCP won't generate those; you'll still need manual steps. This scenario works best when your status updates are text-heavy and your ClickUp structure is predictable (same custom fields across projects).
ClickUp MCP for support teams using ClickUp as a ticketing system
A 5-person support team uses ClickUp instead of Zendesk — each customer issue is a task with priority tags and assignee rules. They want an agent that reads new tickets each morning, suggests priority based on keywords, and routes to the right person. ClickUp MCP handles this if your triage logic is simple (keyword matching, tag-based rules). The limit: if you need sentiment analysis or integration with external CRMs, the MCP alone won't close the loop. This works when ClickUp is already your ticket system and you're automating the first 10 minutes of each support shift — not replacing a full help-desk platform.
Frequently asked
What does the ClickUp MCP let me do in Switchy?
The ClickUp MCP connects your team's ClickUp workspace to Switchy's AI agents, letting them read task details, update statuses, create subtasks, and query project data without leaving the conversation. Your agents can pull context from ClickUp to answer questions like "what's blocking the Q2 launch" or log action items directly into the right list.
Do I need ClickUp admin permissions to connect this MCP?
You need workspace-level OAuth permissions to authorize the connection, which typically means you're an admin or have been granted API access by one. ClickUp's OAuth flow will show exactly which scopes the MCP requests — usually read/write on tasks, lists, and comments. If you're a guest user in ClickUp, you won't be able to complete the setup.
Can the ClickUp MCP create custom fields or modify workspace settings?
No. The MCP focuses on task-level operations — creating, updating, and reading tasks, subtasks, comments, and attachments. It won't touch workspace structure like custom fields, statuses, or team permissions. If you need to change those, do it in ClickUp directly or use their full REST API outside Switchy.
Why use the ClickUp MCP instead of just opening ClickUp in another tab?
The MCP embeds ClickUp data into your team's AI conversations, so agents can reference task context, update statuses, and log decisions without context-switching. You're not replacing ClickUp — you're giving your AI the ability to act on ClickUp data in the same thread where you're making decisions, which cuts down on manual copy-paste and forgotten follow-ups.
Who on my team should connect the ClickUp MCP to Switchy?
Whoever owns your ClickUp workspace and has OAuth authorization rights. Once connected, all Switchy team members can invoke the MCP in shared chats, but the connection itself runs under one person's ClickUp credentials. If that person leaves or revokes access, you'll need to reconnect it under a service account or another admin.