By Ira Bodnar, Ryze AI · Updated · Connector tested the same day
Quick answer
The main way to connect Cursor to ClickUp is the Ryze AI connector. Save a ClickUp personal API token on the ClickUp card in Ryze AI, choose one ClickUp Workspace, then install https://connector.get-ryze.ai/mcp in Cursor through the Add to Cursor link or an mcp.json entry and finish the browser sign-in.
- Create a pk_ token in ClickUp under Settings > Apps > API Token
- Save the token on the ClickUp card in Ryze AI Integrations and pick the Workspace
- In Cursor add the Ryze AI server (Add to Cursor link or mcp.json) and finish the sign-in
- Start a new Cursor chat and ask about your tasks, lists or comments
Cursor to ClickUp at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, added to Cursor with the Add to Cursor link or a url entry in mcp.json |
| Server address | https://connector.get-ryze.ai/mcp, one URL for all users |
| ClickUp sign-in | A personal API token beginning pk_, saved on the ClickUp card in Ryze AI. Requests run as the person who made it |
| Cursor sign-in | The Ryze AI page Cursor opens in the browser, with OAuth and dynamic client registration. A Ryze AI API key in a header also works |
| ClickUp tools | Three tools: clickup__read, clickup__write, clickup__delete |
| Can Cursor change ClickUp | Yes: clickup__write makes and edits tasks and posts comments, clickup__delete removes a task or comment. Cursor prompts before MCP tool calls unless you allowlist them |
| Other data in the same chat | Not covered here. This guide states only the ClickUp tools, because Ryze AI's notes for ClickUp list no other data |
| Cursor plan needed | Cursor's MCP documentation names none |
| Ryze AI price | From $89 per month on Paid Ads, with a 7-day free trial. Connecting costs nothing |
| ClickUp's own option for Cursor | ClickUp's MCP server at https://mcp.clickup.com/mcp with OAuth only, plus a ClickUp entry in the Cursor Marketplace |
| Last tested | November 17, 2026: only the connector's sign-in challenge and discovery file. No ClickUp call, and nothing inside Cursor |
Before you start
- A Cursor install. Cursor's MCP documentation names no plan for using MCP servers. On Enterprise, admins can control which MCP servers users may run in Team Settings > MCP Configuration, so a blocked server needs an admin to allow it.
- A ClickUp personal API token. ClickUp's docs have you click your avatar, choose Settings, open Apps and press Generate under API Token. Tokens begin with pk_ and, per ClickUp, do not expire. Everything Cursor does in ClickUp runs with that user's rights, so generate it from the account whose access you want to hand over.
- A Ryze AI plan or trial. The cheapest start is Paid Ads at $89 per month with a 7-day free trial (SEO Starter is $129 with 3 days free, Agency is $279). The connector itself is free to add, yet the ClickUp tools answer only while a plan or trial is active.
How to connect Cursor to ClickUp
Two steps happen in ClickUp and Ryze AI, two in Cursor, and the last is your first prompt. The connector URL is the same for every user.
Create a ClickUp personal API token
In ClickUp click your avatar, choose Settings, then Apps, and press Generate under API Token. Copy the value that begins with pk_.
Connect ClickUp in Ryze AI
Sign in to Ryze AI (or create an account), open Integrations and click Connect on the ClickUp card. Paste the token into the Personal API token field, click Continue, then choose which Workspace the agent may use and click Save. A single-Workspace login skips the choice.
Add the Ryze AI server to Cursor
Either use the Add to Cursor link on the Ryze AI developers page, which opens a cursor:// install link for a server named ryze at https://connector.get-ryze.ai/mcp, or create ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project) with the url entry shown below.
{ "mcpServers": { "ryze": { "url": "https://connector.get-ryze.ai/mcp" } } }Sign in from Cursor
Confirm the install in Cursor. Cursor runs OAuth with PKCE and dynamic client registration, so there is no client ID or secret to enter. Sign in on the Ryze AI page and click Allow connection. You can manage or toggle the server from the Customize page in the sidebar.
Ask your first question in Cursor
Open a new chat in Cursor, accept the tool prompt, and send: Which ClickUp tasks assigned to me are overdue?
The Ryze AI help center page for ClickUp covers the ClickUp side of the connection. Cursor does not have its own Ryze AI help page; the Ryze AI developers page has the Add to Cursor link and the matching config.
Sources: Cursor MCP documentation, ClickUp authentication, Ryze AI ClickUp guide. Checked November 17, 2026.
mcp.json, API key and Cloud Agents
mcp.json
Save this as ~/.cursor/mcp.json for every project or .cursor/mcp.json for one project. Cursor accepts remote servers through the url field and handles the OAuth sign-in itself.
{
"mcpServers": {
"ryze": {
"url": "https://connector.get-ryze.ai/mcp"
}
}
}Cursor supports stdio, SSE and Streamable HTTP transports. For OAuth it reads the server's protected resource metadata (RFC 9728) and registers as a public client through dynamic client registration. After sign-in, manage or toggle the server from the Customize page in the sidebar.
mcp.json with a Ryze AI API key
If you prefer a key to the browser sign-in, add a headers entry and set RYZE_API_KEY in your environment to the rk_live_ key from Ryze AI under Workspace Settings > Profile > API keys. Keep the key out of files you commit.
{
"mcpServers": {
"ryze": {
"url": "https://connector.get-ryze.ai/mcp",
"headers": {
"Authorization": "Bearer ${env:RYZE_API_KEY}"
}
}
}
}Cloud Agents
Cursor Cloud Agents keep their own MCP sign-ins on Cursor's servers, separate from the sign-in on your desktop. If a Cloud Agent needs your ClickUp tasks, connect the Ryze AI server for it as well.
Cursor and MCP: the facts in one table
| Topic | What Cursor's documentation says |
|---|---|
| Config files | .cursor/mcp.json inside a project, or ~/.cursor/mcp.json for every project |
| Transports | stdio, SSE and Streamable HTTP |
| Sign-in | OAuth. Cursor registers as a public client with no client secret. Static OAuth client credentials in mcp.json are the alternative |
| Variables in mcp.json | ${env:NAME}, ${userHome}, ${workspaceFolder}, ${workspaceFolderBasename} and ${pathSeparator} |
| Tool approval | Cursor asks before it uses an MCP tool by default. In Auto-review mode, allowlisted MCP tools run at once and every other call goes through Cursor's review step |
| MCP features | Tools, resources, prompts and elicitation |
| Where servers are managed | Customize in the sidebar. Team admins use Dashboard > Plugins & MCPs and Team Settings > MCP Configuration |
| Install link | cursor://anysphere.cursor-deeplink/mcp/install, with the server name and a base64 copy of the config |
Sources: Cursor MCP documentation, Cursor MCP install links. Checked November 17, 2026.
Claude and ChatGPT
The same URL works in other MCP clients. ClickUp is connected once in Ryze AI, so nothing changes on the ClickUp side.
Claude
Add https://connector.get-ryze.ai/mcp as a custom connector under Customize > Connectors, pick the workspaces and start a new chat. Claude Code has its own command: claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp. The Claude guide for ClickUp is linked below.
ChatGPT
OpenAI offers custom MCP servers with full support on ChatGPT Business and Enterprise/Edu (web) and read and fetch only on Pro. Add the same URL as an app in Settings > Apps. When ClickUp was linked in Ryze AI after the app was created, delete the app and add it again to refresh its tools.
ClickUp access and scope
A personal token carries no scope list, so the reach of Cursor in ClickUp comes from three settings.
- Whose rights
- Those of the ClickUp user behind the token. Ryze AI states the agent acts as the token owner and can see and edit only what that person can.
- Which Workspace
- The single Workspace chosen on the ClickUp card. Ryze AI ties one connection to one ClickUp Workspace and does not list ClickUp among platforms that take several accounts.
- What Cursor asks first
- Cursor asks for approval before using MCP tools by default and follows the same Run Modes as terminal commands, so a task update waits for your click unless you allowlist the tool.
The access the connection has
ClickUp's authentication page names no scopes for a personal token and says only that users reach what ClickUp permits them. The table shows what Ryze AI documents for this connection.
| Kind of access | Objects | Tool |
|---|---|---|
| Read | Workspaces, Spaces, Folders, Lists, tasks, comments, members, custom fields, Docs | clickup__read |
| Create and update | New tasks, task edits, new comments | clickup__write |
| Delete | A task or a comment, addressed by path | clickup__delete |
Left out: Docs edits and a second Workspace on the same connection. Ryze AI's ClickUp page lists writes for tasks and comments only, although its opening line mentions lists, spaces and docs, so this guide limits write claims to tasks and comments. Private Lists that the token owner cannot open stay invisible to Cursor too.
Source: ClickUp authentication, Ryze AI ClickUp guide. Checked November 17, 2026.
Removing access
To stop Cursor, switch the ryze server off under Customize or delete its entry in mcp.json. To retire the token, press Regenerate under Settings > Apps > API Token in ClickUp, then paste the new value on the ClickUp card in Ryze AI. Ryze AI's notes describe no disconnect step for that card, so none is given here.
What Cursor can do in ClickUp
ClickUp gets one tool per access level in the Ryze AI connector. The names come from the Ryze AI integration manifest; they were not listed from a live connected workspace. Each call carries a ClickUp API path, with GET for reads, POST or PUT for writes and a delete by path.
| Tool | Type | What it does |
|---|---|---|
| clickup__read | Read | GET requests against ClickUp: Workspaces, Spaces, Folders, Lists, tasks, comments, members, custom fields and Docs. |
| clickup__write | Write | POST or PUT requests, for example making a task, adding a comment or editing a task. |
| clickup__delete | Delete | Removes one ClickUp object by its path, such as a task or a comment. |
Some limits apply to every client, Cursor included. One ClickUp Workspace is covered per connection, Docs are read only, and the agent has the token owner's permissions only.
Cursor asks before it runs an MCP tool by default. Keep that default if you want to review each task update, or leave clickup__delete off your allowlist. Separately, the Ryze AI chat has its own Tool approvals setting that starts on Skip all approvals; you can choose Approve write & delete or Manual approve there, and scheduled tasks run without an approval step.
Limits in numbers
| Limit | Figure from ClickUp | Source page |
|---|---|---|
| REST requests per minute on Free Forever, Unlimited and Business plans | 100 for each token | Rate limits |
| REST requests per minute on Business Plus | 1,000 for each token | Rate limits |
| REST requests per minute on Enterprise and Enterprise Plus | 10,000 for each token | Rate limits |
| Over the limit | ClickUp replies HTTP 429 and adds X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset (Unix time) | Rate limits |
| Token lifetime | A personal token has no expiry date | Authentication |
| Ryze AI side | One ClickUp Workspace per connection; the Ryze AI notes repeat the 100 per minute per token figure | Ryze AI help center |
| ClickUp's MCP server, per connection | 1,000 requests per minute, and 20 file uploads per 15 minutes per user, up to 1 GB per file | Supported tools |
| ClickUp's MCP server, per day | Without the Everything AI add-on, per Workspace and per client in a rolling 24 hours: 100 calls on Free Forever, 300 on Core/Unlimited, 1,000 on Business, 2,500 on Business Plus, 5,000 on Enterprise, 25,000 on Enterprise Plus | ClickUp's MCP Server |
ClickUp calls the plan Unlimited on its rate limit page and Core/Unlimited on its MCP page, so each row copies the wording of its own page. The MCP page counts daily calls for each client separately, which means Cursor and Claude each get a count of their own on ClickUp's server. Whether calls through the Ryze AI connector count against those MCP figures is not stated by either vendor; since the connector uses the REST API with your token, they probably do not, but that is an inference.
Sources: ClickUp rate limits, ClickUp's MCP Server, ClickUp supported tools. Checked November 17, 2026.
First 3 prompts to run
1. Find overdue tasks
Look through my ClickUp Workspace for tasks assigned to me with a due date in the past. Give the task name, List and due date for each.
Tools used: clickup__read
What comes back: Task names with their Lists and due dates, read only.
2. Condense a comment thread
Pull the comments from the task I name next and condense them into who requested what, oldest first.
Tools used: clickup__read
What comes back: A short written digest of that task's comments, based on what the read tool returns.
3. Open a task with a comment
In the List called Reporting, open a task named Draft Q1 report and comment on it that the outline is due Friday.
Tools used: clickup__read, clickup__write
What comes back: A task in that List plus a comment, created after you accept the write prompt in Cursor.
Results come from your own Workspace, so no sample task data is printed here. Swap in your own names. Naming a Space, Folder or List narrows the request that the read tool sends to ClickUp.
10 jobs to hand to Cursor
Ten requests for Cursor, each with the tool behind it. None was run for this guide because no ClickUp Workspace was connected. Yes means Ryze AI's notes list a tool for the job; the final row is a job no listed tool covers.
| Job | Ask Cursor | Tool | Works on the default connection |
|---|---|---|---|
| Workspace map | Show the Spaces, Folders and Lists in the Workspace. | clickup__read | Yes |
| Overdue work | Which of my tasks have passed their due date? | clickup__read | Yes |
| Task detail | Give me the description, assignees and custom fields for one task. | clickup__read | Yes |
| Thread digest | Condense the comments on this task. | clickup__read | Yes |
| Member list | Who are the members of this Workspace? | clickup__read | Yes |
| Doc lookup | Find the Doc called this and give me the gist. | clickup__read | Yes |
| New task | Add a task with this title to this List. | clickup__write | Yes, once you accept the prompt in Cursor |
| Task edit | Apply this change to the task I name. | clickup__write | Yes, once you accept the prompt in Cursor |
| Task removal | Remove the task I name. | clickup__delete | Yes, on request; Cursor prompts first unless allowlisted |
| Doc rewrite | Rewrite this Doc for me. | none | No. Docs are read only in Ryze AI |
4 ways to connect Cursor to ClickUp
Four routes put a ClickUp Workspace in front of Cursor. The Ryze AI connector in the first row is the main way here: one saved token, one URL, and separate read, write and delete tools. The other rows come from ClickUp's and GitHub's pages read on November 17, 2026; none was installed for this guide.
| Way | Runs where | Setup in Cursor | What it reaches in ClickUp | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted, one URL for everyone | Add to Cursor link or an mcp.json url entry, then browser sign-in. ClickUp access comes from a pk_ token saved in Ryze AI | Three tools: read Workspaces, Spaces, Folders, Lists, tasks, comments, members, custom fields and Docs; make and edit tasks and comments; remove a task or comment | Paid Ads from $89 per month, 7-day free trial |
| ClickUp's MCP server, added by url | Hosted by ClickUp | ClickUp's setup page gives a url entry for https://mcp.clickup.com/mcp in mcp.json. ClickUp says it supports OAuth only, so a personal API token cannot be used | ClickUp's tools page lists more than 60 tools, including time tracking, chat, reminders, attachments and Docs. Calls run with the signed-in user's permissions | ClickUp says the MCP server is available on all plans, with daily call limits that depend on the plan |
| ClickUp entry in the Cursor Marketplace | Hosted by ClickUp | ClickUp's setup page links cursor.com/marketplace/clickup and Cursor's MCP directory page for an install from Cursor | ClickUp's own server, so the same tools as the row above | Same as above |
| taazkareem/clickup-mcp-server, community | Self-hosted or run with npx | Run it with a ClickUp API key and your own configuration. See its README for the Cursor steps | Its README describes tasks, checklists, sprints, comments, tags, spaces, lists, folders, files, docs, chat and time tracking | The README license badge reads Proprietary and the GitHub license field is not set, so read its terms first |
Two limits of the main way
- A personal token on ClickUp's server. ClickUp's MCP page says its server takes OAuth only, with no personal keys or access tokens. Ryze AI is the route that works from a personal token, since Ryze AI stores it and Cursor only signs in to Ryze AI.
- Bulk and Docs writes through the Ryze AI connector. ClickUp's tools page lists bulk task changes and Doc page edits. Ryze AI documents writes for tasks and comments only, so those jobs need ClickUp's own server.
Which one to pick
Ryze AI is the best way to connect Cursor to ClickUp for task reads and simple task or comment edits behind one shared URL, with one caveat: three tools, one Workspace per connection and read-only Docs. Choose ClickUp's own server when you need time tracking, chat, reminders, bulk edits or Doc writes, and accept its OAuth sign-in. Because the two use different server names, mcp.json can hold both. The community server fits people who want to run code themselves and are fine with its license.
Sources: ClickUp's MCP Server, ClickUp MCP setup instructions, ClickUp supported tools, taazkareem/clickup-mcp-server, Cursor MCP documentation, Ryze AI ClickUp guide. Checked November 17, 2026.
ClickUp and MCP: dates that matter
| Date | What happened |
|---|---|
| March 13, 2026 | ClickUp's authentication page was last updated. It says personal tokens begin with pk_ and never expire. |
| August 14, 2026 | ClickUp's MCP setup page was last updated. It lists a manual mcp.json entry for Cursor and a Cursor Marketplace link. |
| October 7, 2026 | ClickUp's MCP overview page was last updated. It says the MCP server is on all plans, accepts OAuth only, and gives daily call limits per Workspace and per client. |
| October 27, 2026 | ClickUp's supported tools page was last updated. It lists 1,000 requests per minute per connection for ClickUp's MCP server. |
| November 17, 2026 | ClickUp's MCP overview says deletion tools were held back as a safety step, yet its tools page lists Delete task and Delete Comment. Check what your connection shows. Its rate limit page gives 100, 1,000 and 10,000 requests per minute by plan. |
Sources: ClickUp authentication, ClickUp MCP setup instructions, ClickUp's MCP Server, ClickUp supported tools. Checked November 17, 2026.
How this guide was tested
Only the outside of the Ryze AI connector was checked, on November 17, 2026. No ClickUp Workspace is connected in the test workspaces, so the record is brief.
| What was run | What came back |
|---|---|
| POST to the connector address with no token (November 17) | https://connector.get-ryze.ai/mcp returned HTTP 401 and a WWW-Authenticate header naming its protected resource metadata. MCP clients use that reply to start the browser sign-in. |
| Discovery file on the connector host (November 17) | Loaded. It lists authorize, token and register endpoints, the authorization code and refresh token grants, S256 and plain PKCE, and the scopes mcp:read and mcp:write. |
| POST to ClickUp's MCP address with no token (November 17) | https://mcp.clickup.com/mcp returned HTTP 401. |
| Live ClickUp tool list | Not seen. The three names come from the Ryze AI integration manifest because no workspace had ClickUp connected. |
| ClickUp calls | None were made, so this page quotes no ClickUp response. |
Also not run: anything inside Cursor. Cursor was not installed on the test machine, so no server was added, no Ryze AI sign-in was completed from Cursor, and Cursor never called a ClickUp tool. The Cursor steps follow Cursor's MCP documentation as it read on November 17, 2026, and the ClickUp limits follow ClickUp's documentation from the same day.
Cursor and ClickUp errors and fixes
No call to ClickUp was run for this guide, so there are no error messages from a test to quote. The fixes below come from the Ryze AI and ClickUp pages named on this page.
Problems and fixes
- The ClickUp tools do not appear in Cursor
- If ClickUp was connected in Ryze AI after the server was added, remove the ryze entry and add it again, then start a new chat so the tool list refreshes.
- Cursor never asks me to sign in
- Open Customize in the sidebar, find the ryze server and reconnect it. Cursor reads the connector's protected resource metadata and registers itself, so no client ID is needed.
- Ryze AI refuses the token
- Copy the whole pk_ value again from Settings > Apps > API Token. A regenerated token invalidates the earlier one.
- Cursor works in the wrong Workspace
- A connection covers one Workspace. Reconnect the ClickUp card and select the right one.
- A task or List does not show
- The token owner's rights apply. Anything that person cannot open in ClickUp is hidden from Cursor as well.
- Cursor will not edit a Doc
- Ryze AI treats Docs as read only. Have Cursor write the text and paste it into ClickUp by hand.
- Requests start failing
- ClickUp sends HTTP 429 once a token passes its per-minute allowance and puts the reset time in X-RateLimit-Reset. Wait, or ask for fewer and smaller requests.
- A Cloud Agent cannot reach ClickUp
- Cloud Agents keep their own MCP sign-ins on Cursor's servers. Connect the Ryze AI server for the agent separately from your desktop.
- The server is blocked on a team account
- Enterprise admins can allowlist which servers and tools the team may run. Ask an admin to allow the Ryze AI server in Team Settings > MCP Configuration.
- Tools report a missing subscription
- The ClickUp tools need a live Ryze AI plan or trial. Start the trial and try again.
Terms on this page
- MCP
- The Model Context Protocol, an open standard for connecting AI applications to outside systems. Cursor, Claude and ChatGPT support it.
- MCP server
- A program that offers tools over MCP. The Ryze AI connector is an MCP server that runs on Ryze AI's side, so there is nothing to install.
- mcp.json
- The file where Cursor keeps its list of MCP servers.
- Personal API token
- A pk_ credential from ClickUp that acts as its owner and, per ClickUp, never expires.
- Workspace
- The top level of ClickUp, holding Spaces, Folders, Lists and tasks. Not the same as a Ryze AI workspace, which is the Ryze AI account area Cursor may enter.
- List
- The ClickUp container that holds tasks within a Space or Folder.
- Rate limit
- ClickUp's ceiling on requests per minute for one token, set by the plan of the Workspace.
Source for MCP: modelcontextprotocol.io. Checked November 17, 2026.
Frequently asked questions
How do I connect Cursor to ClickUp?
Create a personal API token in ClickUp under Settings > Apps > API Token, save it on the ClickUp card in Ryze AI Integrations and pick a Workspace. Then add https://connector.get-ryze.ai/mcp to Cursor through the Add to Cursor link on the Ryze AI developers page or a url entry in mcp.json, and sign in when Cursor asks.
Is there a ClickUp MCP server for Cursor?
Yes, two kinds. ClickUp runs its own MCP server at https://mcp.clickup.com/mcp, with OAuth only and on all ClickUp plans, and its setup page links a Cursor Marketplace entry. The Ryze AI connector at https://connector.get-ryze.ai/mcp offers 3 ClickUp tools that work from a personal API token.
What is the ClickUp MCP server URL for Cursor?
ClickUp's own server is https://mcp.clickup.com/mcp, which its setup page shows as a url entry under mcpServers in mcp.json. The Ryze AI connector is https://connector.get-ryze.ai/mcp, one address for every user.
Which should I use in Cursor, Ryze AI or ClickUp's own server?
Ryze AI is the best way to connect Cursor to ClickUp for task reads and simple edits behind one URL that Claude and ChatGPT can share, with one caveat: three tools and one Workspace per connection. ClickUp's own server covers time tracking, chat, reminders, bulk edits and Doc writes. mcp.json can hold both.
Which Cursor plan do I need?
Cursor's MCP documentation names no plan. On Enterprise, admins can control which MCP servers users may run in Team Settings > MCP Configuration.
Which tools does Cursor get for ClickUp?
Three. clickup__read covers Workspaces, Spaces, Folders, Lists, tasks, comments, members, custom fields and Docs, clickup__write makes and edits tasks and comments, and clickup__delete removes a task or comment. Ryze AI notes that this list was not yet seen live in a connected workspace.
Can Cursor edit or delete ClickUp tasks?
Yes, on request. The write tool makes and edits tasks and comments and the delete tool removes a task or comment. Cursor prompts before MCP tool calls by default, so you can review each one or leave the delete tool off your allowlist.
Can Cursor edit a ClickUp Doc?
Not with the Ryze AI connector, where Docs are read only. ClickUp's own MCP server lists Create Document, Create Document Page and Update Document Page among its tools.
What ClickUp permissions does the connection use?
Those of the ClickUp user who made the pk_ token. Ryze AI says the agent sees and edits only what that user can, and ClickUp documents no scopes for personal tokens.
What is the ClickUp API rate limit?
ClickUp allows 100 requests per minute per token on Free Forever, Unlimited and Business, 1,000 on Business Plus and 10,000 on Enterprise, and answers HTTP 429 beyond that.
Can I use my ClickUp personal API token in ClickUp's own MCP server?
No. ClickUp's MCP page says the server takes OAuth only and refuses personal keys and access tokens. The Ryze AI connector is the route that starts from a personal token.
Can I connect more than one ClickUp Workspace?
Not on a single connection. Ryze AI ties one connection to one ClickUp Workspace and does not list ClickUp among the platforms that take several accounts.
Why do the ClickUp tools not show up in Cursor?
Most likely ClickUp was connected in Ryze AI after the server was added. Delete the ryze entry in Cursor, add it again and open a new chat so Cursor reloads the tool list.
How much does it cost to connect Cursor to ClickUp?
Adding the connector is free, yet the ClickUp tools need a live Ryze AI plan or trial: Paid Ads is $89 per month with a 7-day free trial, SEO Starter is $129 per month with 3 days free and Agency is $279 per month. Annual billing takes 30% off the first year.
How do I disconnect ClickUp from Cursor?
Switch the ryze server off in Cursor's Customize page or remove its mcp.json entry. To cut off the token itself, regenerate it in ClickUp under Settings > Apps > API Token.