ClickUp MCP Server Enhanced

A comprehensive Model Context Protocol (MCP) server suite providing AI assistants with complete ClickUp integration. Features 177 ClickUp tools (a small core set loads by default; the rest load on demand), AI-powered project intelligence, production-grade security, and full GitHub Flavored Markdown support.

📦 Package Suite

Core Server: @chykalophia/clickup-mcp-server

Complete ClickUp API integration with 177 tools covering all major functionality:

• Tasks, Lists, Spaces, Folders, Workspaces
• Comments, Attachments, Custom Fields, Views
• Time Tracking, Goals, Dependencies, Webhooks
• Chat, Bulk Operations, Real-time Processing

Intelligence Server: @chykalophia/clickup-intelligence-mcp-server ⭐ NEW

AI-powered project management intelligence and workflow optimization:

• Project Health Analyzer: Real-time health scoring and risk assessment ✅ COMPLETED
• Smart Sprint Planner: AI-optimized sprint planning with capacity analysis ✅ COMPLETED
• Task Decomposition Engine: Intelligent task breakdown and sizing
• Resource Optimizer: Team workload balancing and skill matching
• Workflow Intelligence: Pattern analysis and automation recommendations

Shared Utilities: @chykalophia/clickup-mcp-shared

Common types, schemas, and utilities shared across packages.

📦 Quick Install: npx @chykalophia/clickup-mcp-server - No build required!

🚀 Monorepo Architecture

This project uses a monorepo structure with multiple packages:

clickup-mcp-server/
├── packages/
│   ├── core/                          # @chykalophia/clickup-mcp-server
│   │   ├── 177 tools                  # Complete ClickUp API coverage
│   │   ├── Production security        # Zero vulnerabilities
│   │   └── Markdown support           # GitHub Flavored Markdown
│   ├── intelligence/                  # @chykalophia/clickup-intelligence-mcp-server
│   │   ├── Project Health Analyzer    # AI-powered health scoring
│   │   ├── Smart Sprint Planner       # Optimized sprint planning
│   │   ├── Task Decomposition Engine  # Intelligent task breakdown
│   │   ├── Resource Optimizer         # Team workload balancing
│   │   └── Workflow Intelligence      # Pattern analysis & automation
│   └── shared/                        # @chykalophia/clickup-mcp-shared
│       ├── Common types & schemas     # Shared utilities
│       └── Validation helpers         # Cross-package consistency
└── Root workspace configuration

📦 Installation Options

Option 1: Core Server Only (Recommended for most users)

npm install @chykalophia/clickup-mcp-server

Option 2: Intelligence Server Only (AI features)

npm install @chykalophia/clickup-intelligence-mcp-server

Option 3: Full Suite (Core + Intelligence)

npm install @chykalophia/clickup-mcp-server @chykalophia/clickup-intelligence-mcp-server

Option 4: Development Setup (Monorepo)

git clone https://github.com/Chykalophia/ClickUp-MCP-Server---Enhanced.git
cd ClickUp-MCP-Server---Enhanced
npm install
npm run build

📋 Attribution

This Enhanced version is based on the original ClickUp MCP Server codebase by David Whatley at nsxdavid/clickup-mcp-server.

🚀 Key Features

🧠 AI-Powered Efficiency ⭐

• Smart Tool Suggestions: Context-aware recommendations for optimal workflows
• Workflow Optimization: 50-70% efficiency gains in common workflows
• Intelligent Discovery: Purpose-built tools that replace inefficient navigation
• Direct Access: Skip hierarchical navigation with smart discovery tools

✅ GitHub Flavored Markdown Support

• Rich Text Formatting: Headers, bold, italic, code blocks, lists, tables, links
• Smart Content Processing: Automatic markdown ↔ HTML ↔ plain text conversion
• Syntax Highlighting: Code blocks with language-specific highlighting
• Backward Compatible: Existing plain text content continues to work

🛠️ Comprehensive API Coverage

• 177 Total Tools covering 100% of major ClickUp API endpoints
• 9 Feature Domains: Tasks, comments, docs, webhooks, views, dependencies, attachments, time tracking, goals
• Real-time Integration: Webhook processing with HMAC validation
• Advanced Workflows: Dependencies, custom fields, bulk operations

🔒 Production Ready Security

• Zero Vulnerabilities: Comprehensive security audit with 85+ test cases
• Input Validation: XSS and injection prevention with sanitization
• Rate Limiting: Configurable thresholds (1000 API, 100 webhook, 10 upload/min)
• HMAC Validation: Secure webhook authentication with timing-safe comparison
• File Security: Path traversal prevention, dangerous file blocking, size limits

🏷️ Namespaced Tool Names

• Conflict Prevention: All tools prefixed with clickup_ to avoid conflicts with other MCP servers
• Clear Identification: Easy to distinguish ClickUp tools from other services (e.g., clickup_get_tasks vs taskmaster_get_tasks)
• Backward Compatibility: Previous tool names are deprecated but documented for migration
• Examples: clickup_create_task, clickup_get_workspaces, clickup_update_comment

📊 Complete Tool Inventory (177 Tools, plus 3 catalog tools)

🧠 Discovery & Tool Loading ⭐

• Catalog tools (always on): clickup_list_toolsets, clickup_enable_toolset, clickup_call_tool reach every tool without loading all schemas up front (see Tool loading)
• Smart Discovery: clickup_get_workspace_hierarchy (names to IDs in one call), clickup_find_member, clickup_search_chat_channels

Core Workspace Management (54 tools)

• Workspaces: clickup_get_workspaces, clickup_get_workspace_seats
• Finding things by name: clickup_get_workspace_hierarchy — the whole space/folder/list tree as IDs and names in one call, with an optional name_filter. Start here when you know a name but need an ID; it replaces a manual walk that measured 4 round trips and 60 KB against a real workspace (now 2 calls and ~200 bytes).
• Spaces & Lists: clickup_get_spaces, clickup_get_lists, clickup_create_list, clickup_update_list, clickup_delete_list (with safeguards)
• Tasks: clickup_get_tasks, clickup_create_task, clickup_update_task, clickup_get_task_details (with markdown support)
• Bulk Task Operations: clickup_bulk_create_tasks, clickup_bulk_update_tasks (up to 50 tasks per request)
• Delete Operations: clickup_delete_task, clickup_bulk_delete_tasks, clickup_delete_subtask (with confirmation safeguards)
• Task Merging: clickup_merge_tasks (merge multiple tasks with content preservation)
• Comments: clickup_create_task_comment, clickup_create_list_comment, clickup_create_chat_view_comment (with markdown)
• Checklists: clickup_create_checklist, clickup_update_checklist, clickup_create_checklist_item

Advanced Feature Domains

• 📄 Document Management (18 tools): Full CRUD, pages, sharing, search with markdown support
• 🔧 Custom Fields (15 tools): All field types, values, templates, bulk operations
• 📎 Attachments (14 tools): Upload, download, versions, thumbnails, security validation
• 👁️ Views (13 tools): All view types, filters, grouping, sharing, custom configurations
• 🔗 Dependencies (12 tools): Relationships, graphs, conflict detection, critical path
• 🎯 Goals (12 tools): All goal types, targets, progress tracking, analytics
• 🔔 Webhooks (11 tools): Real-time processing, HMAC validation, event history
• ⏱️ Time Tracking (10 tools): Entries, timers, analytics, team tracking
• 💬 Chat & Communication (24 tools): Enhanced chat discovery and messaging

🚀 Efficiency Examples

Smart Chat Discovery

Instead of hierarchical navigation:

// ❌ OLD WAY (4+ API calls)
clickup_get_workspaces() → clickup_get_spaces() → clickup_get_views() → filter for chat

// ✅ NEW WAY (1 tool call; searches up to the first 1,000 channels)
clickup_search_chat_channels({ workspace_id: "123", query: "development" })

Bulk Task Operations

