What can @taazkareem/clickup-mcp-server do?

clickup task crud operations via mcp protocol, clickup document retrieval and search via mcp, clickup chat message posting and retrieval via mcp, mcp tool schema generation and registration for clickup api, multi-client mcp server hosting and protocol negotiation, clickup api authentication and token management, clickup workspace and team context resolution, error handling and api response normalization, custom field mapping and type coercion

@taazkareem/clickup-mcp-server

MCP ServerFree

ClickUp MCP Server - Powering AI Agents with full ClickUp task, document, and chat management capabilities.

Open Source

/ 100

9 capabilities

Capabilities9 decomposed

clickup task crud operations via mcp protocol

Medium confidence

Exposes ClickUp task management (create, read, update, delete) through the Model Context Protocol, allowing AI agents to manipulate tasks by translating MCP tool calls into authenticated ClickUp REST API requests. Implements request/response serialization for task objects including fields like status, priority, assignees, and custom fields, with error handling for API rate limits and authentication failures.

Solves for

I want my AI agent to create tasks in ClickUp from conversation context without manual interventionI need to update task status and assignees programmatically based on agent decisionsI want to fetch task details and metadata to inform agent reasoning about project state

Best for

AI agent developers building ClickUp-integrated workflows

Teams using Claude Desktop, Cursor, or Gemini CLI with ClickUp workspaces

Automation engineers building N8N or Zapier-like task orchestration

Requires

ClickUp API token (generated from ClickUp workspace settings)

Node.js 16+ runtime for MCP server

Valid ClickUp workspace and team IDs

Limitations

Depends on ClickUp API rate limits (typically 100 requests/minute for standard tier)

Custom field handling requires pre-knowledge of field IDs in target workspace

No built-in batching — multiple task operations require sequential API calls

What makes it unique

Implements MCP tool schema mapping specifically for ClickUp's nested workspace/team/space/folder/list hierarchy, translating flat MCP calls into context-aware API requests that respect ClickUp's organizational structure

vs alternatives

Provides native MCP integration for ClickUp task management where Zapier/N8N require webhook setup and polling, enabling synchronous agent-driven task operations with direct API authentication

clickup document retrieval and search via mcp

Medium confidence

Enables AI agents to search and retrieve ClickUp Docs (rich-text documents) through MCP tool calls, translating semantic search queries into ClickUp API document listing/retrieval endpoints. Handles document parsing, metadata extraction (created_by, updated_at, access_level), and content serialization for agent context windows.

Solves for

I want my agent to search for relevant documentation before suggesting task changesI need to retrieve the full text of a ClickUp Doc to provide context to the AI modelI want to list all documents in a space to help the agent understand available knowledge

Best for

Knowledge-driven AI agents that need to reference internal documentation

Teams using ClickUp Docs as a centralized knowledge base

Agents building context-aware responses by combining task state with documentation

Requires

ClickUp API token with Docs read permissions

Node.js 16+ runtime

Valid ClickUp workspace with Docs feature enabled

Limitations

Document content is returned as plain text or HTML — no native support for embedded images or complex formatting

Search is limited to document listing and retrieval; no full-text search across document content (requires client-side filtering)

Large documents may exceed agent context window limits — no built-in pagination or chunking

What makes it unique

Bridges ClickUp Docs (a rich-text document system) with MCP's tool-calling interface, allowing agents to treat internal documentation as queryable context sources without requiring separate knowledge base infrastructure

vs alternatives

Tighter integration with ClickUp's native documentation than external RAG systems, eliminating sync delays and API key management for separate knowledge bases

clickup chat message posting and retrieval via mcp

Medium confidence

Allows AI agents to post messages to ClickUp task comments/chat and retrieve conversation history through MCP tool calls, translating agent outputs into ClickUp comment API requests with support for mentions, attachments, and threaded replies. Implements bidirectional synchronization of chat context between agent and ClickUp workspace.

Solves for

I want my agent to post status updates or decisions directly to task comments for team visibilityI need to retrieve task comment history to understand prior context and decisionsI want the agent to mention team members in comments to trigger notifications

