- Home
- MCP servers
- ClickUp
ClickUp
- typescript
43
GitHub Stars
typescript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"nsxdavid-clickup-mcp-server": {
"command": "node",
"args": [
"/path/to/clickup-mcp-server/build/index.js"
],
"env": {
"CLICKUP_API_TOKEN": "YOUR_API_TOKEN_HERE"
}
}
}
}You can access and manipulate ClickUp data through a dedicated MCP server that exposes a standardized interface for AI assistants. This server lets you work with workspaces, spaces, folders, lists, tasks, docs, comments, and checklists, enabling seamless integration with ClickUp from your AI workflows.
How to use
You connect to the ClickUp MCP Server from your MCP client to perform common data operations. Use it to fetch workspaces, list spaces within a workspace, retrieve tasks, and create or update tasks. You can also retrieve docs from a workspace, create folders in spaces, and manage lists within folders or spaces. All actions are exposed through a consistent set of endpoints that your MCP client can call without writing custom API logic.
How to install
# Prerequisites: ensure Node.js and npm are installed on your system
# 1) Clone the MCP server repository
git clone https://github.com/nsxdavid/clickup-mcp-server.git
# 2) Change into the project directory
cd clickup-mcp-server
# 3) Install dependencies
npm install
# 4) Build the project (if required by the project workflow)
npm run build
# 5) Run the MCP server locally (example with Node runtime path to built index.js)
# This is how you would start the server when using the stdio configuration
node /path/to/clickup-mcp-server/build/index.js
Additional sections
Configuration details are provided to wire the MCP server into your environment. You will supply your API token and define how the MCP server is launched in your MCP settings. The following configuration snippets illustrate how to register the server for your environment.
Configuration example for MCP client
{
"mcpServers": {
"clickup": {
"command": "node",
"args": ["/path/to/clickup-mcp-server/build/index.js"],
"env": {
"CLICKUP_API_TOKEN": "YOUR_API_TOKEN_HERE"
},
"disabled": false,
"autoApprove": []
}
}
}
Alternate installation using npx
{
"mcpServers": {
"clickup": {
"command": "npx",
"args": ["-y", "clickup-mcp-server"],
"env": {
"CLICKUP_API_TOKEN": "YOUR_API_TOKEN_HERE"
},
"disabled": false,
"autoApprove": []
}
}
}
Available tools
get_workspaces
Fetch the list of workspaces available in your ClickUp account. Useful for selecting a scope before querying further resources.
get_spaces
Retrieve all spaces within a chosen workspace. Helps you navigate the organizational structure of your ClickUp data.
get_tasks
Get tasks from a specific list. You can filter by list and other task attributes to support task management workflows.
create_task
Create a new task in a specified list, enabling automated task generation from AI-driven actions.
update_task
Update properties of an existing task, such as status, priority, or due date, to reflect progress.
get_docs_from_workspace
Retrieve all docs within a workspace, enabling documentation access and management from automation.
create_folder
Create a new folder within a space to organize lists and tasks according to your workflow.
get_lists
List the lists within a folder or space to support navigation and selection in automated processes.
create_list
Create a new list within a folder or space to organize tasks and related content.