ClickUp MCP server for Claude, ChatGPT, Claude Code and Cursor

How to connect ClickUp

1. 1
   Click Connect ClickUp free and sign in to ClickUp.
2. 2
   Add ContextGate to your AI app:

   ClaudeChatGPTClaude CodeCursorGitHub CopilotCodexGemini CLIOther

   1. 1

      In Claude, open Settings → Connectors and click Add custom connector.

   2. 2

      Name it ContextGate and paste this URL:

      https://api.contextgate.ai/mcp

   3. 3

      Click Add, then Connect, and sign in to ContextGate.

   4. 4

      In a chat, turn ContextGate on from the + menu → Connectors. Cowork and the desktop app use the same connectors.

   The full Claude guide

   1. 1

      In ChatGPT settings, open Apps & Connectors (or Connectors) → Advanced and turn on Developer mode.

   2. 2

      Create a connector, choose OAuth, and paste this URL:

      https://api.contextgate.ai/mcp

   3. 3

      Sign in to ContextGate when ChatGPT redirects you, then pick the connector in a chat.

   The full ChatGPT guide

   1. 1

      Run this in a terminal:

      claude mcp add --transport http contextgate https://api.contextgate.ai/mcp

   2. 2

      Start Claude Code, run /mcp, choose contextgate and sign in to ContextGate.

   The full Claude Code guide

   Add to Cursor

   1. 1

      Click Add to Cursor, or add this to ~/.cursor/mcp.json:

      {
        "mcpServers": {
          "contextgate": {
            "url": "https://api.contextgate.ai/mcp"
          }
        }
      }

   2. 2

      In Cursor Settings → MCP, sign in to ContextGate when Cursor asks.

   The full Cursor guide

   Add to VS Code

   1. 1

      Click Add to VS Code, or add this to .vscode/mcp.json:

      {
        "servers": {
          "contextgate": {
            "type": "http",
            "url": "https://api.contextgate.ai/mcp"
          }
        }
      }

   2. 2

      Start the server when VS Code asks, sign in to ContextGate, and use it from Copilot Chat in Agent mode.

   The full GitHub Copilot guide

   1. 1

      Run this in a terminal:

      codex mcp add contextgate --url https://api.contextgate.ai/mcp

   2. 2

      Then sign in to ContextGate:

      codex mcp login contextgate

   The full Codex guide

   1. 1

      Run this in a terminal:

      gemini mcp add --transport http contextgate https://api.contextgate.ai/mcp

   2. 2

      In Gemini CLI, run /mcp auth contextgate and sign in to ContextGate.

   The full Gemini CLI guide

   1. 1

      Add a remote (HTTP) MCP server with this URL:

      https://api.contextgate.ai/mcp

   2. 2

      Apps that support MCP sign-in ask you to sign in to ContextGate the first time they connect.

   3. 3

      An app that can't sign in can use a workspace API key instead: create one under API keys and add ?api_key=<your key> to the URL.

   More on adding it to any MCP app
3. 3
   Ask your AI app to use ClickUp, then open Activity to see the call.

ClickUp's own MCP server

• ContextGate now connects to ClickUp's own MCP server by default: in Add Connection, search for ClickUp and sign in with your ClickUp account. There's nothing to copy or paste.
• ContextGate's app connector for ClickUp is still there, under Ways to connect on the same card.
• Whichever way you connect, your tool switches, policies and Activity work the same.

What you get with ClickUp and ContextGate

• Your AI apps can use ClickUpClaude, Cursor, ChatGPT and other AI apps reach ClickUp through the one ContextGate connection you add to them.
• You choose which tools they can useSwitch off any ClickUp tool you don't want used. It's hidden from your AI apps and refused if called.
• Every call is checked and recordedYour policies check each call (for example, personal data is hidden and secrets are blocked), and Activity keeps a record of it.

ContextGate sees only the tool calls that go through it, not your AI app's built-in tools or your chats.

ClickUp tools

Examples of what your AI apps can do in ClickUp. You'll see the exact list of tools after you connect it.

