MCP.so
Sign In

ClickUp MCP Server (Read-Only Version)

@ToSn0w

About ClickUp MCP Server (Read-Only Version)

No overview available yet

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "ClickUp": {
      "command": "npx",
      "args": [
        "-y",
        "@s.pawel940/clickup-mcp-server@latest"
      ],
      "env": {
        "CLICKUP_API_KEY": "your-api-key",
        "CLICKUP_TEAM_ID": "your-team-id",
        "DOCUMENT_SUPPORT": "true"
      }
    }
  }
}

Tools

16

Gets complete workspace hierarchy (spaces, folders, lists). No parameters needed. Returns tree structure with names and IDs for navigation.

Gets task details by taskId (works with regular/custom IDs) or taskName. For taskName search, provide listName for faster lookup. Set subtasks=true to include all subtask details.

Gets task comments. Use taskId (preferred) or taskName + optional listName. Use start/startId params for pagination. Task names may not be unique across lists.

Purpose: Retrieve tasks from across the entire workspace with powerful filtering options, including tag-based filtering. Valid Usage: 1. Apply any combination of filters (tags, lists, folders, spaces, statuses, etc.) 2. Use pagination to manage large result sets Requirements: - At least one filter parameter is REQUIRED (tags, list_ids, folder_ids, space_ids, statuses, assignees, or date filters) - Pagination parameters (page, order_by, reverse) alone are not considered filters Notes: - Provides workspace-wide task access (unlike get_tasks which only searches in one list) - Returns complete task details including descriptions, assignees, custom fields, and all metadata - Tag filtering is especially useful for cross-list organization (e.g., "project-x", "blocker", "needs-review") - Combine multiple filters to narrow down your search scope - Use pagination for large result sets - Use the detail_level parameter to control the amount of data returned: - "summary": Returns lightweight task data (name, status, list, tags) - "detailed": Returns complete task data with all fields (DEFAULT if not specified) - Responses exceeding 50,000 tokens automatically switch to summary format to avoid hitting LLM token limits

Gets all time entries for a task with filtering options. Use taskId (preferred) or taskName + optional listName. Returns all tracked time with user info, descriptions, tags, start/end times, and durations.

Gets the currently running time entry, if any. No parameters needed.

Gets details of a ClickUp list. Use listId (preferred) or listName. Returns list details including name, content, and space info. ListId more reliable as names may not be unique.

Gets folder details. Use folderId (preferred) or folderName + (spaceId/spaceName). Helps understand folder structure before creating/updating lists.

Gets all tags in a ClickUp space. Use spaceId (preferred) or spaceName. Tags are defined at space level - check available tags before adding to tasks.

Returns all members (users) in the ClickUp workspace/team. Useful for resolving assignees by name or email.

Finds a member in the ClickUp workspace by name or email. Returns the member object if found, or null if not found.

Resolves an array of assignee names or emails to ClickUp user IDs. Returns an array of user IDs, or errors for any that cannot be resolved.

Gets details of a ClickUp document. Use documentId (preferred) or search by title in a container.

Lists all documents in a ClickUp space, folder, or list.

Lists all pages in a document with optional depth control

Gets the content of specific pages from a document

Overview

What is ClickUp MCP Server (Read-Only Version)?

A read-only Model Context Protocol (MCP) server that integrates ClickUp tasks, spaces, lists, folders, documents, and time tracking with AI applications. It allows AI agents to retrieve information from ClickUp through a standardized protocol.

How to use ClickUp MCP Server (Read-Only Version)?

Install via Smithery (hosted), NPX (local with dependencies), or Docker (containerized). You need a ClickUp API key and Team ID. Configure environment variables (CLICKUP_API_KEY, CLICKUP_TEAM_ID, optionally DOCUMENT_SUPPORT, ENABLE_SSE, PORT, LOG_LEVEL, DISABLED_TOOLS) in your MCP client settings or command line. Then use natural language to query your workspace.

Key features of ClickUp MCP Server (Read-Only Version)

  • Task information retrieval
  • Workspace organization viewing (spaces, folders, lists)
  • Time tracking data access
  • Member information access
  • Document content viewing
  • Built-in rate limiting and error handling

Use cases of ClickUp MCP Server (Read-Only Version)

  • AI agents fetching task details and statuses
  • Automating workspace hierarchy exploration
  • Retrieving time entries and running timers
  • Searching for workspace members by name or email
  • Accessing document and page content from ClickUp Docs

FAQ from ClickUp MCP Server (Read-Only Version)

How do I install and configure the server?

Add the NPX command or Docker configuration to your MCP client settings, providing your ClickUp API key and Team ID as environment variables. You can also install via Smithery for a hosted option.

How do I enable document support?

Set the environment variable DOCUMENT_SUPPORT to true. The default is false, and document tools will not be available without this setting.

Can I run the server in SSE (Server-Sent Events) mode?

Yes. Set ENABLE_SSE to true and optionally specify a custom PORT (default 3231). Required for clients that need HTTP-based transport.

How do I disable specific tools?

Use the DISABLED_TOOLS environment variable with a comma‑separated list of tool names (e.g., create_task,delete_task). This helps reduce tool count for context limitations.

What authentication is required?

You must provide a valid ClickUp API key via the CLICKUP_API_KEY environment variable. The server connects to ClickUp’s API using this key and is read‑only.

Frequently asked questions

How do I install and configure the server?

Add the NPX command or Docker configuration to your MCP client settings, providing your ClickUp API key and Team ID as environment variables. You can also install via Smithery for a hosted option.

How do I enable document support?

Set the environment variable `DOCUMENT_SUPPORT` to `true`. The default is `false`, and document tools will not be available without this setting.

Can I run the server in SSE (Server-Sent Events) mode?

Yes. Set `ENABLE_SSE` to `true` and optionally specify a custom `PORT` (default 3231). Required for clients that need HTTP-based transport.

How do I disable specific tools?

Use the `DISABLED_TOOLS` environment variable with a comma‑separated list of tool names (e.g., `create_task,delete_task`). This helps reduce tool count for context limitations.

What authentication is required?

You must provide a valid ClickUp API key via the `CLICKUP_API_KEY` environment variable. The server connects to ClickUp’s API using this key and is read‑only.

Comments

More Other MCP servers