Best for

Teams using ClickUp as a centralized communication hub alongside task management

Agents that need to provide audit trails of decisions by posting to task comments

Workflows where agent outputs should trigger team notifications via ClickUp mentions

Requires

ClickUp API token with comment/chat write permissions

Node.js 16+ runtime

Valid task IDs in ClickUp workspace

Limitations

Comment attachments require pre-upload to ClickUp or external URL references — no direct file streaming

Mention resolution requires pre-knowledge of user IDs; no fuzzy name matching

Comment history retrieval is paginated; large task conversations may require multiple API calls

What makes it unique

Implements bidirectional chat synchronization through MCP, allowing agents to both consume task conversation history and contribute to it, creating a unified communication channel between AI and human teams

vs alternatives

Avoids context fragmentation by keeping agent-generated insights in ClickUp's native comment system rather than external logs, improving team visibility and reducing context switching

mcp tool schema generation and registration for clickup api

Medium confidence

Dynamically generates MCP tool schemas that map ClickUp API endpoints to callable tools, handling parameter validation, type coercion, and error response formatting. Implements a registry pattern where each ClickUp API operation (task create, doc retrieve, etc.) is registered as an MCP tool with JSON Schema definitions for input validation and output typing.

Solves for

I want to expose ClickUp operations as tools that my AI agent can discover and callI need input validation and type checking before sending requests to ClickUp APII want consistent error handling and response formatting across all ClickUp operations

Best for

MCP server developers integrating third-party APIs

Teams building custom AI agent frameworks with tool discovery

Developers who need to abstract ClickUp API complexity behind a tool interface

Requires

Node.js 16+ with TypeScript or JavaScript runtime

MCP SDK for Node.js

ClickUp API documentation or manual schema definitions

Limitations

Schema generation is static at server startup — dynamic ClickUp workspace schema changes require server restart

Complex nested parameters (e.g., custom field definitions) may not map cleanly to JSON Schema

No automatic OpenAPI/Swagger import — schemas must be manually defined or generated from ClickUp API docs

What makes it unique

Implements MCP tool registration as a first-class pattern for ClickUp API, providing structured tool discovery and validation that MCP clients (Claude, Cursor, etc.) can introspect and call with type safety

vs alternatives

Cleaner than raw REST API integration because MCP clients get native tool discovery and parameter validation, vs. agents having to manage HTTP requests and error handling manually

multi-client mcp server hosting and protocol negotiation

Medium confidence

Runs as a standalone MCP server process that negotiates protocol versions and capabilities with multiple MCP clients (Claude Desktop, Cursor, Gemini CLI, N8N, Cline, Windsurf, Zed). Implements stdio/HTTP transport selection, client capability detection, and graceful degradation for clients with limited MCP support.

Solves for

I want to run a single ClickUp MCP server that works with Claude Desktop, Cursor, and other toolsI need my MCP server to handle multiple concurrent client connectionsI want to support both local (stdio) and remote (HTTP) MCP transports

Best for

Teams using multiple AI tools (Claude, Cursor, Gemini) that need unified ClickUp access

Developers building MCP servers for distribution across heterogeneous client ecosystems

Organizations deploying MCP servers as shared infrastructure

Requires

Node.js 16+ runtime

MCP SDK for Node.js

MCP-compatible client with stdio or HTTP transport support

Limitations

Stdio transport is single-connection only — requires separate server instances for multiple local clients

HTTP transport adds network latency and requires firewall/authentication configuration

Protocol version negotiation may fail silently if client/server versions are incompatible

What makes it unique

Abstracts MCP transport and client negotiation, allowing a single ClickUp MCP server to work seamlessly across Claude Desktop, Cursor, Gemini CLI, N8N, and other MCP-compatible tools without client-specific code

vs alternatives

Eliminates the need to build separate integrations for each tool (Zapier plugin, N8N node, Claude plugin) by leveraging MCP as a universal protocol

clickup api authentication and token management

Medium confidence

Manages ClickUp API authentication by accepting and validating API tokens, implementing secure token storage (environment variables or config files), and handling token refresh/expiration. Includes error handling for invalid tokens and automatic retry logic for transient authentication failures.

Solves for

I want to securely provide my ClickUp API token to the MCP server without hardcoding itI need the server to handle authentication errors gracefully and inform me of token issuesI want to rotate or update my ClickUp token without restarting the server

Best for

Developers deploying ClickUp MCP servers in production environments

Teams managing multiple ClickUp workspaces with different API tokens

Security-conscious organizations requiring token rotation and audit trails

Requires

Valid ClickUp API token (generated from ClickUp workspace settings)

Environment variable or config file for token storage

Node.js 16+ runtime

Limitations

ClickUp API tokens do not expire automatically — no built-in token refresh mechanism

Token storage relies on environment variables or file-based config — no native secret management integration (e.g., HashiCorp Vault)

No token rotation or versioning — changing tokens requires manual server configuration update

What makes it unique

Implements ClickUp API token validation as a prerequisite for MCP tool registration, ensuring that unauthenticated servers fail fast rather than returning cryptic API errors to clients

vs alternatives

Cleaner than embedding tokens in MCP tool definitions because it centralizes authentication logic and prevents token leakage in tool schemas or logs

clickup workspace and team context resolution

Medium confidence

Resolves ClickUp workspace, team, space, folder, and list hierarchies from API responses, allowing agents to reference resources by name or ID. Implements caching of workspace metadata to reduce API calls and provides context-aware defaults for operations that require parent resource IDs.

Solves for

I want my agent to create a task in 'Project X' without needing to know the space/folder IDsI need the agent to understand the ClickUp workspace structure to make intelligent decisionsI want to cache workspace metadata to avoid repeated API calls for the same resources

Best for

Agents operating across multiple ClickUp workspaces or teams

Scenarios where agents need to infer resource context from natural language (e.g., 'create task in Project X')

High-frequency agent operations where API call reduction is critical

Requires

ClickUp API token with workspace read permissions

Node.js 16+ runtime

Valid ClickUp workspace

Limitations

Workspace metadata caching is in-memory only — cache is lost on server restart

Name-to-ID resolution is not fuzzy — exact name matches required (case-sensitive by default)

Deeply nested hierarchies (space > folder > list > task) require multiple API calls to fully resolve

What makes it unique

Implements a context-aware resource resolver that maps human-readable ClickUp workspace names to API IDs, reducing the cognitive load on agents and enabling natural language task creation

vs alternatives

Avoids requiring agents to manually track ClickUp IDs by providing a semantic layer that resolves names to IDs, similar to how file systems abstract inode numbers

error handling and api response normalization

Medium confidence

Standardizes ClickUp API error responses into consistent MCP error formats, implementing retry logic for transient failures (rate limits, timeouts) and providing actionable error messages for permanent failures (invalid IDs, permission denied). Includes logging and monitoring hooks for debugging agent-API interactions.

Solves for

I want my agent to handle ClickUp API errors gracefully without crashingI need clear error messages that help me debug why a task creation failedI want the server to automatically retry transient failures like rate limits

Best for

Production deployments where API reliability is critical

Agents that need to make decisions based on error types (e.g., retry vs. fail)

Teams debugging agent-API integration issues

Requires

Node.js 16+ runtime

ClickUp API token

Limitations

Retry logic uses exponential backoff with fixed max retries — no adaptive retry strategies

Error classification is based on HTTP status codes and ClickUp error messages — may miss edge cases

Logging is not structured (no JSON logging by default) — requires custom log parsing

What makes it unique

Implements MCP-aware error handling that translates ClickUp API errors into MCP error schemas, allowing clients to handle errors consistently without parsing ClickUp-specific error formats

vs alternatives

Better error transparency than raw API proxies because it classifies errors (transient vs. permanent) and provides retry logic, reducing agent confusion and improving reliability

custom field mapping and type coercion

Medium confidence