• get_access_tokenExchanges a clickup oauth 2.0 authorization code (obtained after user consent) for an access token.
• create_folderCreates a new clickup folder within the specified space, which must exist and be accessible.
• delete_folderPermanently and irreversibly deletes a specified folder and all its contents (lists, tasks) if the folder id exists.
• edit_guest_on_workspaceModifies the details and permissions of an existing guest user within a specific workspace.
• add_guest_to_taskAssigns a guest to a task with specified permissions; requires clickup enterprise plan, and `team id` if `custom task ids` is true.
• add_guest_to_listShares a clickup list with an existing guest user, granting them specified permissions; requires the workspace to be on the clickup enterprise plan.
• add_guest_to_folderAdds a guest to a folder with specified permissions; requires a clickup enterprise plan.
• create_task_attachmentUploads a file as an attachment to a specified clickup task, requiring `multipart/form-data` for file upload.
• create_task_commentAdds a comment to a clickup task; `team id` is required if `custom task ids` is true.
• create_chat_view_commentPosts a new comment to a specified clickup chat view; the 'view id' must correspond to an existing and accessible chat view.
• create_list_commentAdds a new comment with specific text to an existing and accessible clickup list, assigns it to a user, and sets notification preferences for all list members.
• delete_commentDeletes an existing comment from a task using its `comment id`.
• create_listCreates a new list in clickup within a specified, existing folder.
• create_taskCreates a new clickup task in a specific list, optionally as a subtask if a `parent` task id (which cannot be a subtask itself and must be in the same list) is provided.
• delete_taskPermanently deletes a task, using its standard id or a custom task id (requires `custom task ids=true` and `team id`).
• get_taskRetrieves comprehensive details for a clickup task by its id, supporting standard or custom task ids (requires `team id` for custom ids).
• update_taskUpdates attributes of an existing task; `team id` is required if `custom task ids` is true, use a single space (" ") for `description` to clear it, and provide at least one modifiable field.
• add_dependencyAdds a 'waiting on' or 'blocking' dependency to a task, requiring either `depends on` (task becomes waiting on) or `dependency of` (task becomes blocking), but not both; `team id` is required if `custom task ids` is true.
• add_tags_from_time_entriesAssociates a list of specified tags with one or more time entries within a given team (workspace).
• add_tag_to_taskAdds an existing tag to a specified task; team id is required if custom task ids is true.
• add_task_linkLinks two existing and accessible clickup tasks, identified by `task id` (source) and `links to` (target).
• add_task_to_listAdds an existing task to an additional clickup list; the "tasks in multiple lists" clickapp must be enabled in the workspace for this.
• change_tag_names_from_time_entriesUpdates the name, background color, and/or foreground color for an existing time entry tag, identified by its current `name` and `team id`.
• create_a_time_entryCreates a new time entry for a specified team.
• create_checklistCreates a new checklist with a specified name within an existing task, which can be identified by its standard id or a custom task id (if `custom task ids` is true, `team id` is also required).
• create_checklist_itemCreates a new checklist item within a specified, existing checklist, optionally setting the item's name and assigning it to a user.
• create_folderless_listCreates a new folderless list (a list not part of any folder) directly within a specified clickup space.
• create_folder_viewCreates a new, highly customizable view within a specific clickup folder using its `folder id`.
• create_goalCreates a new goal in a clickup team (workspace).
• create_key_resultCreates a new key result (target) for a specified goal in clickup to define and track measurable objectives towards achieving that goal.
• create_list_viewCreates a new, customizable view (e.g., list, board, calendar) within a specified clickup list, requiring an existing list id accessible by the user.
• create_spaceCreates a new space in a clickup team, with customizable name, privacy, color, and feature settings.
• create_space_tagCreates a new tag (name, foreground color, background color) in an existing clickup space.
• create_space_viewCreates a customizable view (e.g., list, board, gantt) within a specified clickup space, allowing configuration of grouping, sorting, filtering, and display settings.
• create_task_from_templateCreates a new task in a specified clickup list from a task template, using the provided name for the new task.
• create_teamCreates a new team (user group) with specified members in a workspace; member ids must be for existing users, and be aware that adding view-only guests as paid members may incur extra charges.
• create_webhookCreates a clickup webhook for a team (workspace) to notify a public url on specified events (at least one, or '*' for all), optionally scoped to a space, folder, list, or task; the endpoint must accept requests from dynamic ips.
• create_workspace_everything_level_viewCreates a new, customizable view (e.g., list, board) at the 'everything' level for a specified team (workspace id), encompassing all tasks within that workspace.
• delete_a_time_entryDeletes an existing time entry, specified by `timer id`, from a workspace identified by `team id`.
• delete_checklistPermanently deletes an existing checklist identified by its `checklist id`.
• delete_checklist_itemPermanently deletes an existing item, identified by `checklist item id`, from an existing checklist, identified by `checklist id`.
• delete_dependencyRemoves two dependency links for `task id`: one where `task id` is blocked by `depends on`, and another where `dependency of` is blocked by `task id`; `team id` is required if `custom task ids` is true.
• delete_goalPermanently removes an existing goal, identified by its `goal id`, from the workspace.
• delete_key_resultDeletes an existing key result, also referred to as a target within a goal, identified by its `key result id`.
• delete_listPermanently deletes an existing list and all its contents; this action is destructive and irreversible via the api.
• delete_spacePermanently deletes a specified space in clickup; this action is irreversible as the space cannot be recovered via the api.
• delete_space_tagDeletes a tag from a space, identified by `tag name` in path; precise matching of tag details in the request body (`tag name 1`, `tag tag fg`, `tag tag bg`) is generally required for successful deletion.
• delete_task_linkDeletes an existing link, effectively a dependency or relationship, between two clickup tasks; set `custom task ids=true` and provide `team id` if using custom task ids.
• delete_teamPermanently deletes an existing team (user group) from the workspace using its `group id`.
• delete_time_trackedDeletes a time-tracked interval from a task; use this legacy endpoint for older time tracking systems.
• delete_viewPermanently and irreversibly deletes an existing view in clickup, identified by its `view id`.
• delete_webhookPermanently removes an existing webhook, specified by its id, thereby ceasing all its event monitoring and notifications.
• edit_checklistUpdates an existing checklist's name or position, identified by its `checklist id`.
• edit_checklist_itemUpdates an existing checklist item, allowing modification of its name, assignee, resolution status, or parent item for nesting.
• edit_key_resultUpdates an existing key result's progress or note in clickup, where the key result measures progress towards a goal.
• edit_space_tagUpdates an existing tag's name and colors in a clickup space; requires current tag name for identification, and new values for tag name, foreground color, and background color, all of which are mandatory for the update.
• edit_time_trackedEdits a legacy time-tracked interval for a task (identified by `task id` and `interval id`) to update its start/end times and duration; `team id` is required if `custom task ids` is true.
• edit_user_on_workspaceUpdates a user's username, admin status, or custom role in a workspace; requires the workspace to be on an enterprise plan.
• get_accessible_custom_fieldsRetrieves all accessible custom field definitions for a specified clickup list using its `list id`.
• get_all_tags_from_time_entriesRetrieves all unique tags applied to time entries within a specified clickup team (workspace).
• get_authorized_teams_workspacesRetrieves a list of workspaces (teams) the authenticated user can access.
• get_authorized_userRetrieves the details of the currently authenticated clickup user.
• get_bulk_tasks_time_in_statusRetrieves the time spent in each status for multiple tasks; requires the 'total time in status' clickapp to be enabled in the workspace.
• get_chat_view_commentsRetrieves comments from a specified chat view in clickup, supporting pagination via `start` and `start id` to fetch comments older than the default 25 most recent.
• get_custom_rolesRetrieves all custom roles, which allow granular permission configurations, for a specified workspace (team).
• get_custom_task_typesRetrieves all custom task types available within a specified workspace (team id).
• get_filtered_team_tasksRetrieves a paginated list of tasks (up to 100 per page) from a specified team (workspace id in `team id`) based on various filter criteria, respecting user access permissions.
• get_folderRetrieves detailed information about a specific folder in clickup.
• get_folderless_listsRetrieves all lists within a specified space that are not located in any folder.
• get_foldersRetrieves folders within a specified clickup space, ensuring `space id` is valid, with an option to filter by archived status.
• get_folder_viewsRetrieves all configured views (like list, board, calendar) for a specified, existing folder in clickup.
• get_goalRetrieves detailed information for an existing clickup goal, specified by its unique `goal id`.
• get_goalsRetrieves goals for a specified clickup workspace (team); the `team id` must be valid and accessible.
• get_guestCall this to retrieve detailed information for a specific guest within a team (workspace), ensuring the `guest id` is valid for the given `team id`; this action requires the clickup enterprise plan.
• get_listRetrieves detailed information for an existing list in clickup, identified by its unique `list id`.
• get_list_commentsRetrieves comments for a specific clickup list, supporting pagination using `start` (timestamp) and `start id` (comment id) to fetch earlier comments; omits them for the latest 25.
• get_list_membersRetrieves all members of a specific, existing clickup list by its id.
• get_listsRetrieves all lists within a specified, existing clickup folder, optionally filtering by archived status.
• get_list_viewsRetrieves all task and page views for a specified and accessible clickup list.
• get_running_time_entryRetrieves the currently active time entry for a user in a workspace; a negative 'duration' in its data indicates it's running, and the response may be empty if no entry is active.
• get_singular_time_entryFetches a specific time entry by its id for a given team; a negative duration in the response indicates an active timer.
• get_spaceRetrieves detailed information for an existing space in a clickup workspace, identified by its unique space id.
• get_spacesRetrieves spaces for a team id; member information for private spaces is returned only if the authenticated user is a member.
• get_space_tagsRetrieves all tags for tasks within a specified clickup space, requiring a valid `space id`.
• get_space_viewsRetrieves all task and page views for a specified space id in clickup.
• get_task_commentsRetrieves up to 25 comments for a specified task, supporting pagination using `start` and `start id` to fetch older comments.
• get_task_membersRetrieves users with explicit access (directly assigned or shared) to a specific existing task, excluding users with inherited permissions.
• get_tasksRetrieves tasks from a specified clickup list; only tasks whose home is the given list id are returned.
• get_task_s_time_in_statusRetrieves the duration a task has spent in each status, provided the 'total time in status' clickapp is enabled for the workspace.
• get_task_templatesRetrieves task templates for a specified workspace (team id), supporting pagination.
• get_teamsRetrieves user groups (teams) from a clickup workspace, typically requiring `team id` (workspace id), with an option to filter by `group ids`.
• get_time_entries_within_a_date_rangeRetrieves time entries for a specified team (workspace id) within a date range (defaults to the last 30 days for the authenticated user if dates are omitted); active timers are indicated by negative durations in the response.
• get_time_entry_historyRetrieves the modification history for an existing time entry within a specific clickup team (workspace).
• get_tracked_timeRetrieves tracked time for a task using a legacy endpoint; prefer newer time tracking api endpoints for managing time entries.
• get_userRetrieves detailed information for a specific user within a clickup workspace (team), available only for workspaces on the clickup enterprise plan.
• get_viewFetches details for a specific clickup view, identified by its `view id`, which must exist.
• get_view_tasksRetrieves all tasks visible in a specified clickup view, respecting its applied filters, sorting, and grouping.
• get_webhooksFetches webhooks for a team (workspace), returning only those created by the authenticated user via api, for a `team id` they can access.
• get_workspace_everything_level_viewsRetrieves all task and page views at the 'everything level' (a comprehensive overview of all tasks across all spaces) for a specified clickup workspace.
• get_workspace_planRetrieves the details of the current subscription plan for a specified clickup workspace.