← Explore all mcp servers

WORK MANAGEMENT / ClickUp

ClickUp MCP

Search workspace context and perform task, document and collaboration actions.

“ClickUp hosted MCP exposes task, hierarchy, document and time-tracking tools.”

01 / THE REASONING

Why this made the selection.

  • Official hosted integration with documented authentication and account permissions.
  • Review sprint tasks and threaded discussion before proposing status/assignee changes.
  • ClickUp documents a remote MCP server at https://mcp.clickup.com/mcp that exposes many of the API’s capabilities.
  • The assistant can only do what the authorizing user can do, and on Team, Enterprise, and Edu workspaces only owners and admins can configure MCP servers.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server-1
  • https://developer.clickup.com/docs/mcp-tools
  • Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

Our findings

  • Official setup and tools pages establish OAuth, selected Workspace access and a broad mutation surface.
  • Tool documentation uses conditional confirmation wording; the catalogue does not upgrade that into a mandatory gate.
  • The tools page says the ClickUp MCP exposes many capabilities of the ClickUp API, and that the assistant can only perform actions the user has permission to do.
  • The setup page gives the remote URL https://mcp.clickup.com/mcp and OAuth as the authentication selection in the documented clients.
  • In Team, Enterprise, and Edu workspaces, only owners and admins have permission to configure MCP servers.
  • The tool catalog includes task deletion, bulk task mutations, dependencies and comments that can mention other users.

Not established by this review

  • Server startup, authentication, live tool execution and security isolation were not tested.
  • Published package/container parity with a source revision and hosted implementation internals were not tested.
  • The resource was not executed and its tools were not called.
  • The server was not called. A source review is not a runtime or security certification.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. Add the remote HTTP endpoint and complete OAuth, choosing the intended Workspaces.
  2. Inspect workspace hierarchy and resolve assignees before creating tasks or moving them between Lists.
  3. Review individual targets and proposed messages/time entries before allowing write tools.
  4. Resolve the exact task/List and inspect affected records before a bulk operation; configure client confirmation for deletion and outbound comments.

Before you start

  • An account with the required publisher permissions and a compatible remote MCP client.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "clickup": {
      "type": "http",
      "url": "https://mcp.clickup.com/mcp"
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server-1

    Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports

  2. https://developer.clickup.com/docs/mcp-tools

    Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports

Evidence & Ask