ClickUp

Provides an MCP server that enables AI assistants to manage ClickUp workspaces via tasks, lists, teams, and boards.
  • typescript

0

GitHub Stars

typescript

Language

7 months ago

First Indexed

3 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": {
    "mcp-mirror-nazruden_clickup-mcp-server": {
      "command": "npx",
      "args": [
        "@mcp/clickup-server"
      ],
      "env": {
        "PORT": "3000",
        "LOG_LEVEL": "info",
        "CLICKUP_CLIENT_ID": "your_client_id",
        "CLICKUP_REDIRECT_URI": "http://localhost:3000/oauth/callback",
        "CLICKUP_CLIENT_SECRET": "your_client_secret"
      }
    }
  }
}

You can connect an AI assistant to ClickUp workspaces through this MCP server, enabling tasks, lists, teams, and boards to be managed via natural language commands. It handles authentication securely, exposes practical actions, and starts on demand when your MCP client needs it, so you don’t run a separate server process all the time.

How to use

Your AI assistant uses the ClickUp MCP Server to perform common ClickUp actions. Configure the MCP client with the ClickUp server entry, then ask your assistant to create tasks, update tasks, fetch teams and lists, or create boards. The server handles authentication and API calls in the background, returning results to your assistant.

How to install

Prerequisites you need before starting:

  • Node.js (LTS version) and npm installed on your machine.

Follow these steps to set up the ClickUp MCP Server configuration for your MCP client.

{
  "mcpServers": {
    "clickup": {
      "command": "npx",
      "args": ["@mcp/clickup-server"],
      "env": {
        "CLICKUP_CLIENT_ID": "your_client_id",
        "CLICKUP_CLIENT_SECRET": "your_client_secret",
        "CLICKUP_REDIRECT_URI": "http://localhost:3000/oauth/callback"
      }
    }
  }
}

Security and configuration notes

All tokens and credentials are handled securely and encrypted at rest. The OAuth2 flow is used for authentication, and the system avoids logging sensitive data. If you need to customize logging, you can set a logging level via an environment variable.

Troubleshooting

Common issues and how to address them include authentication errors, rate limiting, and server startup problems. Ensure your OAuth credentials are correct, verify the redirect URI matches your setup, and check for token expiration. If you encounter rate limits, review logs for warnings and consider batching requests.

Notes on environment and ports

Required environment variables are CLICKUP_CLIENT_ID, CLICKUP_CLIENT_SECRET, and CLICKUP_REDIRECT_URI. Optional variables include PORT (default 3000) and LOG_LEVEL (default info). The server uses port 3000 by default, but you can override it with the PORT variable.

Available tools

clickup_create_task

Create a new task in a ClickUp list by specifying details such as task name, description, due date, and assignees.

clickup_update_task

Update properties of an existing ClickUp task, such as status, priority, due date, or assignees.

clickup_get_teams

Retrieve all teams accessible to the authenticated user, including team IDs and names.

clickup_get_lists

Fetch all lists within a specified folder or space to locate the right place for new or updated tasks.

clickup_create_board

Create a new board within a ClickUp space to organize workflows and visualize progress.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational