{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm-taazkareem-clickup-mcp-server","slug":"taazkareem-clickup-mcp-server","name":"@taazkareem/clickup-mcp-server","type":"mcp","url":"https://github.com/taazkareem/clickup-mcp-server","page_url":"https://unfragile.ai/taazkareem-clickup-mcp-server","categories":["mcp-servers","documentation"],"tags":["clickup","mcp","ai","tasks","project-management","model-context-protocol","mcp-server","claude","claude-desktop","gemini","gemini-cli","cursor","cursor-ide","n8n","cline","windsurf","zed","supermaven","clickup-server","clickup-mcp-server"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm-taazkareem-clickup-mcp-server__cap_0","uri":"capability://tool.use.integration.clickup.task.crud.operations.via.mcp.protocol","name":"clickup task crud operations via mcp protocol","description":"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.","intents":["I want my AI agent to create tasks in ClickUp from conversation context without manual intervention","I need to update task status and assignees programmatically based on agent decisions","I 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"],"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)"],"requires":["ClickUp API token (generated from ClickUp workspace settings)","Node.js 16+ runtime for MCP server","Valid ClickUp workspace and team IDs","MCP-compatible client (Claude Desktop, Cursor, Gemini CLI, or custom MCP host)"],"input_types":["JSON task objects with name, description, priority, status, assignee_ids","Task IDs (strings or UUIDs)","List/folder/space IDs for task creation context"],"output_types":["JSON task objects with full metadata (id, created_at, updated_at, custom_fields)","Boolean success/failure responses","Error objects with ClickUp API error codes"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-taazkareem-clickup-mcp-server__cap_1","uri":"capability://memory.knowledge.clickup.document.retrieval.and.search.via.mcp","name":"clickup document retrieval and search via mcp","description":"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.","intents":["I want my agent to search for relevant documentation before suggesting task changes","I need to retrieve the full text of a ClickUp Doc to provide context to the AI model","I 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"],"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","Access control is enforced by ClickUp API but not explicitly surfaced in MCP responses"],"requires":["ClickUp API token with Docs read permissions","Node.js 16+ runtime","Valid ClickUp workspace with Docs feature enabled","MCP-compatible client"],"input_types":["Document IDs (strings)","Space/folder IDs for listing documents","Search query strings (for client-side filtering)"],"output_types":["JSON document objects with title, content, created_by, updated_at, access_level","Document lists with metadata","Plain text or HTML document content"],"categories":["memory-knowledge","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-taazkareem-clickup-mcp-server__cap_2","uri":"capability://tool.use.integration.clickup.chat.message.posting.and.retrieval.via.mcp","name":"clickup chat message posting and retrieval via mcp","description":"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.","intents":["I want my agent to post status updates or decisions directly to task comments for team visibility","I need to retrieve task comment history to understand prior context and decisions","I 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"],"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","No support for rich formatting (markdown/HTML) — comments are plain text or basic ClickUp formatting"],"requires":["ClickUp API token with comment/chat write permissions","Node.js 16+ runtime","Valid task IDs in ClickUp workspace","MCP-compatible client"],"input_types":["Task IDs (strings)","Comment text (plain text strings)","User IDs for mentions","Optional attachment URLs"],"output_types":["JSON comment objects with id, text, created_by, created_at, replies","Comment lists with pagination metadata","Boolean success/failure for post operations"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-taazkareem-clickup-mcp-server__cap_3","uri":"capability://tool.use.integration.mcp.tool.schema.generation.and.registration.for.clickup.api","name":"mcp tool schema generation and registration for clickup api","description":"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.","intents":["I want to expose ClickUp operations as tools that my AI agent can discover and call","I need input validation and type checking before sending requests to ClickUp API","I 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"],"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","Tool discovery is limited to MCP protocol capabilities — no runtime introspection of available operations"],"requires":["Node.js 16+ with TypeScript or JavaScript runtime","MCP SDK for Node.js","ClickUp API documentation or manual schema definitions"],"input_types":["Tool definition objects (name, description, parameters)","JSON Schema parameter definitions"],"output_types":["MCP tool schema JSON","Registered tool handlers (functions)"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-taazkareem-clickup-mcp-server__cap_4","uri":"capability://tool.use.integration.multi.client.mcp.server.hosting.and.protocol.negotiation","name":"multi-client mcp server hosting and protocol negotiation","description":"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.","intents":["I want to run a single ClickUp MCP server that works with Claude Desktop, Cursor, and other tools","I need my MCP server to handle multiple concurrent client connections","I 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"],"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","No built-in load balancing or clustering — single server instance is a potential bottleneck"],"requires":["Node.js 16+ runtime","MCP SDK for Node.js","MCP-compatible client with stdio or HTTP transport support","Network access (for HTTP transport) or local process spawning (for stdio)"],"input_types":["MCP client initialization messages","Tool call requests from clients"],"output_types":["MCP protocol responses","Tool execution results"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-taazkareem-clickup-mcp-server__cap_5","uri":"capability://safety.moderation.clickup.api.authentication.and.token.management","name":"clickup api authentication and token management","description":"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.","intents":["I want to securely provide my ClickUp API token to the MCP server without hardcoding it","I need the server to handle authentication errors gracefully and inform me of token issues","I 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"],"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","Authentication errors are not distinguished from authorization errors in some ClickUp API responses"],"requires":["Valid ClickUp API token (generated from ClickUp workspace settings)","Environment variable or config file for token storage","Node.js 16+ runtime"],"input_types":["ClickUp API token (string)","Workspace/team context (optional, for multi-workspace scenarios)"],"output_types":["Authentication status (boolean)","Error messages for invalid/expired tokens"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-taazkareem-clickup-mcp-server__cap_6","uri":"capability://memory.knowledge.clickup.workspace.and.team.context.resolution","name":"clickup workspace and team context resolution","description":"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.","intents":["I want my agent to create a task in 'Project X' without needing to know the space/folder IDs","I need the agent to understand the ClickUp workspace structure to make intelligent decisions","I 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"],"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","Cache invalidation is manual — no automatic refresh when ClickUp workspace structure changes"],"requires":["ClickUp API token with workspace read permissions","Node.js 16+ runtime","Valid ClickUp workspace"],"input_types":["Resource names (strings, e.g., 'Project X', 'Engineering')","Resource IDs (strings or UUIDs)","Hierarchy paths (e.g., 'workspace > team > space > folder')"],"output_types":["Resolved resource IDs","Workspace metadata objects (teams, spaces, folders, lists)","Context objects with default parent IDs for operations"],"categories":["memory-knowledge","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-taazkareem-clickup-mcp-server__cap_7","uri":"capability://safety.moderation.error.handling.and.api.response.normalization","name":"error handling and api response normalization","description":"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.","intents":["I want my agent to handle ClickUp API errors gracefully without crashing","I need clear error messages that help me debug why a task creation failed","I 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"],"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","No built-in metrics/monitoring — requires external APM integration for observability"],"requires":["Node.js 16+ runtime","ClickUp API token"],"input_types":["ClickUp API error responses (HTTP status codes, error messages)"],"output_types":["Normalized MCP error objects","Retry decisions (boolean)","Log entries (text or JSON)"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-taazkareem-clickup-mcp-server__cap_8","uri":"capability://data.processing.analysis.custom.field.mapping.and.type.coercion","name":"custom field mapping and type coercion","description":"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.","intents":["I want my agent to set custom fields on tasks without needing to know the field IDs","I need the agent to understand what custom fields are available and their types","I 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)"],"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","Custom field validation is basic — complex validation rules (e.g., conditional fields) are not enforced"],"requires":["ClickUp API token with custom field read permissions","Node.js 16+ runtime","Valid ClickUp workspace with custom fields defined"],"input_types":["Custom field IDs (strings)","Custom field values (strings, numbers, dates, arrays for multi-select)","Custom field type definitions (from ClickUp API)"],"output_types":["Coerced custom field values","Custom field schema definitions (JSON Schema)","Validation errors for invalid values"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":48,"verified":false,"data_access_risk":"high","permissions":["ClickUp API token (generated from ClickUp workspace settings)","Node.js 16+ runtime for MCP server","Valid ClickUp workspace and team IDs","MCP-compatible client (Claude Desktop, Cursor, Gemini CLI, or custom MCP host)","ClickUp API token with Docs read permissions","Node.js 16+ runtime","Valid ClickUp workspace with Docs feature enabled","MCP-compatible client","ClickUp API token with comment/chat write permissions","Valid task IDs in ClickUp workspace"],"failure_modes":["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)","Large documents may exceed agent context window limits — no built-in pagination or chunking","Access control is enforced by ClickUp API but not explicitly surfaced in MCP responses","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","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.5463886293337168,"quality":0.43,"ecosystem":0.7000000000000001,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.902Z","last_scraped_at":"2026-05-03T14:04:47.472Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":26972,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=taazkareem-clickup-mcp-server","compare_url":"https://unfragile.ai/compare?artifact=taazkareem-clickup-mcp-server"}},"signature":"9y6pIfgh2ImW8PBCsb3hI1djwnn8XiEGc9eefoncOHWBSgJONuESjGkvu7Uk8swRNN5h4T+AMjePmWYUvgSgCw==","signedAt":"2026-06-23T04:19:29.699Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/taazkareem-clickup-mcp-server","artifact":"https://unfragile.ai/taazkareem-clickup-mcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=taazkareem-clickup-mcp-server","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}