ClickUp MCP server for Claude, ChatGPT and other clients: what it does, access, how to connect

What can an agent do with ClickUp through MCP?

It can search a Workspace, read and change tasks, log time, edit Docs and post Chat messages through 48 tools, per ClickUp.

What access does it get?

The same access as the ClickUp user who signs in, limited to the Workspaces they select; ClickUp publishes no OAuth scope names.

How do I connect it?

Add https://mcp.clickup.com/mcp in your client, sign in to ClickUp and pick your Workspaces; test with a read-only prompt first.

{
  "mcpServers": {
    "clickup": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.clickup.com/mcp"]
    }
  }
}

What should a finance team watch for?

Low daily call caps on smaller plans, writes that take effect at once, and free text in tasks and comments that the agent reads.

• Without the Everything AI add-on, calls are capped per Workspace and per client over a rolling 24 hours, per ClickUp: 100 on Free Forever, 300 on Core/Unlimited, 1,000 on Business, 2,500 on Business Plus, 5,000 on Enterprise and 25,000 on Enterprise Plus. The window starts with your first request, each tool call counts, and caps cannot be reset.
• A blocked call returns RATE_LIMIT_EXCEEDED. At 100 calls a day, one close-status review that walks many tasks could use up the Free Forever cap.
• With the add-on, MCP shares the public API's per-minute limits (100 to 10,000 requests per minute per token by plan). ClickUp says limits may change and a fair use policy applies.
• Creates, updates, bulk edits, file attachments, removals, Chat messages and Delete task act immediately. Keep your client's per-call approval on.
• ClickUp's overview says there are no deletion tools, but its tool reference lists Delete task; assume deletion is possible.
• IT can't gate MCP inside ClickUp: ClickUp says no Workspace admin approval is needed and documents no Workspace-level off switch. Control it in your AI client's admin settings instead.
• Task descriptions, comments, Docs and Chat are untrusted input: an injected instruction could push the agent to edit, delete or message. Don't approve calls you didn't ask for.
• Least privilege: connect only the Workspaces you need, and give each staff member their own ClickUp sign-in so changes carry their own permissions. ClickUp documents no way to switch off write tools.
• The Claude Free bridge runs npx -y mcp-remote, which fetches a third-party npm package at launch without a pinned version. mcp-remote's README says it stores credentials in ~/.mcp-auth on that machine. Don't share or commit the config, and pin a version if your policy requires it. ClickUp's setup for other clients uses the same command.
• ClickUp's MCP docs don't describe data handling. ClickUp's AI terms cover ClickUp AI features. Data an agent reads over MCP goes to your AI client, so check Anthropic's or OpenAI's terms as well.

How could finance teams and accounting firms use it?

Reads suit status questions and time reporting across close and client work; writes suit task and Doc drafting that a person checks before it goes out.

Keep a person approving anything that changes ClickUp or another system of record. Treat AI summaries of time and status as drafts until someone checks them.

Change log

FAQ

Sources

• ClickUp developer docs: ClickUp's MCP Server
• ClickUp developer docs: connect an AI assistant
• ClickUp developer docs: MCP tools
• ClickUp developer docs: API rate limits
• ClickUp blog: how to use the ClickUp MCP server
• Claude connector directory: ClickUp
• mcp-remote README (credential storage)
• ClickUp AI terms

Verified by theFinanceStack, 21 Oct 2026. Vendor list on the CFO Software Market Map courtesy of Jason Staats; AI connectivity data by theFinanceStack. Not tax, compliance or financial advice.