Skip to main content
Back to the ClickUp MCP server

MCP Gateway · Claude

ClickUp icon

Connect ClickUp to Claude

Project managers, marketers and operations staff can ask Claude about ClickUp work in plain language. Added as a custom connector through the Speakeasy MCP Gateway, ClickUp becomes something people search and update from chat, and each person sees only the servers their role can reach. No client ID or secret is needed, because the gateway's sign-in handles client registration.

Category
Project management
Tools
51
Authentication
OAuth
Claude
Web, desktop and mobile

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 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. The organization gateway works out each person's servers from their live access, so granting access adds ClickUp to their gateway on the next call, and removing it takes it away.

  3. 03

    Connect Claude

    Add the gateway URL as a custom connector, then connect it from Customize > Connectors.

    On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.

    Each person opens Customize > Connectors and clicks Connect to sign in.

    On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.

  4. 04

    Sign in and use ClickUp from Claude

    The first time Claude 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, limited to what the person's access allows, and every call lands in the gateway's tool logs.

No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.

Use cases

What Claude users do with ClickUp

Find anything in the workspace

Ask Claude where the onboarding checklist or last quarter's launch doc lives, and it searches tasks, docs and attachments across ClickUp at once.

clickup_search

Set reminders from a conversation

After talking through a plan with Claude, have it create ClickUp reminders with due dates for each follow-up, then list them later to see what's still open.

clickup_create_reminderclickup_search_reminders

Check on a client project

Ask how a client project is going. Claude finds its folder and lists in the workspace, then filters tasks by status and due date to show what's late.

clickup_get_workspace_hierarchyclickup_filter_tasks

Tools

51 tools

Each ClickUp tool can be allowed or denied per team and role at the MCP Gateway before Claude 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

The gateway covers every client the same way. The rest depends on what Claude 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. MCP-scoped policies are enabled per organization.

Anthropic inference hooks

Claude

On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.

Conversation import

Claude

Claude conversations can be imported through Anthropic's Compliance API for review after the fact.

  • Custom connectors need a Claude plan that supports them.
  • Budgets don't cover Claude web and desktop usage.

Questions

Frequently asked questions

Do Speakeasy budgets cover ClickUp use in Claude?
No. Budgets don't cover Claude web and desktop usage. Access is still controlled at the MCP Gateway, where each ClickUp tool is allowed or denied per team and role.
Can a prompt be blocked before Claude acts on it?
On Claude Enterprise, each prompt goes to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
How do Claude users get ClickUp?
An admin adds ClickUp from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway URL as a custom connector, then connect it from Customize > Connectors. Each person then sees only the ClickUp tools their access allows.
Are ClickUp calls from Claude 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.