Maps ClickUp custom fields (which have workspace-specific IDs and types) to MCP tool parameters, implementing type coercion for custom field values (dates, dropdowns, numbers, text). Handles custom field validation and provides schema definitions that agents can use to understand available fields.

Solves for

I want my agent to set custom fields on tasks without needing to know the field IDsI need the agent to understand what custom fields are available and their typesI want automatic type coercion so the agent can pass natural language values (e.g., 'high' for priority dropdown)

Best for

ClickUp workspaces with extensive custom field configurations

Agents that need to populate task metadata beyond standard fields

Teams where custom fields encode important business logic (e.g., SLA, cost center)

Requires

ClickUp API token with custom field read permissions

Node.js 16+ runtime

Valid ClickUp workspace with custom fields defined

Limitations

Custom field IDs are workspace-specific — schemas must be regenerated when custom fields change

Type coercion is limited to basic types (text, number, date, dropdown) — complex types (formulas, rollups) may not be supported

Dropdown value mapping requires pre-knowledge of valid options — no fuzzy matching for dropdown values

What makes it unique

Implements a custom field abstraction layer that maps workspace-specific ClickUp field IDs to semantic MCP parameters, allowing agents to work with custom fields without hardcoding field IDs

vs alternatives

Reduces boilerplate compared to agents manually managing custom field IDs and types, similar to how ORMs abstract database schema details

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with @taazkareem/clickup-mcp-server, ranked by overlap. Discovered automatically through the match graph.

MCP Server47

@taazkareem/clickup-mcp-server

ClickUp MCP Server - Powering AI Agents with full ClickUp task, document, and chat management capabilities.

chat-message-posting-and-retrievaltask-creation-and-management-via-mcpmcp-protocol-server-hostingdocument-retrieval-and-search-in-spaces

4 shared capabilities

MCP Server27

@hisma/server-puppeteer

Fork and update (v0.6.5) of the original @modelcontextprotocol/server-puppeteer MCP server for browser automation using Puppeteer.

mcp-server-lifecycle-and-process-management

1 shared capability

MCP Server24

user-postgresql-mcp

A PostgreSQL MCP server built with @modelcontextprotocol/sdk.

mcp protocol message handling and routing

1 shared capability

MCP Server25

any-chat-completions-mcp

** - Chat with any other OpenAI SDK Compatible Chat Completions API, like Perplexity, Groq, xAI and more

mcp protocol stdio communication with clients

1 shared capability

MCP Server23

WebSearch-MCP

** - Self-hosted Websearch API

mcp-compliant web search tool exposure

1 shared capability

MCP Server38

@ui5/mcp-server

MCP server for SAPUI5/OpenUI5 development

mcp protocol server implementation for ui5 development tools

1 shared capability

Best For

✓AI agent developers building ClickUp-integrated workflows
✓Teams using Claude Desktop, Cursor, or Gemini CLI with ClickUp workspaces
✓Automation engineers building N8N or Zapier-like task orchestration
✓Knowledge-driven AI agents that need to reference internal documentation
✓Teams using ClickUp Docs as a centralized knowledge base
✓Agents building context-aware responses by combining task state with documentation
✓Teams using ClickUp as a centralized communication hub alongside task management
✓Agents that need to provide audit trails of decisions by posting to task comments

Known Limitations

⚠Depends on ClickUp API rate limits (typically 100 requests/minute for standard tier)
⚠Custom field handling requires pre-knowledge of field IDs in target workspace
⚠No built-in batching — multiple task operations require sequential API calls
⚠Task creation latency varies with ClickUp API response time (typically 200-500ms per operation)
⚠Document content is returned as plain text or HTML — no native support for embedded images or complex formatting
⚠Search is limited to document listing and retrieval; no full-text search across document content (requires client-side filtering)

Requirements

ClickUp API token (generated from ClickUp workspace settings)Node.js 16+ runtime for MCP serverValid ClickUp workspace and team IDsMCP-compatible client (Claude Desktop, Cursor, Gemini CLI, or custom MCP host)ClickUp API token with Docs read permissionsNode.js 16+ runtimeValid ClickUp workspace with Docs feature enabledMCP-compatible client