// Create multiple tasks efficiently
clickup_bulk_create_tasks({
  list_id: "123456789",
  tasks: [
    {
      name: "Setup Database Schema",
      description: "Create initial database tables and relationships",
      priority: 3,
      assignees: [12345],
      tags: ["backend", "database"]
    },
    {
      name: "Design API Endpoints",
      description: "# API Design\n\n- Authentication endpoints\n- CRUD operations\n- Error handling",
      priority: 2,
      assignees: [12345, 67890]
    },
    {
      name: "Write Unit Tests",
      description: "Comprehensive test coverage for all modules",
      priority: 1,
      tags: ["testing", "quality"]
    }
  ],
  continue_on_error: true
})
// Returns: Detailed results with success/failure status for each task

// Update multiple tasks at once
clickup_bulk_update_tasks({
  tasks: [
    { task_id: "abc123", status: "in progress", priority: 4 },
    { task_id: "def456", status: "completed" },
    { task_id: "ghi789", assignees: [12345, 67890] }
  ],
  continue_on_error: false
})
// Returns: Bulk update results with execution time and detailed status

Delete Operations with Safeguards

// Delete a single task (requires explicit confirmation)
clickup_delete_task({
  task_id: "abc123",
  confirm_deletion: true  // Required safeguard
})
// Returns: Confirmation message with task name and warning

// Bulk delete multiple tasks
clickup_bulk_delete_tasks({
  task_ids: ["task1", "task2", "task3"],
  confirm_deletion: true,  // Required safeguard
  continue_on_error: true
})
// Returns: Detailed results with success/failure status for each task

// Delete a list (with enhanced safeguards)
clickup_delete_list({
  list_id: "list123",
  confirm_deletion: true  // Required safeguard - prevents accidental deletion
})
// Returns: Confirmation with list name and permanent deletion warning

Task Merging Operations

// Merge multiple tasks into one
clickup_merge_tasks({
  primary_task_id: "primary123",
  secondary_task_ids: ["secondary1", "secondary2"],
  merge_descriptions: true,
  merge_comments: true,
  merge_attachments: true,
  merge_time_tracking: true,
  confirm_merge: true  // Required safeguard
})
// Returns: Merge results with content summary and deletion confirmation

Real-time Webhook Processing

// Process ClickUp webhooks with HMAC validation
clickup_process_webhook({
  payload: webhookData,
  validate_signature: true,
  signature: request.headers['x-signature'],
  secret: process.env.WEBHOOK_SECRET
})
// Returns: Structured event data with relationships and changes

📝 Markdown Examples

Creating a Task with Rich Description

// Task with markdown description using clickup_create_task
{
  "list_id": "123456789",
  "name": "Project Documentation",
  "description": `# Project Overview

This project implements **advanced features** for our application.

## Key Components

1. **Authentication System**
   - JWT token management
   - Role-based access control

2. **API Integration**
   - RESTful endpoints
   - Real-time updates

## Code Example

\`\`\`typescript
interface User {
  id: string;
  name: string;
  role: 'admin' | 'user';
}
\`\`\`

## Next Steps

- [x] Set up project structure
- [ ] Complete authentication module
- [ ] Implement API endpoints

> **Note**: This is a high-priority project.`
}

Adding a Formatted Comment

// Comment with markdown formatting using clickup_create_task_comment
{
  "task_id": "868f9p3bg",
  "comment_text": `## Status Update ✅

### Completed
- Authentication system implementation
- Database schema design

### In Progress
- **API Integration**: Currently working on REST endpoints

### Code Changes
\`\`\`diff
+ Added user authentication middleware
+ Implemented JWT token validation
- Removed deprecated login method
\`\`\`

**Estimated Completion**: End of week`
}

🚀 Easy Installation

Option 1: One-Click Installer (Recommended)

Download and run the automated installer:

curl -O https://raw.githubusercontent.com/Chykalophia/ClickUp-MCP-Server---Enhanced/main/clickup-installer.js
node clickup-installer.js

Or via NPX:

npx clickup-mcp-installer

Option 2: Web Configurator

Visit the web-based configurator for visual setup: ClickUp MCP Configurator

1. Enter your ClickUp API token
2. Download the generated config file
3. Place it in your Claude Desktop config directory

Option 3: NPM Package (Manual Setup)

Use the published npm package - no build required:

@chykalophia/clickup-mcp-server

Option 4: Build from Source

For development or customization:

git clone https://github.com/Chykalophia/ClickUp-MCP-Server---Enhanced.git
cd ClickUp-MCP-Server---Enhanced
npm install
npm run build

