ClickUp MCP Server – Tasks and Workspace Automation
ClickUp's official hosted MCP server gives AI assistants permission-aware access to ClickUp Workspace data and actions. Use it to search work, create and update tasks, collaborate in comments and chat, track time, and produce reports from live workspace context.
Overview
ClickUp's official MCP server connects compatible AI assistants to a user's
ClickUp Workspace through a hosted remote service. After OAuth authorization,
the agent can work with current tasks, Lists, Folders, Docs, comments, and other
permitted ClickUp data instead of relying only on information pasted manually
into a prompt.
What the MCP server enables
ClickUp documents a broad tool set that covers workspace search, task
management, collaboration, reporting, and time tracking. Depending on the
signed-in user's permissions, an AI agent can:
- Search across tasks, Lists, Folders, Docs, and comments.
- Create, retrieve, update, and delete tasks and subtasks.
- Create and update tasks in bulk.
- Set custom fields, tags, dependencies, and task links.
- Upload task attachments and retrieve or post comments.
- Summarize comment threads and extract action items.
- Start and stop timers, log historical time entries, and retrieve time data.
- Build status updates, release notes, portfolio summaries, and other reports.
- Combine multiple tools in one workflow to route and enrich work.
When to use it
Use ClickUp MCP when an AI workflow needs live workspace context or must perform
an authorized productivity action. Typical examples include creating a task
from a bug report, finding overdue work, assigning tasks, updating priorities
and due dates, summarizing a project, generating an executive status update,
logging time, or posting a progress comment from an AI assistant.
Connection and authentication
The official endpoint is https://mcp.clickup.com/mcp over remote HTTP.
ClickUp supports OAuth 2.1 with PKCE. API keys and personal access tokens are
not supported for MCP authentication.
Clients that cannot connect directly to a remote MCP server can use the
documented mcp-remote stdio bridge. ClickUp maintains an allowlist of vetted
MCP client redirect URIs, and unsupported custom clients may need to request
review before their OAuth redirect URI is accepted.
Key considerations
ClickUp MCP is currently in public beta and is available on all ClickUp plans.
Every action is limited by the authenticated user's existing Workspace
permissions. Without the Everything AI add-on, documented rolling 24-hour
limits are 50 calls on Free Forever and 300 calls on Unlimited and above;
workspaces with Everything AI use ClickUp Public API plan-based rate limits.
Rate limits and feature restrictions may change. Require human confirmation for
destructive actions such as deleting tasks, and connect only trusted MCP clients.
Supported Transports
streamable_http
URL: https://mcp.clickup.com/mcp
stdio
Command: npx
Args:
-ymcp-remotehttps://mcp.clickup.com/mcp
Frequently Asked Questions
- When should an AI agent use the ClickUp MCP server?
- Use it when a workflow needs live ClickUp Workspace context or authorized actions, such as creating and updating tasks, searching work, summarizing projects, collaborating in comments, tracking time, or generating reports.
- What does the ClickUp MCP server add to an AI agent's capabilities?
- It gives the agent structured, permission-aware access to current ClickUp data and actions, allowing it to search, retrieve, create, update, and coordinate work instead of relying only on static model knowledge or manually pasted workspace content.
- What can an AI agent access or manage through ClickUp MCP?
- Depending on user permissions, the agent can work with tasks, subtasks, Lists, Folders, Docs, comments, chat, tags, custom fields, attachments, dependencies, task links, time entries, timers, and workspace search results.
- How is authentication configured for the ClickUp MCP server?
- ClickUp MCP uses OAuth 2.1 with PKCE. API keys and personal access tokens are not supported. The client opens a browser authorization flow and the resulting access remains limited by the signed-in user's Workspace permissions.
- Which transport should be used for the ClickUp MCP server?
- Use the hosted remote HTTP endpoint at https://mcp.clickup.com/mcp for clients that support remote MCP directly. Use the documented mcp-remote stdio bridge only when the client requires a locally launched process.