Input / Output

Accepts: JSON task objects with name, description, priority, status, assignee_ids, Task IDs (strings or UUIDs), List/folder/space IDs for task creation context, Document IDs (strings), Space/folder IDs for listing documents, Search query strings (for client-side filtering), Task IDs (strings), Comment text (plain text strings), User IDs for mentions, Optional attachment URLs, Tool definition objects (name, description, parameters), JSON Schema parameter definitions, MCP client initialization messages, Tool call requests from clients, ClickUp API token (string), Workspace/team context (optional, for multi-workspace scenarios), Resource names (strings, e.g., 'Project X', 'Engineering'), Resource IDs (strings or UUIDs), Hierarchy paths (e.g., 'workspace > team > space > folder'), ClickUp API error responses (HTTP status codes, error messages), Custom field IDs (strings), Custom field values (strings, numbers, dates, arrays for multi-select), Custom field type definitions (from ClickUp API)

Produces: JSON task objects with full metadata (id, created_at, updated_at, custom_fields), Boolean success/failure responses, Error objects with ClickUp API error codes, JSON document objects with title, content, created_by, updated_at, access_level, Document lists with metadata, Plain text or HTML document content, JSON comment objects with id, text, created_by, created_at, replies, Comment lists with pagination metadata, Boolean success/failure for post operations, MCP tool schema JSON, Registered tool handlers (functions), MCP protocol responses, Tool execution results, Authentication status (boolean), Error messages for invalid/expired tokens, Resolved resource IDs, Workspace metadata objects (teams, spaces, folders, lists), Context objects with default parent IDs for operations, Normalized MCP error objects, Retry decisions (boolean), Log entries (text or JSON), Coerced custom field values, Custom field schema definitions (JSON Schema), Validation errors for invalid values

UnfragileRank

Adoption55%(30% weight)

Quality27%(25% weight)

Ecosystem70%(25% weight)