Get ClickUp API Token

1. Log in to ClickUp account
2. Go to Settings > Apps
3. Click "Generate API Token"
4. Copy the token

Configuration

Add to the MCP settings file:

🚀 Quick Setup Configuration

NPM Package (Recommended) ⭐

{
  "mcpServers": {
    "clickup": {
      "command": "npx",
      "args": ["-y", "@chykalophia/clickup-mcp-server@latest"],
      "env": {
        "CLICKUP_API_TOKEN": "YOUR_API_TOKEN_HERE"
      }
    }
  }
}

Keep the @latest. Without a version specifier, npx runs a matching binary already on your $PATH instead of fetching from the registry. If you have ever run npm install -g @chykalophia/clickup-mcp-server, that global copy wins silently and the server never updates — no error, it just keeps serving the old version. A version specifier (@latest or @6.0.1) bypasses the $PATH binary. To check what is actually running, look at the version reported in the MCP handshake rather than trusting the config.

🔧 Build from Source (Advanced Users)

If you prefer to build from source, point your client at the built server:

{
  "mcpServers": {
    "clickup": {
      "command": "node",
      "args": ["/path/to/ClickUp-MCP-Server---Enhanced/packages/core/build/index-enhanced.js"],
      "env": {
        "CLICKUP_API_TOKEN": "YOUR_API_TOKEN_HERE"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

There is a single server. build/index-enhanced.js is the entry point; the clickup-mcp-server-basic, clickup-mcp-server-enhanced and clickup-mcp-server-efficiency bins (and build/index.js / build/index-efficiency-simple.js) are aliases of it, kept so existing configs keep working. They all expose the same tools.

📝 Configuration Notes

• Replace YOUR_API_TOKEN_HERE with your actual ClickUp API token
• NPM method requires no installation or cloning - the package is downloaded automatically
• Build from source requires cloning this repository and running npm run build
• Local file uploads are off by default. clickup_upload_attachment only accepts file_path when you set CLICKUP_UPLOAD_DIR to a directory (e.g. "CLICKUP_UPLOAD_DIR": "/Users/me/clickup-uploads"); the resolved path, after following symlinks, must stay inside it. file_data (base64) and file_url work without it. file_url must resolve to a public address: private, loopback, link-local, CGNAT and cloud-metadata addresses (IPv4 and IPv6) are refused, and every redirect hop is re-checked.

Tool Loading (CLICKUP_TOOL_MODE, CLICKUP_TOOLSETS)

Changed in 7.0.0: the server registers every tool but publishes only a core set on connect — 17 tools, ~29 KB of tools/list instead of ~173 KB. Everything else stays one call away through three always-on catalog tools:

• clickup_list_toolsets — every toolset, its tools, and whether it is enabled (include_schemas: true with a toolset returns full input schemas)
• clickup_enable_toolset — switch toolsets on or off at runtime; the client is notified via notifications/tools/list_changed
• clickup_call_tool — run any tool by name, enabled or not, with the same strict parameter validation as a direct call

Variable	Effect
CLICKUP_TOOL_MODE=core	Default. Core tools + catalog tools.
CLICKUP_TOOL_MODE=all	Every tool, as in 6.x (with CLICKUP_TOOLSETS unset or all; named toolsets narrow it to exactly those).
CLICKUP_TOOLSETS=goals,time	Add whole toolsets or profiles to core (all = everything).

Toolsets: tasks, lists, comments, custom-fields, docs, workspace, bulk, attachments, time-tracking, goals, views, webhooks, checklists, chat, spaces, dependencies. Profiles: pm (tasks, comments, lists, custom-fields, checklists, dependencies), time, chat, docs, admin (spaces, views, webhooks, goals, workspace).

{
  "mcpServers": {
    "clickup": {
      "command": "npx",
      "args": ["-y", "@chykalophia/clickup-mcp-server@latest"],
      "env": {
        "CLICKUP_API_TOKEN": "YOUR_API_TOKEN_HERE",
        "CLICKUP_TOOLSETS": "pm,time"
      }
    }
  }
}

Every tool also carries MCP annotations (title, read-only / destructive / idempotent hints), and destructive tools ask for confirmation when the client advertises form elicitation (elicitation.form, or the older empty elicitation: {}; CLICKUP_CONFIRM_DESTRUCTIVE=false turns that off). Resources are always registered. CLICKUP_DEBUG_TOOLS=true adds the raw-API debugging tool clickup_create_task_comment_raw_test.

Full details: docs/guides/TOOL_LOADING.md.

Parameter Handling

Unknown parameters are rejected

Every tool validates its arguments strictly. A parameter name the tool does not declare is an error naming the offending key, the closest valid name when one is close enough, and the full valid set:

MCP error -32602: Unknown parameter(s) for clickup_create_task: markdown_contnet.
"markdown_contnet" -> did you mean "markdown_content"?
Valid parameters: list_id, name, description, markdown_content, ...

Before v6.2.0 an unknown key was silently discarded and the operation ran anyway, so a misspelled description produced a real task with an empty body and a success response. Note that the JSON Schema this server publishes has always declared additionalProperties: false; strict validation makes the runtime obey the contract it was already advertising, rather than adding a new restriction.

Alternative parameter names are accepted

Where this server's parameter name differs from ClickUp's public API or from Anthropic's first-party ClickUp MCP, both names work. The alias is renamed to the canonical name before the tool runs, so nothing is sent twice.

Alias	Canonical	Where
workspace_id	team_id	any tool taking team_id (42 tools)
team_id	workspace_id	any tool taking workspace_id (39 tools)
document_id	doc_id	the doc tools (7 tools)
markdown_description	markdown_content	clickup_create_task, clickup_update_task
folder_ids	project_ids	clickup_get_filtered_team_tasks
task_id, source_task_ids	primary_task_id, secondary_task_ids	clickup_merge_tasks

workspace_id / team_id is bidirectional because the split is internal too: this server's own tools are divided between the two spellings for the same workspace ID. Both now work everywhere rather than renaming half the surface.

Where a canonical parameter was required and has an alias, the schema marks it optional and its description says Required unless <alias> is given instead; supplying neither is still an error. Aliases are renames only — parameters that differ in type from the first-party server (priority, due_date, time_estimate, assignees, start/stop) are deliberately not aliased, since coercing values silently is the failure mode this release exists to remove. See packages/core/src/utils/param-aliases.ts for the full table and the reasoning.

Configuration File Locations

• Cline VSCode Extension: ~/.vscode/extensions/saoudrizwan.claude-dev/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Claude Desktop Apps:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Examples

See the examples/ folder for:

• Basic MCP client usage
• Tool integration patterns
• Authentication setup
• Advanced workflows

Run examples with: node examples/basic-usage.js

🔒 Security Features

Production-Grade Security

• Input Validation: XSS and injection prevention with comprehensive sanitization
• API Token Security: Format validation, secure storage, character validation
• Rate Limiting: Sliding window implementation (1000 API, 100 webhook, 10 upload/min)
• HMAC Validation: Timing-safe webhook signature verification
• File Security: Local file uploads disabled unless CLICKUP_UPLOAD_DIR is set; symlink-safe containment inside that directory; upload size limits
• URL Validation: SSRF prevention — http(s) only, DNS-resolved addresses checked against private/loopback/link-local/metadata ranges (IPv4 and IPv6), redirects re-validated per hop
• Error Handling: Secure responses without information leakage

Security Testing

• 85+ Test Cases covering all security scenarios
• Zero Vulnerabilities in dependency audit
• Comprehensive Integration Tests for real-world validation
• Security Headers implementation for HTTP protection

📝 Markdown Support

GitHub Flavored Markdown Features

• Headers: # H1 through ###### H6
• Text Formatting: **bold**, *italic*, ~~strikethrough~~
• Code: inline code and fenced blocks with syntax highlighting
• Lists: Ordered, unordered, and task lists with - [ ] checkboxes
• Links & Images: [text](url) and ![alt](image-url)
• Tables: Full table support with alignment
• Blockquotes: > quoted text and nested quotes

Smart Processing

• Auto-Detection: Identifies markdown, HTML, or plain text content
• Bidirectional Conversion: Seamless markdown ↔ HTML ↔ plain text
• ClickUp Optimization: Prepares content in format ClickUp expects
• Response Processing: Converts ClickUp responses to readable markdown

🔔 Webhook Processing

Real-time Integration

• Event Processing: Handle all ClickUp events (tasks, comments, goals, etc.)
• HMAC Validation: Secure signature verification with timing-safe comparison
• Event Analysis: Extract relationships, changes, and context from payloads
• Monitoring: Event history, statistics, and retry mechanisms

Supported Events

• Task Events: Created, updated, deleted, status changed, assigned
• Comment Events: Posted, updated, threaded discussions
• Time Events: Time tracked, timer started/stopped
• Goal Events: Created, updated, target progress
• Workspace Events: Lists, folders, spaces created/updated/deleted

Development

Environment Requirements

• Node.js: Version 18.14.0 or higher
• Package Manager: npm or yarn
• IDE: VSCode recommended with TypeScript support

Setup

# Clone and install
git clone https://github.com/Chykalophia/ClickUp-MCP-Server---Enhanced.git
cd ClickUp-MCP-Server---Enhanced
npm install

# Environment configuration
cp .env.example .env
# Edit .env with your CLICKUP_API_TOKEN

Building

npm run build

Running Tests

npm test

Testing Markdown Features

# Test markdown functionality specifically
npm test -- --testPathPatterns=markdown

# Run all tests with coverage
npm run test:coverage

Release Procedure

Pre-release Checklist

1. Ensure all changes are committed and pushed
2. Verify all tests pass: npm test
3. Check build process works: npm run build
4. Update CHANGELOG.md with new version details

Version Update Process

1. Update package.json version following semantic versioning:

   • MAJOR: Incompatible API changes
   • MINOR: New functionality (backward compatible)
   • PATCH: Bug fixes (backward compatible)

2. Update CHANGELOG.md:

   ## [1.12.0] - 2025-04-14
   ### Added
   - New feature descriptions
   ### Changed
   - Modified functionality
   ### Fixed
   - Bug fixes
   

Release Steps

1. Build and Test:

   npm run build
   npm test
   

2. Create Git Tag:

   git tag -a v1.12.0 -m "Release v1.12.0: Brief description"
   git push --tags
   

3. Publish to NPM:

   npm publish --access public
   

4. Create GitHub Release:

   gh release create v1.12.0 --title "v1.12.0" --notes "Release notes from CHANGELOG.md"
   

Post-release Verification

• Check npm package: https://www.npmjs.com/package/@chykalophia/clickup-mcp-server
• Verify GitHub release: https://github.com/Chykalophia/ClickUp-MCP-Server---Enhanced/releases
• Test installation: npm install @chykalophia/clickup-mcp-server@latest

🔧 Technical Architecture

Enhanced Client System

• Base Client: Secure ClickUp API client with axios integration
• Specialized Clients: 9 enhanced clients for different feature areas
• Type Safety: Comprehensive TypeScript schemas with Zod validation
• Error Handling: Structured error responses with user-friendly messages

Performance & Scalability

• Efficient Operations: Bulk operations for multiple items in single requests
• Pagination Support: Handle large datasets efficiently
• Memory Management: Automatic cleanup and optimization
• Caching Strategy: Optimized API usage patterns

Testing Framework

• Security Tests: 47 test cases covering all attack vectors
• Integration Tests: 15 test cases for end-to-end validation
• Error Handling Tests: 23 test cases for robust error processing
• Total Coverage: 85+ test cases with 80%+ code coverage

License

MIT

🎯 Production Readiness

Quality Assurance

• Security Level: HIGH - Production approved with zero vulnerabilities
• Code Quality: TypeScript strict mode, comprehensive validation
• Test Coverage: Security-focused testing with 85+ test cases
• Documentation: Complete guides with security audit and examples

Deployment Features

• Health Checks: Built-in monitoring endpoints
• Environment Validation: Secure configuration verification
• Logging & Monitoring: Structured logging with security event tracking
• Error Recovery: Automatic retry mechanisms and conflict resolution

Performance Metrics

• API Call Reduction: 50-70% fewer calls for common workflows
• Execution Speed: 40-60% faster completion times
• Memory Efficiency: <1% security overhead, optimized resource usage
• Scalability: Supports high concurrency with efficient batch processing

🤔 What is MCP and How Do You Use It?

MCP (Model Context Protocol) is a protocol that allows AI assistants (like Claude, ChatGPT, etc.) to access external tools and data sources. Unlike traditional applications with user interfaces, MCP tools are accessed through AI conversations.

🎯 How to Access Your New AI Intelligence Tools

Method 1: Claude Desktop (Recommended)

Step 1: Install the Intelligence Package

npm install @chykalophia/clickup-intelligence-mcp-server

Step 2: Configure Claude Desktop

Add this to your Claude Desktop configuration file:

Location:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Configuration:

{
  "mcpServers": {
    "clickup-intelligence": {
      "command": "npx",
      "args": ["-y", "@chykalophia/clickup-intelligence-mcp-server"],
      "env": {
        "CLICKUP_API_TOKEN": "YOUR_CLICKUP_API_TOKEN_HERE"
      }
    }
  }
}

Step 3: Restart Claude Desktop

Step 4: Use the Tools in Conversation

Simply ask Claude to analyze your ClickUp projects:

"Can you analyze the health of my ClickUp workspace? The workspace ID is 12345678"

Method 2: Other MCP-Compatible AI Assistants

The same configuration works with any MCP-compatible AI assistant:

• Cline (VS Code extension)
• Continue.dev
• Other MCP clients

🛠️ Available AI Intelligence Tools

1. Project Health Analyzer (clickup_analyze_project_health)

What it does: Provides comprehensive project health analysis with AI-powered insights.

How to use:

"Analyze the health of my ClickUp project. Workspace ID: 12345678, Space ID: 87654321"

Parameters:

• workspace_id (required): Your ClickUp workspace ID
• space_id (optional): Specific space to analyze
• list_id (optional): Specific list to analyze
• include_archived (optional): Include archived tasks (default: false)
• analysis_depth (optional): "basic", "detailed", or "comprehensive" (default: "detailed")

What you get:

• Overall health score (0-100) with letter grade
• Executive dashboard with key metrics
• Risk assessment with severity levels
• Actionable recommendations (immediate, short-term, long-term)
• Trend analysis for velocity, quality, and timeline
• Workload distribution analysis
• Dependency health evaluation

📋 Example Conversations

Basic Health Analysis

You: "Can you check the health of my ClickUp workspace 12345678?"

Claude: I'll analyze your ClickUp workspace health using our AI-powered analyzer.
[Runs clickup_analyze_project_health with workspace_id: "12345678"]

[Returns comprehensive health report with scores, risks, and recommendations]

Detailed Analysis with Specific Scope

You: "I want a comprehensive analysis of list 98765432 in workspace 12345678, including archived tasks"

Claude: I'll perform a comprehensive health analysis of that specific list.
[Runs clickup_analyze_project_health with detailed parameters]

[Returns in-depth analysis focused on that list]

🔧 Getting Your ClickUp API Token

1. Log in to your ClickUp account
2. Go to Settings → Apps
3. Click Generate API Token
4. Copy the token and use it in your MCP configuration

🎯 No Traditional Interface Needed!

Key Point: These are conversational AI tools, not traditional software with buttons and menus. You interact with them by:

1. Asking questions in natural language
2. Requesting analysis of your ClickUp data
3. Getting insights through AI-generated reports
4. Following up with additional questions

🔍 Troubleshooting

"Tool not found" Error

• Ensure the MCP server is properly configured in Claude Desktop
• Restart Claude Desktop after configuration changes
• Verify your ClickUp API token is valid

"Access denied" Error

• Check that your ClickUp API token has the necessary permissions
• Verify the workspace/space/list IDs are correct
• Ensure you have access to the specified ClickUp resources

"Analysis failed" Error

• Try with a smaller scope (specific list instead of entire workspace)
• Check that the workspace contains tasks to analyze
• Verify your internet connection for ClickUp API access

---

Status: ✅ PRODUCTION READY - Comprehensive ClickUp integration with AI-powered efficiency, production-grade security, and complete API coverage. Ready for immediate deployment and enterprise use.