Skip to main content
Back to the ClickUp MCP server

MCP Gateway · Cursor

ClickUp icon

Connect ClickUp to Cursor

Cursor users can keep ClickUp tasks and docs in step with the code they're writing. With ClickUp behind the Speakeasy MCP Gateway, Cursor finds the task for a feature, attaches files to it and writes technical docs into the right space. Cursor hooks check each prompt and tool call with Speakeasy and fail closed.

Category
Project management
Tools
51
Authentication
OAuth
Cursor
Editor and terminal

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 Cursor 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 Cursor

    Add the gateway to Cursor in one click from the Organization Gateway page.

    On the Organization Gateway page in Speakeasy, choose Cursor under Install.

    Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.

  4. 04

    Sign in and use ClickUp from Cursor

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

For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.

Use cases

What Cursor users do with ClickUp

Read the task behind a feature

Search ClickUp for the task behind the feature you're editing and have Cursor read its description and subtasks, so the implementation matches what was asked for.

clickup_searchclickup_get_task

Write the technical doc beside the code

Once a design settles, Cursor creates a ClickUp doc in the project's space and adds pages for the API and the data model.

clickup_create_documentclickup_create_document_page

Attach evidence to a bug task

When you reproduce a bug, Cursor attaches the log file or a screenshot URL to the ClickUp task so QA works from the same evidence.

clickup_attach_task_file

Tools

51 tools

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

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

Prompt and tool-call blocking

Cursor

Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.

User attribution

Cursor

Every Cursor hook event carries the user's email.

Budgets

Cursor

Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.

Device agent and MDM

Cursor

The device agent installs the marketplace and plugins and reapplies them every minute.

  • Cursor Cloud agents need a checked-in .cursor/hooks.json. Session and MCP-specific hooks don't run there.
  • After a plugin update, members run Developer: Reload Window.

Questions

Frequently asked questions

Do Cursor Cloud agents get the same ClickUp controls?
Not all of them. Cursor Cloud agents need a checked-in .cursor/hooks.json, and session and MCP-specific hooks don't run there.
Can Cursor overwrite a ClickUp doc page?
clickup_update_document_page replaces a page's full content when content is provided. If that's a concern, deny it for a role at the MCP Gateway and keep clickup_create_document_page allowed.
How do Cursor users get ClickUp?
An admin adds ClickUp from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway to Cursor in one click from the Organization Gateway page. Each person then sees only the ClickUp tools their access allows.
Are ClickUp calls from Cursor 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.