Match Graph10%(15% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

9 capabilities

Visit @taazkareem/clickup-mcp-server→

Repository Details

Package Details

npm

Registry

0.14.3

Version

27,410

Weekly Downloads

About

ClickUp MCP Server - Powering AI Agents with full ClickUp task, document, and chat management capabilities.

Alternatives to @taazkareem/clickup-mcp-server

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of @taazkareem/clickup-mcp-server?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

npm

Looking for something else?

Search →

Capabilities9 decomposed

clickup task crud operations via mcp protocol

Medium confidence

Solves for

Best for

AI agent developers building ClickUp-integrated workflows

Teams using Claude Desktop, Cursor, or Gemini CLI with ClickUp workspaces

Automation engineers building N8N or Zapier-like task orchestration

Requires

ClickUp API token (generated from ClickUp workspace settings)

Node.js 16+ runtime for MCP server

Valid ClickUp workspace and team IDs

Limitations

Depends on ClickUp API rate limits (typically 100 requests/minute for standard tier)

Custom field handling requires pre-knowledge of field IDs in target workspace

No built-in batching — multiple task operations require sequential API calls

What makes it unique

vs alternatives

Provides native MCP integration for ClickUp task management where Zapier/N8N require webhook setup and polling, enabling synchronous agent-driven task operations with direct API authentication

clickup document retrieval and search via mcp

Medium confidence

Solves for

Best for

Knowledge-driven AI agents that need to reference internal documentation

Teams using ClickUp Docs as a centralized knowledge base

Agents building context-aware responses by combining task state with documentation

Requires

ClickUp API token with Docs read permissions

Node.js 16+ runtime

Valid ClickUp workspace with Docs feature enabled

Limitations

Document content is returned as plain text or HTML — no native support for embedded images or complex formatting

Search is limited to document listing and retrieval; no full-text search across document content (requires client-side filtering)

Large documents may exceed agent context window limits — no built-in pagination or chunking

What makes it unique

vs alternatives

Tighter integration with ClickUp's native documentation than external RAG systems, eliminating sync delays and API key management for separate knowledge bases

clickup chat message posting and retrieval via mcp

Medium confidence

Solves for

Best for

Teams using ClickUp as a centralized communication hub alongside task management

Agents that need to provide audit trails of decisions by posting to task comments

Workflows where agent outputs should trigger team notifications via ClickUp mentions

Requires

ClickUp API token with comment/chat write permissions

Node.js 16+ runtime

Valid task IDs in ClickUp workspace

Limitations

Comment attachments require pre-upload to ClickUp or external URL references — no direct file streaming

Mention resolution requires pre-knowledge of user IDs; no fuzzy name matching

Comment history retrieval is paginated; large task conversations may require multiple API calls

What makes it unique

vs alternatives

Avoids context fragmentation by keeping agent-generated insights in ClickUp's native comment system rather than external logs, improving team visibility and reducing context switching

mcp tool schema generation and registration for clickup api

Medium confidence

Solves for

Best for

MCP server developers integrating third-party APIs

Teams building custom AI agent frameworks with tool discovery

Developers who need to abstract ClickUp API complexity behind a tool interface

Requires

Node.js 16+ with TypeScript or JavaScript runtime

MCP SDK for Node.js

ClickUp API documentation or manual schema definitions

Limitations

Schema generation is static at server startup — dynamic ClickUp workspace schema changes require server restart

Complex nested parameters (e.g., custom field definitions) may not map cleanly to JSON Schema

No automatic OpenAPI/Swagger import — schemas must be manually defined or generated from ClickUp API docs

What makes it unique

vs alternatives

Cleaner than raw REST API integration because MCP clients get native tool discovery and parameter validation, vs. agents having to manage HTTP requests and error handling manually

multi-client mcp server hosting and protocol negotiation

Medium confidence

Solves for

Best for

Teams using multiple AI tools (Claude, Cursor, Gemini) that need unified ClickUp access

Developers building MCP servers for distribution across heterogeneous client ecosystems

Organizations deploying MCP servers as shared infrastructure

Requires

Node.js 16+ runtime

MCP SDK for Node.js

MCP-compatible client with stdio or HTTP transport support

Limitations

Stdio transport is single-connection only — requires separate server instances for multiple local clients

HTTP transport adds network latency and requires firewall/authentication configuration

Protocol version negotiation may fail silently if client/server versions are incompatible

What makes it unique

vs alternatives

Eliminates the need to build separate integrations for each tool (Zapier plugin, N8N node, Claude plugin) by leveraging MCP as a universal protocol

clickup api authentication and token management

Medium confidence

Solves for

Best for

Developers deploying ClickUp MCP servers in production environments

Teams managing multiple ClickUp workspaces with different API tokens

Security-conscious organizations requiring token rotation and audit trails

Requires

Valid ClickUp API token (generated from ClickUp workspace settings)

Environment variable or config file for token storage

Node.js 16+ runtime

Limitations

ClickUp API tokens do not expire automatically — no built-in token refresh mechanism

Token storage relies on environment variables or file-based config — no native secret management integration (e.g., HashiCorp Vault)

No token rotation or versioning — changing tokens requires manual server configuration update

What makes it unique

Implements ClickUp API token validation as a prerequisite for MCP tool registration, ensuring that unauthenticated servers fail fast rather than returning cryptic API errors to clients

vs alternatives

Cleaner than embedding tokens in MCP tool definitions because it centralizes authentication logic and prevents token leakage in tool schemas or logs

clickup workspace and team context resolution

Medium confidence

Solves for

Best for

Agents operating across multiple ClickUp workspaces or teams

Scenarios where agents need to infer resource context from natural language (e.g., 'create task in Project X')

High-frequency agent operations where API call reduction is critical

Requires

ClickUp API token with workspace read permissions

Node.js 16+ runtime

Valid ClickUp workspace

Limitations

Workspace metadata caching is in-memory only — cache is lost on server restart

Name-to-ID resolution is not fuzzy — exact name matches required (case-sensitive by default)

Deeply nested hierarchies (space > folder > list > task) require multiple API calls to fully resolve

What makes it unique

Implements a context-aware resource resolver that maps human-readable ClickUp workspace names to API IDs, reducing the cognitive load on agents and enabling natural language task creation

vs alternatives

Avoids requiring agents to manually track ClickUp IDs by providing a semantic layer that resolves names to IDs, similar to how file systems abstract inode numbers

error handling and api response normalization

Medium confidence

Solves for

Best for

Production deployments where API reliability is critical

Agents that need to make decisions based on error types (e.g., retry vs. fail)

Teams debugging agent-API integration issues

Requires

Node.js 16+ runtime

ClickUp API token

Limitations

Retry logic uses exponential backoff with fixed max retries — no adaptive retry strategies

Error classification is based on HTTP status codes and ClickUp error messages — may miss edge cases

Logging is not structured (no JSON logging by default) — requires custom log parsing

What makes it unique

Implements MCP-aware error handling that translates ClickUp API errors into MCP error schemas, allowing clients to handle errors consistently without parsing ClickUp-specific error formats

vs alternatives

Better error transparency than raw API proxies because it classifies errors (transient vs. permanent) and provides retry logic, reducing agent confusion and improving reliability

custom field mapping and type coercion

Medium confidence

Solves for

Best for

ClickUp workspaces with extensive custom field configurations

Agents that need to populate task metadata beyond standard fields

Teams where custom fields encode important business logic (e.g., SLA, cost center)

Requires

ClickUp API token with custom field read permissions

Node.js 16+ runtime

Valid ClickUp workspace with custom fields defined

Limitations

Custom field IDs are workspace-specific — schemas must be regenerated when custom fields change

Type coercion is limited to basic types (text, number, date, dropdown) — complex types (formulas, rollups) may not be supported

Dropdown value mapping requires pre-knowledge of valid options — no fuzzy matching for dropdown values

What makes it unique

Implements a custom field abstraction layer that maps workspace-specific ClickUp field IDs to semantic MCP parameters, allowing agents to work with custom fields without hardcoding field IDs

vs alternatives

Reduces boilerplate compared to agents manually managing custom field IDs and types, similar to how ORMs abstract database schema details

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to @taazkareem/clickup-mcp-server

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

@taazkareem/clickup-mcp-server

Capabilities9 decomposed

clickup task crud operations via mcp protocol

clickup document retrieval and search via mcp

clickup chat message posting and retrieval via mcp

mcp tool schema generation and registration for clickup api

multi-client mcp server hosting and protocol negotiation

clickup api authentication and token management

clickup workspace and team context resolution

error handling and api response normalization

custom field mapping and type coercion

Related Artifactssharing capabilities

@taazkareem/clickup-mcp-server

@hisma/server-puppeteer

user-postgresql-mcp

any-chat-completions-mcp

WebSearch-MCP

@ui5/mcp-server

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Repository Details

Package Details

About

Categories

Alternatives to @taazkareem/clickup-mcp-server

Are you the builder of @taazkareem/clickup-mcp-server?

Get the weekly brief

Data Sources

@taazkareem/clickup-mcp-server

Capabilities9 decomposed

clickup task crud operations via mcp protocol

clickup document retrieval and search via mcp

clickup chat message posting and retrieval via mcp

mcp tool schema generation and registration for clickup api

multi-client mcp server hosting and protocol negotiation

clickup api authentication and token management

clickup workspace and team context resolution

error handling and api response normalization

custom field mapping and type coercion

Related Artifactssharing capabilities

@taazkareem/clickup-mcp-server

@hisma/server-puppeteer

user-postgresql-mcp

any-chat-completions-mcp

WebSearch-MCP

@ui5/mcp-server

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Repository Details

Package Details

About

Categories

Alternatives to @taazkareem/clickup-mcp-server

Are you the builder of @taazkareem/clickup-mcp-server?

Get the weekly brief

Data Sources