{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-taazkareemclickup-mcp-server","slug":"npm-taazkareemclickup-mcp-server","name":"@taazkareem/clickup-mcp-server","type":"mcp","url":"https://www.npmjs.com/package/@taazkareem/clickup-mcp-server","page_url":"https://unfragile.ai/npm-taazkareemclickup-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","task-management","productivity","automation","workflow","team-collaboration","artificial-intelligence","project-tracking","task-tracking","project-planning","clickup-integration","clickup-api","clickup-automation","task-organization","project-organization"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-taazkareemclickup-mcp-server__cap_0","uri":"capability://tool.use.integration.task.creation.and.management.via.mcp","name":"task-creation-and-management-via-mcp","description":"Creates, updates, and deletes ClickUp tasks through MCP protocol handlers that translate natural language or structured requests into ClickUp API calls. Implements request validation, error handling, and response transformation to present task operations as native MCP tools callable by AI agents without direct API knowledge.","intents":["I want my AI agent to create tasks in ClickUp when certain conditions are met","I need to update task status, priority, or assignee from within an AI workflow","I want to delete or archive tasks programmatically based on agent decisions"],"best_for":["AI agent developers building autonomous task management workflows","Teams integrating ClickUp with Claude, Gemini, or other MCP-compatible LLMs","Automation engineers replacing REST API calls with MCP-based task operations"],"limitations":["Requires valid ClickUp API token with appropriate workspace/team permissions","Task creation latency depends on ClickUp API response time (typically 200-500ms)","Batch operations not natively supported — each task requires separate MCP call","Custom fields require pre-existing field definitions in ClickUp workspace"],"requires":["ClickUp API token (personal or OAuth)","Node.js 16+","MCP-compatible client (Claude Desktop, Cursor, Gemini CLI, or custom MCP host)","Valid ClickUp workspace and team/list access"],"input_types":["structured JSON (task name, description, assignee, priority, due date)","natural language instructions from LLM","task IDs for update/delete operations"],"output_types":["task object with ID, status, timestamps","confirmation messages","error responses with validation details"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-taazkareemclickup-mcp-server__cap_1","uri":"capability://search.retrieval.document.retrieval.and.search.in.spaces","name":"document-retrieval-and-search-in-spaces","description":"Searches and retrieves ClickUp documents from workspaces/spaces using MCP resource handlers that query the ClickUp API and return document metadata, content, and hierarchy. Implements pagination and filtering to handle large document collections without overwhelming agent context windows.","intents":["I want my AI agent to find relevant documents in ClickUp based on search queries","I need to retrieve document content to provide context to an LLM for analysis or summarization","I want to list all documents in a space to understand available knowledge"],"best_for":["Knowledge workers building AI assistants that need access to ClickUp documentation","Teams using ClickUp Docs as a knowledge base for agent-powered Q&A systems","Developers implementing RAG (Retrieval-Augmented Generation) with ClickUp as the document source"],"limitations":["Search is limited to document titles and metadata — full-text search requires fetching and parsing document content","Large documents may exceed MCP message size limits; pagination required for content retrieval","Document access permissions inherited from ClickUp workspace — cannot override user-level restrictions","Real-time document updates may have slight lag due to API caching"],"requires":["ClickUp API token with Docs read permissions","Node.js 16+","MCP client with resource support (Claude Desktop 0.5+, Cursor, Gemini CLI)","Valid ClickUp workspace with Docs feature enabled"],"input_types":["search query strings","space/folder IDs","document IDs","filter parameters (date range, author)"],"output_types":["document metadata (title, ID, created date, author)","document content (markdown or HTML)","document hierarchy/breadcrumb","search result lists with relevance ranking"],"categories":["search-retrieval","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-taazkareemclickup-mcp-server__cap_10","uri":"capability://safety.moderation.oauth.and.token.based.authentication","name":"oauth-and-token-based-authentication","description":"Supports both personal API tokens and OAuth2 authentication flows for ClickUp, allowing secure credential management without exposing tokens in prompts. Implements token refresh logic and credential validation before making API calls.","intents":["I want to authenticate with ClickUp using OAuth instead of hardcoding API tokens","I need to securely manage ClickUp credentials in a multi-user environment","I want to validate authentication before attempting ClickUp operations"],"best_for":["Teams deploying shared MCP servers where multiple users need ClickUp access","Security-conscious organizations that require OAuth for credential management","Developers building multi-tenant AI agent platforms"],"limitations":["OAuth flow requires user interaction for initial authorization — not suitable for fully automated setups","Token refresh requires network access to ClickUp OAuth endpoints","No built-in credential storage — requires external secret management (e.g., environment variables, vaults)","OAuth tokens have expiration — server must handle token refresh transparently"],"requires":["ClickUp OAuth app credentials (client ID, client secret)","Node.js 16+","MCP client","Secure credential storage (environment variables or secret manager)"],"input_types":["OAuth authorization code (during initial setup)","API token (for personal token auth)"],"output_types":["authentication status (success/failure)","token refresh confirmation"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-taazkareemclickup-mcp-server__cap_2","uri":"capability://search.retrieval.task.list.and.filter.retrieval","name":"task-list-and-filter-retrieval","description":"Retrieves filtered task lists from ClickUp spaces/lists using MCP resource handlers that support multiple filter dimensions (status, assignee, priority, due date, custom fields). Implements efficient pagination and sorting to present task data to agents without requiring manual API query construction.","intents":["I want my agent to fetch all tasks assigned to a specific person or team","I need to retrieve high-priority tasks due this week for prioritization workflows","I want to get tasks in a specific status (e.g., 'In Progress') to monitor progress"],"best_for":["Workflow automation engineers building task monitoring and escalation systems","AI agent developers creating task prioritization or assignment recommendations","Teams building dashboards or reports powered by agent-driven task queries"],"limitations":["Complex multi-field filters may require multiple API calls if ClickUp API doesn't support all filter combinations","Large task lists (1000+) require pagination; retrieving all tasks in one call may timeout","Custom field filtering depends on field definitions existing in the workspace","Real-time task updates may lag by 1-2 seconds due to API caching"],"requires":["ClickUp API token with task read permissions","Node.js 16+","MCP client with resource support","Valid ClickUp workspace with tasks"],"input_types":["space/list/folder IDs","filter objects (status, assignee, priority, due date range)","sort parameters (by date, priority, custom field)","pagination parameters (limit, offset)"],"output_types":["task arrays with full metadata (ID, name, status, assignee, priority, due date, custom fields)","aggregated counts (tasks by status, by assignee)","pagination metadata (total count, has_more)"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-taazkareemclickup-mcp-server__cap_3","uri":"capability://tool.use.integration.chat.message.posting.and.retrieval","name":"chat-message-posting-and-retrieval","description":"Posts messages to ClickUp task comments and retrieves comment threads using MCP tool handlers that translate agent messages into ClickUp API calls. Supports rich text formatting, mentions, and attachment references while maintaining conversation context within task threads.","intents":["I want my agent to post status updates or notes to task comments automatically","I need to retrieve task comment history to provide context to an LLM for decision-making","I want to mention team members in task comments when escalating or assigning work"],"best_for":["Teams using ClickUp comments as a collaboration channel for agent-driven workflows","AI agents that need to provide feedback or updates within task context","Automation systems that log decisions or actions as task comments for audit trails"],"limitations":["Comment formatting limited to ClickUp's supported rich text (no custom HTML)","Mentions require valid ClickUp user IDs — agent must resolve names to IDs first","Comment history retrieval may be slow for tasks with 100+ comments","Attachments cannot be uploaded directly — only referenced by URL"],"requires":["ClickUp API token with comment read/write permissions","Node.js 16+","MCP client","Valid task IDs in ClickUp workspace"],"input_types":["task IDs","message text (plain or rich text)","user IDs for mentions","attachment URLs"],"output_types":["comment object with ID, timestamp, author, content","comment thread (array of comments with metadata)","confirmation of posted message"],"categories":["tool-use-integration","text-generation-language"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-taazkareemclickup-mcp-server__cap_4","uri":"capability://search.retrieval.workspace.and.team.context.discovery","name":"workspace-and-team-context-discovery","description":"Discovers and exposes ClickUp workspace structure (teams, spaces, lists, folders) through MCP resource handlers that query the ClickUp API and cache hierarchy metadata. Enables agents to understand available task containers and navigate the workspace without hardcoded IDs.","intents":["I want my agent to discover available teams and spaces to determine where to create tasks","I need to list all lists/folders in a space to understand task organization","I want my agent to validate that a target space exists before attempting operations"],"best_for":["Multi-team organizations where agents need to route tasks to correct spaces dynamically","Developers building flexible agent workflows that adapt to workspace structure changes","Teams implementing agent-driven task routing without hardcoding space/list IDs"],"limitations":["Hierarchy discovery is read-only — agents cannot create new spaces/lists via MCP","Large workspaces (100+ spaces) may have slow discovery due to API pagination","Metadata caching may be stale if workspace structure changes frequently","Custom field definitions require separate API call to retrieve"],"requires":["ClickUp API token with workspace read permissions","Node.js 16+","MCP client","Valid ClickUp workspace"],"input_types":["workspace ID (optional — defaults to authenticated user's workspace)","filter parameters (team ID, space ID)"],"output_types":["workspace metadata (name, ID, plan type)","teams array with IDs and names","spaces array with hierarchy (space > folder > list)","custom field definitions"],"categories":["search-retrieval","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-taazkareemclickup-mcp-server__cap_5","uri":"capability://tool.use.integration.task.status.and.custom.field.updates","name":"task-status-and-custom-field-updates","description":"Updates task metadata (status, priority, custom fields, due dates, assignees) through MCP tool handlers that validate field types and values against ClickUp's schema before submitting API calls. Implements field-type-aware transformations (date parsing, enum validation, number formatting) to prevent API errors.","intents":["I want my agent to move tasks between statuses based on workflow logic","I need to update custom fields (e.g., 'Effort Estimate', 'Client Name') programmatically","I want to change task priority or due date based on agent decisions"],"best_for":["Workflow automation engineers building status-driven task pipelines","AI agents that need to update task metadata based on analysis or decisions","Teams using custom fields for tracking and want agent-driven updates"],"limitations":["Custom field updates require pre-existing field definitions in ClickUp — agent cannot create new fields","Field validation is schema-based — invalid values are rejected before API call","Enum fields (status, priority) are workspace-specific — agent must know valid values","Date parsing may fail if agent provides ambiguous formats (e.g., '01/02/2024')"],"requires":["ClickUp API token with task write permissions","Node.js 16+","MCP client","Valid task IDs and field definitions in workspace"],"input_types":["task ID","field updates object (status, priority, custom_fields, due_date, assignees)","field values (strings, numbers, dates, enums)"],"output_types":["updated task object with new metadata","validation error messages if update fails","confirmation of successful update"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-taazkareemclickup-mcp-server__cap_6","uri":"capability://tool.use.integration.mcp.protocol.server.hosting","name":"mcp-protocol-server-hosting","description":"Runs as a standalone MCP server process that exposes ClickUp capabilities via the Model Context Protocol, handling authentication, request routing, and response serialization. Supports multiple concurrent MCP clients (Claude Desktop, Cursor, Gemini CLI, n8n) through a single server instance with configurable logging and error handling.","intents":["I want to run a single ClickUp MCP server that multiple AI tools can connect to","I need to host the MCP server in a specific environment (local, Docker, cloud)","I want to monitor and debug MCP requests and responses"],"best_for":["Teams deploying ClickUp integration across multiple MCP clients (Claude, Cursor, Gemini)","DevOps engineers containerizing MCP servers for production environments","Developers debugging MCP protocol issues or custom tool implementations"],"limitations":["Single-threaded Node.js process — high concurrency may cause latency spikes","No built-in load balancing or clustering — requires external orchestration for HA","Authentication via environment variables — no dynamic credential rotation","Logging is basic — requires integration with external monitoring for production use"],"requires":["Node.js 16+","ClickUp API token (as environment variable)","MCP client compatible with stdio or SSE transport","Port availability (if using HTTP transport)"],"input_types":["MCP protocol messages (JSON-RPC over stdio or HTTP)","tool calls with parameters","resource requests"],"output_types":["MCP protocol responses (JSON-RPC)","tool results","resource data","error messages"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-taazkareemclickup-mcp-server__cap_7","uri":"capability://memory.knowledge.ai.agent.context.window.optimization","name":"ai-agent-context-window-optimization","description":"Structures MCP responses to fit within LLM context windows by implementing pagination, summarization, and selective field inclusion. Omits unnecessary metadata and provides compact representations of large task lists or document collections, allowing agents to work with ClickUp data without exceeding token limits.","intents":["I want my agent to work with large task lists without exceeding context window limits","I need to retrieve task data in a compact format to preserve tokens for reasoning","I want my agent to fetch only relevant fields (e.g., task name and status, not full metadata)"],"best_for":["Developers building token-efficient AI agents with limited context windows","Teams using smaller LLMs (e.g., Claude 3 Haiku) that have tight token budgets","Workflows that need to process many tasks in a single agent run"],"limitations":["Pagination requires multiple MCP calls — agents must handle pagination logic","Selective field inclusion may omit data needed for downstream decisions","Summarization is lossy — agents cannot access full task details without additional calls","No built-in compression — context optimization depends on agent prompt design"],"requires":["MCP client with pagination support","Agent prompt that understands pagination parameters","ClickUp API token"],"input_types":["pagination parameters (limit, offset)","field selection parameters (which fields to include)","filter parameters (to reduce result set)"],"output_types":["compact task objects (name, ID, status, assignee only)","pagination metadata (total count, has_more)","summarized task lists"],"categories":["memory-knowledge","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-taazkareemclickup-mcp-server__cap_8","uri":"capability://safety.moderation.error.handling.and.api.resilience","name":"error-handling-and-api-resilience","description":"Implements retry logic, rate-limit handling, and error transformation for ClickUp API calls, converting API errors into human-readable messages for agents. Includes exponential backoff for transient failures and graceful degradation when ClickUp API is unavailable.","intents":["I want my agent to automatically retry failed ClickUp operations","I need clear error messages when ClickUp API calls fail","I want my agent to handle rate limits gracefully without crashing"],"best_for":["Production AI agents that need reliable ClickUp integration","Teams with high-volume task operations that may hit rate limits","Developers building fault-tolerant automation workflows"],"limitations":["Retry logic adds latency (exponential backoff up to 30 seconds)","Rate limit handling is reactive — no proactive rate limit prediction","Transient failures are retried up to 3 times — persistent failures fail fast","Error messages are generic — specific ClickUp API error details may be lost"],"requires":["Node.js 16+","MCP client with timeout support","ClickUp API token"],"input_types":["MCP tool calls","API responses (success or error)"],"output_types":["successful operation results","error messages with retry information","rate limit warnings"],"categories":["safety-moderation","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-taazkareemclickup-mcp-server__cap_9","uri":"capability://tool.use.integration.multi.client.mcp.compatibility","name":"multi-client-mcp-compatibility","description":"Maintains compatibility with multiple MCP clients (Claude Desktop, Cursor IDE, Gemini CLI, n8n, Cline, Windsurf, Zed, Supermaven) through adherence to MCP protocol standards and testing against each client's specific transport and tool-calling implementations. Handles client-specific quirks (e.g., different JSON-RPC versions, tool parameter formats).","intents":["I want to use the same ClickUp MCP server with Claude Desktop and Cursor","I need my ClickUp integration to work with n8n workflows","I want to ensure compatibility across multiple AI tools without maintaining separate integrations"],"best_for":["Teams using multiple MCP clients and wanting a single ClickUp integration","Developers building MCP servers that need broad client support","Organizations with heterogeneous AI tool stacks (Claude, Gemini, Cursor, etc.)"],"limitations":["Client-specific features (e.g., Claude's vision) are not supported by all clients","Testing across all clients is manual — no automated cross-client test suite","Protocol updates in MCP spec may require server updates for new clients","Some clients have different tool parameter validation rules — edge cases may fail on specific clients"],"requires":["Node.js 16+","MCP-compatible client (Claude Desktop 0.5+, Cursor, Gemini CLI, n8n, etc.)","ClickUp API token"],"input_types":["MCP protocol messages from any compatible client"],"output_types":["MCP protocol responses compatible with requesting client"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":46,"verified":false,"data_access_risk":"high","permissions":["ClickUp API token (personal or OAuth)","Node.js 16+","MCP-compatible client (Claude Desktop, Cursor, Gemini CLI, or custom MCP host)","Valid ClickUp workspace and team/list access","ClickUp API token with Docs read permissions","MCP client with resource support (Claude Desktop 0.5+, Cursor, Gemini CLI)","Valid ClickUp workspace with Docs feature enabled","ClickUp OAuth app credentials (client ID, client secret)","MCP client","Secure credential storage (environment variables or secret manager)"],"failure_modes":["Requires valid ClickUp API token with appropriate workspace/team permissions","Task creation latency depends on ClickUp API response time (typically 200-500ms)","Batch operations not natively supported — each task requires separate MCP call","Custom fields require pre-existing field definitions in ClickUp workspace","Search is limited to document titles and metadata — full-text search requires fetching and parsing document content","Large documents may exceed MCP message size limits; pagination required for content retrieval","Document access permissions inherited from ClickUp workspace — cannot override user-level restrictions","Real-time document updates may have slight lag due to API caching","OAuth flow requires user interaction for initial authorization — not suitable for fully automated setups","Token refresh requires network access to ClickUp OAuth endpoints","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.5463886293337168,"quality":0.47,"ecosystem":0.6000000000000001,"match_graph":0.25,"freshness":0.52,"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:24.483Z","last_scraped_at":"2026-05-03T14:23:34.252Z","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=npm-taazkareemclickup-mcp-server","compare_url":"https://unfragile.ai/compare?artifact=npm-taazkareemclickup-mcp-server"}},"signature":"I2c0o6sVaVQrXGMdjlPyMN5+HOTUldRMbw6O3cJOOjFA6FNM1Cii5eIMG+TZ0xumGoTHKlor7YBEIVuFjWkNAw==","signedAt":"2026-06-22T08:31:12.908Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-taazkareemclickup-mcp-server","artifact":"https://unfragile.ai/npm-taazkareemclickup-mcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=npm-taazkareemclickup-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"}}