@taazkareem/clickup-mcp-server 0.5.1 → 0.6.0

package/README.md

@@ -1,18 +1,12 @@
-<img src="https://clickup.com/assets/brand/logo-v3-clickup-dark.svg" alt="ClickUp" height="40" style="vertical-align: middle; margin-top: -4px;">
-
-# MCP Server
+<img src="assets/images/clickup_mcp_server_social_image.png" alt="ClickUp MCP Server" width="100%">
 
+![Total Supporters](https://img.shields.io/badge/🏆%20Total%20Supporters-2-gold)
 [![GitHub Stars](https://img.shields.io/github/stars/TaazKareem/clickup-mcp-server?style=flat&logo=github)](https://github.com/TaazKareem/clickup-mcp-server/stargazers)
-[![Maintenance](https://img.shields.io/badge/Maintained%3F-yes-green.svg)](https://github.com/TaazKareem/clickup-mcp-server/graphs/commit-activity)
+[![Maintenance](https://img.shields.io/badge/Maintained%3F-yes-brightgreen.svg)](https://github.com/TaazKareem/clickup-mcp-server/graphs/commit-activity)
 
 A Model Context Protocol (MCP) server for integrating ClickUp tasks with AI applications. This server allows AI agents to interact with ClickUp tasks, spaces, lists, and folders through a standardized protocol.
 
-
-> 🚧 **Status Update:** -v0.5.1 beta release with new Attach Task Files tool, Create Task Comments tool, Get Task Comments tool, and Custom ID support across all tools.
-
-
-
-
+> 🚧 **Status Update:** v0.5.2 release with new Attach Task Files tool, Create Task Comments tool, Get Task Comments tool, Custom ID support across all tools, and Subtasks support.
 
 ## Setup
 
@@ -26,13 +20,13 @@ A Model Context Protocol (MCP) server for integrating ClickUp tasks with AI appl
 
 [![smithery badge](https://smithery.ai/badge/@TaazKareem/clickup-mcp-server)](https://smithery.ai/server/@TaazKareem/clickup-mcp-server)
 
-The server is hosted on Smithery. There, you can preview the available tools or copy the commands to run on your specific client app. 
+The server is hosted on [Smithery](https://smithery.ai/server/@TaazKareem/clickup-mcp-server). There, you can preview the available tools or copy the commands to run on your specific client app. 
 
 
 ## NPX Installation
 
 [![NPM Version](https://img.shields.io/npm/v/@taazkareem/clickup-mcp-server.svg?style=flat&logo=npm)](https://www.npmjs.com/package/@taazkareem/clickup-mcp-server)
-[![Dependency Status](https://img.shields.io/librariesio/github/TaazKareem/clickup-mcp-server)](https://libraries.io/github/TaazKareem/clickup-mcp-server)
+[![Dependency Status](https://img.shields.io/badge/dependencies-up%20to%20date-brightgreen)](https://github.com/TaazKareem/clickup-mcp-server/blob/main/package.json)
 [![NPM Downloads](https://img.shields.io/npm/dm/@taazkareem/clickup-mcp-server.svg?style=flat&logo=npm)](https://npmcharts.com/compare/@taazkareem/clickup-mcp-server?minimal=true)
 
 Add this entry to your client's MCP settings JSON file:
@@ -69,6 +63,7 @@ Or use this npx command:
   - Get task comments
   - Set due dates using natural language and relative time expressions
   - Attach files to tasks using local file paths, URL, base64, or chunked uploads
+  - Create and manage subtasks with support for multi-level nesting
 
 - 📂 **Workspace Organization**
   - Complete workspace hierarchy (spaces, folders, lists)
@@ -86,12 +81,12 @@ Or use this npx command:
 | Tool | Description | Required Parameters |
 |------|-------------|-------------------|
 | [get_workspace_hierarchy](docs/api-reference.md#workspace-navigation) | Get workspace structure | None |
-| [create_task](docs/api-reference.md#task-management) | Create a task | `name`, (`listId`/`listName`) |
+| [create_task](docs/api-reference.md#task-management) | Create a task | `name`, (`listId`/`listName`), optional `parent` |
 | [create_bulk_tasks](docs/api-reference.md#task-management) | Create multiple tasks | `tasks[]` |
 | [update_task](docs/api-reference.md#task-management) | Modify task | `taskId`/`taskName` |
 | [update_bulk_tasks](docs/api-reference.md#task-management) | Update multiple tasks | `tasks[]` with IDs or names |
-| [get_tasks](docs/api-reference.md#task-management) | Get tasks from list | `listId`/`listName` |
-| [get_task](docs/api-reference.md#task-management) | Get task details | `taskId`/`taskName` |
+| [get_tasks](docs/api-reference.md#task-management) | Get tasks from list | `listId`/`listName`, optional `subtasks` |
+| [get_task](docs/api-reference.md#task-management) | Get task details | `taskId`/`taskName`, optional `subtasks` |
 | [get_task_comments](docs/api-reference.md#task-management) | Get comments on a task | `taskId`/`taskName` |
 | [create_task_comment](docs/api-reference.md#task-management) | Add a comment to a task | `commentText`, (`taskId`/(`taskName`+`listName`)) |
 | [attach_task_file](docs/api-reference.md#task-management) | Attach file to a task | `taskId`/`taskName`, (`file_data` or `file_url`) |
@@ -112,8 +107,8 @@ Or use this npx command:
 
 See [full documentation](docs/api-reference.md) for optional parameters and advanced usage.
 
-## Available Prompts
-Not yet implemented (or needed) For now, you can send a follow up prompt after the tool result.
+## Prompts
+Not yet implemented and not supported by all client apps. Request a feature for a Prompt implementation that would be most beneficial for your workflow (without it being too specific). Examples:
 
 | Prompt | Purpose | Features |
 |--------|---------|----------|
@@ -131,6 +126,9 @@ The server provides clear error messages for:
 - API errors
 - Rate limiting
 
+The `LOG_LEVEL` environment variable can be specified to control the verbosity of server logs. Valid values are `trace`, `debug`, `info`, `warn`, and `error` (default).
+This can be also be specified on the command line as, e.g. `--env LOG_LEVEL=info`.
+
 ## Support the Developer
 
 When using this server, you may occasionally see a small sponsor message with a link to this repository included in tool responses. I hope you can support the project!
@@ -138,10 +136,12 @@ If you find this project useful, please consider supporting:
 
 [![Sponsor TaazKareem](https://img.shields.io/badge/Sponsor-TaazKareem-orange?logo=github)](https://github.com/sponsors/TaazKareem)
 
+
 <a href="https://buymeacoffee.com/taazkareem">
   <img src="https://cdn.buymeacoffee.com/buttons/v2/default-yellow.png" width="200" alt="Buy Me A Coffee">
 </a>
 
+
 ## Acknowledgements
 
 Special thanks to [ClickUp](https://clickup.com) for their excellent API and services that make this integration possible.
@@ -158,7 +158,7 @@ This project is licensed under the MIT License - see the [LICENSE](LICENSE) file
 
 ## Disclaimer
 
-Disclaimer: This software makes use of third-party APIs and may reference trademarks
+This software makes use of third-party APIs and may reference trademarks
 or brands owned by third parties. The use of such APIs or references does not imply 
 any affiliation with or endorsement by the respective companies. All trademarks and 
 brand names are the property of their respective owners. This project is an independent

package/build/config.js

@@ -22,8 +22,7 @@ for (let i = 0; i < args.length; i++) {
 const configuration = {
     clickupApiKey: envArgs.clickupApiKey || process.env.CLICKUP_API_KEY || '',
     clickupTeamId: envArgs.clickupTeamId || process.env.CLICKUP_TEAM_ID || '',
-    enableSponsorMessage: process.env.ENABLE_SPONSOR_MESSAGE !== 'false',
-    sponsorUrl: process.env.SPONSOR_URL || 'https://github.com/sponsors/taazkareem'
+    enableSponsorMessage: process.env.ENABLE_SPONSOR_MESSAGE !== 'false'
 };
 // Validate only the required variables are present
 const requiredVars = ['clickupApiKey', 'clickupTeamId'];

package/build/index.js

@@ -1,37 +1,25 @@
 #!/usr/bin/env node
 /**
- * ClickUp MCP Server - A Model Context Protocol server for ClickUp integration
+ * ClickUp MCP Server
  *
- * This server enables AI applications to interact with ClickUp through a standardized protocol,
- * allowing AI assistants to manage tasks, lists, and folders in ClickUp workspaces.
+ * This custom server implements the Model Context Protocol (MCP) specification to enable
+ * AI applications to interact with ClickUp workspaces. It provides a standardized
+ * interface for managing tasks, lists, folders and other ClickUp entities using Natural Language.
  *
- * Key capabilities include:
+ * Key Features:
+ * - Complete task management (CRUD operations, moving, duplicating)
+ * - Workspace organization (spaces, folders, lists)
+ * - Bulk operations with concurrent processing
+ * - Natural language date parsing
+ * - File attachments support
+ * - Name-based entity resolution
+ * - Markdown formatting
+ * - Built-in rate limiting
  *
- * Task Management:
- * - Create, update, move and duplicate tasks with rich description support
- * - Find tasks by name with smart disambiguation
- * - Optimized bulk task operations with concurrent processing
- * - Comprehensive filtering and sorting options
- *
- * Workspace Organization:
- * - Navigate and discover workspace structure with hierarchical views
- * - Create and manage lists and folders with proper nesting
- * - Smart name-based lookups that eliminate the need for IDs
- * - Support for priorities, statuses, and due dates
- *
- * Technical Features:
- * - Full markdown support for rich text content
- * - Secure credential handling through configuration
- * - Comprehensive error reporting and validation
- * - Name-based entity resolution with fuzzy matching
- *
- * This implementation follows the Model Context Protocol specification and
- * is designed to be used with AI assistants that support MCP.
+ * For full documentation and usage examples, please refer to the README.md file.
  */
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 import { configureServer, server } from "./server.js";
-import { clickUpServices } from "./services/shared.js";
-import { initializeWorkspaceTool } from "./tools/workspace.js";
 import { info, error, warn } from "./logger.js";
 import { exec } from 'child_process';
 import { promisify } from 'util';
@@ -76,9 +64,6 @@ async function main() {
             os: process.platform,
             arch: process.arch
         });
-        // Initialize tools with services
-        info("Initializing workspace tools");
-        initializeWorkspaceTool(clickUpServices);
         // Configure the server with all handlers
         info("Configuring server request handlers");
         await configureServer();

package/build/logger.js

@@ -24,8 +24,35 @@ export var LogLevel;
     LogLevel[LogLevel["WARN"] = 3] = "WARN";
     LogLevel[LogLevel["ERROR"] = 4] = "ERROR";
 })(LogLevel || (LogLevel = {}));
-// Fixed log level - always use TRACE as the minimum level for complete logging
-const configuredLevel = LogLevel.TRACE;
+// Parse LOG_LEVEL environment variable or command line argument
+const parseLogLevel = (levelStr) => {
+    if (!levelStr)
+        return LogLevel.ERROR; // Default to ERROR if not specified
+    switch (levelStr.toUpperCase()) {
+        case 'TRACE': return LogLevel.TRACE;
+        case 'DEBUG': return LogLevel.DEBUG;
+        case 'INFO': return LogLevel.INFO;
+        case 'WARN': return LogLevel.WARN;
+        case 'ERROR': return LogLevel.ERROR;
+        default:
+            console.error(`Invalid LOG_LEVEL: ${levelStr}, defaulting to ERROR`);
+            return LogLevel.ERROR;
+    }
+};
+// Parse command line arguments for LOG_LEVEL
+const args = process.argv.slice(2);
+let argLogLevel;
+for (let i = 0; i < args.length; i++) {
+    if (args[i] === '--env' && i + 1 < args.length) {
+        const [key, value] = args[i + 1].split('=');
+        if (key === 'LOG_LEVEL')
+            argLogLevel = value;
+        i++;
+    }
+}
+// Get log level from environment variable or command line, default to ERROR
+const configuredLevel = parseLogLevel(argLogLevel || process.env.LOG_LEVEL);
+console.debug(`Log level set to: ${LogLevel[configuredLevel]}`);
 /**
  * Check if a log level is enabled based on the configured level
  * @param level The log level to check

package/build/server.js

@@ -15,7 +15,7 @@ const { workspace } = clickUpServices;
  */
 export const server = new Server({
     name: "clickup-mcp-server",
-    version: "0.5.1",
+    version: "0.6.0",
 }, {
     capabilities: {
         tools: {},
@@ -61,7 +61,7 @@ export function configureServer() {
     });
     // Register CallTool handler with proper logging
     logger.info("Registering tool handlers", {
-        toolCount: 23,
+        toolCount: 24,
         categories: ["workspace", "task", "list", "folder"]
     });
     server.setRequestHandler(CallToolRequestSchema, async (req) => {

package/build/services/clickup/task.js

@@ -204,6 +204,28 @@ export class TaskService extends BaseClickUpService {
             throw this.handleError(error, `Failed to get task ${taskId}`);
         }
     }
+    /**
+     * Get subtasks of a specific task
+     * @param taskId The ID of the parent task
+     * @returns Array of subtask details
+     */
+    async getSubtasks(taskId) {
+        this.logOperation('getSubtasks', { taskId });
+        try {
+            return await this.makeRequest(async () => {
+                // First, get the task to get its list ID
+                const task = await this.getTask(taskId);
+                const listId = task.list.id;
+                // Then get all tasks from the list
+                const allTasks = await this.getTasks(listId, { subtasks: true });
+                // Filter tasks that have the specified task as parent
+                return allTasks.filter(t => t.parent === taskId || t.top_level_parent === taskId);
+            });
+        }
+        catch (error) {
+            throw this.handleError(error, `Failed to get subtasks of task ${taskId}`);
+        }
+    }
     /**
      * Get a specific task by its custom ID
      * @param customTaskId The custom ID of the task (e.g., "DEV-1234")
@@ -214,8 +236,11 @@ export class TaskService extends BaseClickUpService {
         this.logOperation('getTaskByCustomId', { customTaskId, listId });
         try {
             return await this.makeRequest(async () => {
-                // Build query with custom_task_ids=true
-                const params = new URLSearchParams({ custom_task_ids: 'true' });
+                // Build query with custom_task_ids=true and team_id
+                const params = new URLSearchParams({
+                    custom_task_ids: 'true',
+                    team_id: this.teamId
+                });
                 // Use the ClickUp API endpoint for retrieving tasks by ID
                 // With custom_task_ids=true parameter, it will treat the ID as a custom ID
                 const response = await this.client.get(`/task/${customTaskId}?${params.toString()}`);

package/build/tools/task/handlers.js

@@ -83,7 +83,7 @@ async function mapTaskIds(tasks) {
  * Handler for creating a task
  */
 export async function createTaskHandler(params) {
-    const { name, description, markdown_description, status, dueDate } = params;
+    const { name, description, markdown_description, status, dueDate, parent } = params;
     if (!name)
         throw new Error("Task name is required");
     // Use our helper function to validate and convert priority
@@ -95,7 +95,8 @@ export async function createTaskHandler(params) {
         markdown_description,
         status,
         priority,
-        due_date: dueDate ? parseDueDate(dueDate) : undefined
+        due_date: dueDate ? parseDueDate(dueDate) : undefined,
+        parent
     });
 }
 /**
@@ -131,6 +132,12 @@ export async function duplicateTaskHandler(params) {
 export async function getTaskHandler(params) {
     // resolveTaskIdWithValidation now auto-detects whether taskId is a regular ID or custom ID
     const taskId = await getTaskId(params.taskId, params.taskName, params.listName, params.customTaskId);
+    // If subtasks parameter is provided and true, use the getTaskWithSubtasks method
+    if (params.subtasks) {
+        const task = await taskService.getTask(taskId);
+        const subtasks = await taskService.getSubtasks(taskId);
+        return { ...task, subtasks };
+    }
     return await taskService.getTask(taskId);
 }
 /**
@@ -140,14 +147,6 @@ export async function getTasksHandler(params) {
     const listId = await getListId(params.listId, params.listName);
     return await taskService.getTasks(listId, buildTaskFilters(params));
 }
-/**
- * Handler for deleting a task
- */
-export async function deleteTaskHandler(params) {
-    const taskId = await getTaskId(params.taskId, params.taskName, params.listName);
-    await taskService.deleteTask(taskId);
-    return true;
-}
 /**
  * Handler for getting task comments
  */
@@ -242,3 +241,11 @@ export async function deleteBulkTasksHandler(params) {
     await bulkService.deleteTasks(taskIds, parseBulkOptions(params.options));
     return taskIds.map(() => true);
 }
+/**
+ * Handler for deleting a task
+ */
+export async function deleteTaskHandler(params) {
+    const taskId = await getTaskId(params.taskId, params.taskName, params.listName);
+    await taskService.deleteTask(taskId);
+    return true;
+}

package/build/tools/task/single-operations.js

@@ -57,7 +57,8 @@ Requirements:
 
 Notes:
 - For multiple tasks, use create_bulk_tasks instead
-- Reuse list IDs from previous responses when possible to avoid redundant lookups`,
+- Reuse list IDs from previous responses when possible to avoid redundant lookups
+- To create a subtask, set the parent parameter to the ID of the parent task`,
     inputSchema: {
         type: "object",
         properties: {
@@ -92,6 +93,10 @@ Notes:
             dueDate: {
                 type: "string",
                 description: "Optional due date. Supports Unix timestamps (ms) or natural language like '1 hour from now', 'tomorrow', 'next week', etc."
+            },
+            parent: {
+                type: "string",
+                description: "Optional ID of the parent task. When specified, this task will be created as a subtask of the specified parent task."
             }
         }
     }
@@ -269,7 +274,8 @@ Requirements:
 Note:
 - Task names are only unique within a list, so the system needs to know which list to search in
 - Regular task IDs are always 9 characters long (e.g., "86b394eqa")
-- Custom IDs have an uppercase prefix followed by a hyphen and number (e.g., "DEV-1234")`,
+- Custom IDs have an uppercase prefix followed by a hyphen and number (e.g., "DEV-1234")
+- Set subtasks=true to include all subtasks in the response`,
     inputSchema: {
         type: "object",
         properties: {
@@ -288,6 +294,10 @@ Note:
             customTaskId: {
                 type: "string",
                 description: "Custom task ID (e.g., 'DEV-1234'). Only use this if you want to explicitly force custom ID lookup. In most cases, you can just use taskId which auto-detects ID format."
+            },
+            subtasks: {
+                type: "boolean",
+                description: "Whether to include subtasks in the response. Set to true to retrieve full details of all subtasks."
             }
         },
         required: []
@@ -322,6 +332,15 @@ Notes:
                 type: "string",
                 description: "Name of list to get tasks from. Only use if you don't have listId."
             },
+            subtasks: {
+                type: "boolean",
+                description: "Include subtasks"
+            },
+            statuses: {
+                type: "array",
+                items: { type: "string" },
+                description: "Filter by status names (e.g. ['To Do', 'In Progress'])"
+            },
             archived: {
                 type: "boolean",
                 description: "Include archived tasks"
@@ -337,55 +356,11 @@ Notes:
             reverse: {
                 type: "boolean",
                 description: "Reverse sort order (descending)"
-            },
-            subtasks: {
-                type: "boolean",
-                description: "Include subtasks"
-            },
-            statuses: {
-                type: "array",
-                items: {
-                    type: "string"
-                },
-                description: "Filter by status names (e.g. ['To Do', 'In Progress'])"
             }
         },
         required: []
     }
 };
-/**
- * Tool definition for deleting a task
- */
-export const deleteTaskTool = {
-    name: "delete_task",
-    description: `Purpose: PERMANENTLY DELETE a task.
-
-Valid Usage:
-1. Use taskId alone (preferred and safest)
-2. Use taskName + optional listName
-
-Warning:
-- This action CANNOT be undone
-- Using taskName is risky as names may not be unique
-- Provide listName when using taskName for more precise targeting`,
-    inputSchema: {
-        type: "object",
-        properties: {
-            taskId: {
-                type: "string",
-                description: "ID of task to delete (preferred). Works with both regular task IDs (9 characters) and custom IDs with uppercase prefixes (like 'DEV-1234')."
-            },
-            taskName: {
-                type: "string",
-                description: "Name of task to delete. Use with extreme caution as names may not be unique."
-            },
-            listName: {
-                type: "string",
-                description: "Name of list containing the task. Helps ensure correct task deletion when using taskName."
-            }
-        }
-    }
-};
 /**
  * Tool definition for retrieving task comments
  */
@@ -477,3 +452,36 @@ Notes:
         required: ["commentText"]
     }
 };
+/**
+ * Tool definition for deleting a task
+ */
+export const deleteTaskTool = {
+    name: "delete_task",
+    description: `Purpose: PERMANENTLY DELETE a task.
+
+Valid Usage:
+1. Use taskId alone (preferred and safest)
+2. Use taskName + optional listName
+
+Warning:
+- This action CANNOT be undone
+- Using taskName is risky as names may not be unique
+- Provide listName when using taskName for more precise targeting`,
+    inputSchema: {
+        type: "object",
+        properties: {
+            taskId: {
+                type: "string",
+                description: "ID of task to delete (preferred). Works with both regular task IDs (9 characters) and custom IDs with uppercase prefixes (like 'DEV-1234')."
+            },
+            taskName: {
+                type: "string",
+                description: "Name of task to delete. Use with extreme caution as names may not be unique."
+            },
+            listName: {
+                type: "string",
+                description: "Name of list containing the task. Helps ensure correct task deletion when using taskName."
+            }
+        }
+    }
+};

package/build/tools/workspace.js

@@ -6,11 +6,11 @@
  */
 import { Logger } from '../logger.js';
 import { sponsorService } from '../utils/sponsor-service.js';
+import { clickUpServices } from '../services/shared.js';
 // Create a logger for workspace tools
 const logger = new Logger('WorkspaceTool');
-// Use the workspace service imported from the server
-// This is defined when server.ts imports this module
-let workspaceService;
+// Use the workspace service from the shared services
+const { workspace: workspaceService } = clickUpServices;
 /**
  * Tool definition for retrieving the complete workspace hierarchy
  */
@@ -33,20 +33,6 @@ Notes:
         properties: {}
     }
 };
-/**
- * Initialize the tool with services
- */
-export function initializeWorkspaceTool(services) {
-    logger.info('Initializing workspace tool');
-    if (!services || !services.workspace) {
-        logger.error('Failed to initialize workspace tool: services not provided');
-        throw new Error('Workspace service not available');
-    }
-    workspaceService = services.workspace;
-    logger.info('Workspace tool initialized successfully', {
-        serviceType: workspaceService.constructor.name
-    });
-}
 /**
  * Handler for the get_workspace_hierarchy tool
  */
@@ -56,40 +42,13 @@ export async function handleGetWorkspaceHierarchy() {
         const hierarchy = await workspaceService.getWorkspaceHierarchy();
         // Generate tree representation
         const treeOutput = formatTreeOutput(hierarchy);
-        return sponsorService.createResponse({
-            hierarchy: treeOutput
-        }, true);
+        // Use sponsor service to create the response with optional sponsor message
+        return sponsorService.createResponse({ hierarchy: treeOutput }, true);
     }
     catch (error) {
         return sponsorService.createErrorResponse(`Error getting workspace hierarchy: ${error.message}`);
     }
 }
-/**
- * Format the hierarchy for the response
- */
-function formatHierarchyResponse(hierarchy) {
-    try {
-        const treeOutput = formatTreeOutput(hierarchy);
-        return {
-            content: [
-                {
-                    type: "text",
-                    text: treeOutput
-                }
-            ]
-        };
-    }
-    catch (error) {
-        return {
-            content: [
-                {
-                    type: "text",
-                    text: `Error formatting workspace hierarchy: ${error.message}`
-                }
-            ]
-        };
-    }
-}
 /**
  * Format the hierarchy as a tree string
  */
@@ -114,5 +73,6 @@ function formatTreeOutput(hierarchy) {
     };
     // Generate tree representation
     const treeLines = formatNodeAsTree(hierarchy.root);
+    // Return plain text instead of adding code block markers
     return treeLines.join('\n');
 }

package/build/utils/sponsor-service.js

@@ -12,8 +12,8 @@ const logger = new Logger('SponsorService');
  */
 export class SponsorService {
     constructor() {
+        this.sponsorUrl = 'https://github.com/sponsors/taazkareem';
         this.isEnabled = config.enableSponsorMessage;
-        this.sponsorUrl = config.sponsorUrl;
         logger.info('SponsorService initialized', { enabled: this.isEnabled });
     }
     /**
@@ -56,7 +56,7 @@ export class SponsorService {
         if (this.isEnabled && includeSponsorMessage) {
             content.push({
                 type: "text",
-                text: `\n\n❤️ Support this project by sponsoring the developer at ${this.sponsorUrl}`
+                text: `⎯ Support this project by sponsoring the developer at ${this.sponsorUrl}`
             });
         }
         return { content };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@taazkareem/clickup-mcp-server",
-  "version": "0.5.1",
+  "version": "0.6.0",
   "description": "ClickUp MCP Server - Integrate ClickUp tasks with AI through Model Context Protocol",
   "type": "module",
   "main": "build/index.js",