home / mcp / clickup mcp server mcp server
Fork of ClickUp MCP Server - Integrate ClickUp task management with AI through Model Context Protocol
Configuration
View docs{
"mcpServers": {
"windalfin-clickup-mcp-server": {
"command": "npx",
"args": [
"-y",
"@taazkareem/clickup-mcp-server@latest",
"--env",
"CLICKUP_API_KEY=your_api_key_here",
"--env",
"CLICKUP_TEAM_ID=your_team_id_here"
],
"env": {
"CLICKUP_API_KEY": "your_api_key_here",
"CLICKUP_TEAM_ID": "your_team_id_here"
}
}
}
}You can run a dedicated MCP server that lets AI agents interact with ClickUp tasks, spaces, lists, and folders through a standardized protocol. This server streamlines task management by enabling natural-language interactions and programmatic controls from your AI applications.
You operate the MCP server from your MCP client by provisioning credentials and pointing the client to the server you run. After you configure your ClickUp credentials, you can use natural language prompts to create, update, move, or query tasks and workspace components. The server supports task-level operations, bulk actions, list and folder management, and workspace navigation. It also provides name- or ID-based lookups with case-insensitive matching and Markdown formatting in responses.
Prerequisites: ensure Node.js is installed on your system. You can verify by running node -v and npm -v in your terminal. If Node.js is not installed, install it from the official Node.js website for your platform.
Install and run the MCP server using the following command in your MCP client settings or terminal, replacing credentials with your actual values.
npx -y @taazkareem/clickup-mcp-server@latest \
--env CLICKUP_API_KEY=your_api_key_here \
--env CLICKUP_TEAM_ID=your_team_id_hereConfiguration security: protect your API key and team ID. Do not expose credentials in client-side apps. Use environment isolation where possible and rotate API keys regularly.
Troubleshooting tips: if you encounter authentication errors, confirm that the API key is active and that the Team ID matches your ClickUp workspace. If you receive permission issues, verify that your ClickUp API key has the necessary scopes for the tasks and workspace components you intend to access.
Notes: the server is designed to support relative time expressions for due dates and to work with natural-language prompts via compatible MCP clients. Maintain up-to-date client integrations to leverage new features and compatibility updates.
Retrieve the complete workspace structure including spaces, folders, and lists to understand relationships and navigate the workspace tree.
Create a new task with a name and target list, optionally setting details like due date, priority, and description.
Create multiple tasks in a single operation by providing an array of task definitions.
Modify an existing task identified by ID or name, updating properties such as status, priority, due date, and description.
Update multiple tasks in a single operation using an array of task definitions with IDs or names.
Fetch tasks from a specific list by ID or name, with optional filtering by status, priority, or due date.
Retrieve full details for a single task by ID or name.
Remove a task by ID or name.
Remove multiple tasks by providing an array of IDs or names.
Move a single task to a different list, space, or folder by specifying the destination list or its path.
Move multiple tasks to a new destination list by providing IDs/names and target list.
Create a copy of a task in a specified list.
Create a new list within a space using a name and either spaceId or spaceName.
Create a new folder within a space by providing a name and space reference.
Create a new list inside a folder with a given name and folder reference.
Retrieve details for a folder by ID or name.
Update properties of a folder identified by ID or name.
Delete a folder by ID or name.
Get details of a list by ID or name.
Update list properties by ID or name.
Delete a list by ID or name.