Skip to main content
Back to the ClickUp MCP server

MCP Gateway · Claude Cowork

ClickUp icon

Connect ClickUp to Claude Cowork

Cowork can carry out ClickUp work that takes many steps, such as setting up a project from a brief or writing a weekly status report from several lists. Members receive the ClickUp plugin from the organization's synced marketplace without a GitHub invitation. Agent hooks send each prompt to Speakeasy before the step runs, and Cowork's OTLP export ties sessions to people.

Category
Project management
Tools
51
Authentication
OAuth
Claude Cowork
Cowork tab in Claude Desktop

Behind the MCP Gateway

Run ClickUp MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every ClickUp call inspected and logged.

Deploy on MCP Gateway

Set up

Add ClickUp to Claude Cowork in 4 steps

  1. 01

    Add ClickUp from the catalog

    An admin finds ClickUp in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    ClickUp uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use ClickUp

    Give teams the mcp:connect scope on the ClickUp server through team access or a role. Claude Cowork connects to the ClickUp server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use ClickUp from Claude Cowork

    The first time Claude Cowork connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    ClickUp needs its own OAuth grant, so each person connects it once. Until they do, ClickUp calls fail while the rest of the gateway keeps working.

    From then on, ClickUp's tools appear in Claude Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with ClickUp

Set up a project from a brief

Give Cowork a project brief and it creates a ClickUp folder with a list for each phase, then fills the lists with tasks taken from the brief.

clickup_create_folderclickup_create_list_in_folderclickup_create_task

Write the weekly status report

Each week Cowork filters completed and overdue tasks, checks where work sat longest, and writes the summary into a ClickUp doc for the team.

clickup_filter_tasksclickup_get_bulk_tasks_time_in_statusclickup_create_document

Clear out finished and overdue work

Cowork goes through a list's overdue tasks, moves the finished ones to an archive list and updates the status or due date on the rest.

clickup_filter_tasksclickup_move_taskclickup_update_task

Tools

51 tools

Each ClickUp tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork sees it.

clickup_get_workspace_hierarchy

Get workspace hierarchy (spaces, folders, lists) from your authenticated workspace with pagination support. Workspace ID is automatically detected from your session. Returns tree structure with names and IDs for navigation.

clickup_create_task

Create task in a ClickUp list. Requires task name and list_id. ALWAYS ask user which list to use - never guess. Use clickup_get_list to resolve list names to IDs. Supports assignees as array of user IDs, emails, usernames, or "me". , 'Bug', 'Feature').

clickup_get_task

Get task details by task_id (works with regular/custom IDs). Set subtasks=true to include all subtask details.

clickup_filter_tasks

Retrieve tasks with combined filters. Supports filtering by tags, lists, folders, spaces, statuses, assignees, due date range, and completion date range. , tags: ["bug", "feature"] returns tasks with either tag).

clickup_update_task

Update task properties. Requires task_id and at least one update field. Custom fields supported as array of {id, value}. Supports assignees as array of user IDs, emails, usernames, or "me". , 'Bug', 'Feature'), or null to reset to default.

See all 51 tools

Control

What Speakeasy can see and stop in Claude Cowork

The gateway covers every client the same way. The rest depends on what Claude Cowork exposes to Speakeasy.

Tool logs

Gateway

Every ClickUp call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the ClickUp tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to ClickUp can reject a tool request before it reaches the server, or withhold a result from Claude Cowork. MCP-scoped policies are enabled per organization.

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

Does the device agent manage ClickUp in Cowork?
No. Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies. Cowork reads the synced repository, and a new session picks up plugin changes.
Can a Cowork task create folders and lists in ClickUp?
Only if the person's role allows it. Folder, list and task tools are each allowed or denied per team and role at the MCP Gateway, so a reporting role can read tasks without creating structure.
How do Claude Cowork users get ClickUp?
An admin adds ClickUp from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the ClickUp tools their access allows.
Are ClickUp calls from Claude Cowork logged?
Yes. ClickUp calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

ClickUp in other clients

AI everywhere.

Control here.