Skip to main content
Glama
helbertparanhos

clickup-mcp-pro

by helbertparanhos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to clickup-mcp-pro

No user-submitted related servers found.

    Related Servers

    • clickup-mcp

      MohanadAlrefaai
      A
      license
      B
      quality
      B
      maintenance
      A Model Context Protocol (MCP) server exposing the full ClickUp REST API v2 as MCP tools, enabling natural language management of ClickUp workspaces, spaces, folders, lists, tasks, custom fields, comments, goals, views, webhooks, and time tracking via any MCP-compatible client like Claude Desktop or Cursor.
      97
      25 npm
      MIT

    • ClickUp MCP Server

      BusyBee3333
      F
      license
      Not graded
      quality
      D
      maintenance
      Complete Model Context Protocol server for ClickUp, enabling interaction with tasks, spaces, lists, docs, goals, time tracking, and more through 93 tools and 18 React MCP apps.
      -

    • amazing-clickup-mcp

      trustxai
      A
      license
      A
      quality
      A
      maintenance
      A comprehensive MCP server for the ClickUp API exposing 166 tools to manage Spaces, Folders, Lists, Tasks, Docs, and more, enabling LLMs to read and drive a ClickUp Workspace.
      100
      1
      Apache 2.0

    • ClickUp MCP Sedrver

      nsxdavid
      A
      license
      B
      quality
      D
      maintenance
      ClickUp MCP Server enables AI assistants to seamlessly interact with your ClickUp workspace. This powerful integration allows Claude to create and manage tasks, access documents, organize folders and lists, add comments, and handle checklists—all through natural conversation.
      42
      307 npm
      43
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 162 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but there is notable redundancy: `set_custom_field_value` and `set_task_custom_field_value` are identical, as are `remove_custom_field_value` and `remove_task_custom_field_value`. This creates ambiguity for the agent.

    Naming Consistency4/5

    The naming pattern is largely verb_noun and consistent (create, get, update, delete, add, remove), but there are a few outliers like `clickup_raw`, `duplicate_task`, and `find_list_by_name` that deviate. Overall, minor inconsistencies.

    Tool Count2/5

    162 tools is excessively high for an MCP server. While it covers many features, the sheer number can overwhelm agents and make discovery difficult. A more focused or modular approach would be better.

    Completeness5/5

    The tool set is extremely comprehensive, covering all major ClickUp entities (tasks, lists, folders, spaces, workspaces, docs, chat, goals, time entries, guests, webhooks, views) with full CRUD and many specialized operations. No obvious gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources