clickup

This MCP server provides a ClickUp integration that exposes a suite of tools for managing ClickUp data from an MCP client. The server authenticates to ClickUp using a Personal API Token and exposes operations for tasks, spaces, folders, lists, boards, views, docs, and more. Clients can invoke the available tools to create tasks, update spaces, fetch lists, search docs, and manage views, among other capabilities. The tools are designed to be used in natural language prompts by the MCP client, which will route requests to the server and return structured results suitable for conversational assistants or automation flows.

To use the server, configure your MCP client with the server you want to run. The recommended setup in the provided example uses npx to fetch @nazruden/clickup-server, and you must supply your ClickUp Personal API Token via the CLICKUP_PERSONAL_TOKEN environment variable. Once configured, restart the MCP client so it can download and start the server. The client will then be able to invoke tools such as clickup_create_task, clickup_get_spaces, clickup_get_folders, clickup_create_doc, clickup_search_docs, and many others to interact with your ClickUp workspaces programmatically.

Prerequisites:

• Node.js (14.x or newer) and npm installed on your machine
• Access to an MCP client that supports dynamic server download via npx

Step-by-step installation:

1. Ensure Node.js and npm are installed. Verify with:

node -v
npm -v

2. Install the ClickUp MCP Server via Smithery or directly via npx as part of client configuration. Example using the README approach:

# When configuring your MCP client, use the following to fetch the server on demand:
npx -y @smithery/cli install @Nazruden/clickup-mcp-server --client claude

3. Configure the server for your client by adding the required environment variable. In your MCP client configuration (see the example below), set:

{
  "mcpServers": {
    "clickup": {
      "command": "npx",
      "args": ["@nazruden/clickup-server"],
      "env": {
        "CLICKUP_PERSONAL_TOKEN": "your_personal_api_token_here"
      }
    }
  }
}

4. Restart your MCP client to allow the server to be downloaded and started automatically when needed.
5. (Optional) Set additional environment variables like LOG_LEVEL or PORT in your client configuration if you plan to run HTTP endpoints or adjust logging. The essential variable is CLICKUP_PERSONAL_TOKEN.

Notes and tips:

• The server requires a valid ClickUp Personal API Token to authenticate requests. Keep this token secure and avoid exposing it in client-side code.
• Optional environment variables include LOG_LEVEL (error, warn, info, debug) and PORT for future HTTP-related features. The default Stdio MCP flow does not rely on PORT, but it may be relevant if you extend the server with HTTP transport.
• The available tools cover Task, Space, Folder, List, Board, Doc, and View management. Refer to the tool list in the README for exact required parameters.
• If you encounter token-related failures, double-check token permissions and ensure the token has access to the necessary ClickUp workspaces and resources.
• When using the MCP client, you may need to restart the client after adding or updating the configuration to ensure the server is pulled and run correctly.