The ClickUp MCP Integration server allows Large Language Models to interact with your ClickUp workspace, providing access to tasks, documents, custom fields, and more through the Model Context Protocol (MCP).
https://app.clickup.com/{workspace_id}/home
cline_mcp_settings.json
inside the mcpServers
key:"clickup": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"CLICKUP_API_TOKEN",
"-e",
"CLICKUP_WORKSPACE_ID",
"your-docker-repository"
],
"env": {
"CLICKUP_API_TOKEN": "your-api-token",
"CLICKUP_WORKSPACE_ID": "your-workspace-id"
}
}
C:\Users\YourUsername\AppData\Roaming\Claude\claude_desktop_config.json
~/Library/Application\ Support/Claude/claude_desktop_config.json
claude_desktop_config.json
inside the mcpServers
key:"clickup": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"CLICKUP_API_TOKEN",
"-e",
"CLICKUP_WORKSPACE_ID",
"your-docker-repository"
],
"env": {
"CLICKUP_API_TOKEN": "your-api-token",
"CLICKUP_WORKSPACE_ID": "your-workspace-id"
}
}
The MCP server provides several tools for managing ClickUp tasks:
Creating tasks: Create new tasks in your workspace
clickup_create_task
Retrieving tasks: Get task information using ID or custom ID
clickup_get_task
clickup_get_task_by_custom_id
Updating tasks: Modify existing tasks
clickup_update_task
clickup_update_task_by_custom_id
Listing tasks: Get all tasks from a specific list with filtering options
get_list_tasks
For ClickUp documents, you can:
Search documents
clickup_search_docs
Create new documents
clickup_create_doc
Manage document pages
clickup_get_doc_pages
clickup_get_page
clickup_create_page
clickup_edit_page
Custom fields can be managed with:
Retrieving custom fields
clickup_get_list_custom_fields
Setting custom field values
clickup_set_custom_field_value
clickup_set_custom_field_value_by_custom_id
Manage your ClickUp workspace structure with:
Viewing workspace hierarchy
get_spaces
get_folders
get_lists
Creating lists
create_list
get_list_assignees
If you encounter issues with the MCP server:
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"cursor-rules-mcp": {
"command": "npx",
"args": [
"-y",
"cursor-rules-mcp"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.