Is this an official ClickUp MCP server?

No. It is Memtro's MCP server with Memtro's ClickUp connector behind it: the connector reads ClickUp through its API with the credentials you connect on Dashboard → Connections, and ClickUp publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in ClickUp?

Only when you ask, and only what it has been granted: create a task in a list, or a subtask of one; comment on a task; change a task's status, priority, due date, assignees, title or description, or archive it. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Work management

ClickUp MCP server

ClickUp in any MCP client, through Memtro: ClickUp does not publish this server. Memtro's ClickUp connector reads ClickUp through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Work management: browse workspaces, spaces, folders and lists, find tasks by list, status, assignee, dates or text, read a task with subtasks and comments, read Docs, and look up members; can also create a task, comment on one, and change its status, assignees, dates or description when you ask.

Reads

clickup_workspaceWorkspaces, and the spaces → folders → lists tree (with task counts and list ids) of one workspace.
clickup_tasksFind tasks in a workspace: filter by list/space/folder ids, status names, assignee (id, email or username), updated-since, due window…
clickup_taskOne task by id (the code in its URL, or a custom id with workspace) with full description, custom fields, subtasks and comments.
clickup_docsClickUp Docs: list docs in a workspace (filter by name), or read one doc's pages as Markdown text by doc_id.
clickup_membersPeople in a workspace (id, username, email) to translate assignees or find someone's id; filter by name or email.

Acts, when you ask

These change something in ClickUp. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

clickup_create_taskCreates a task in a ClickUp list.
clickup_comment_taskComments on a ClickUp task.
clickup_update_taskChanges a ClickUp task — its status, priority, due date, assignees, title or description — or archives it.

Connect it

First connect ClickUp on Dashboard → Connections, then add Memtro to your client once. The ClickUp tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared ClickUp connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› What is in progress in the Website Relaunch list?
› Which of Bob's tasks are overdue?
› Summarise the Onboarding Doc
› What did the team complete this week?

Questions

Is this an official ClickUp MCP server?: No. It is Memtro's MCP server with Memtro's ClickUp connector behind it: the connector reads ClickUp through its API with the credentials you connect on Dashboard → Connections, and ClickUp publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in ClickUp?: Only when you ask, and only what it has been granted: create a task in a list, or a subtask of one; comment on a task; change a task's status, priority, due date, assignees, title or description, or archive it. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.