ClickUp MCP | OAuth ClickUp connector for AI agents

Tools your project management agent reaches for on ClickUp, scoped per user.

CALL ANY TOOL

List tasks and spaces, create or update tasks, add comments, and track priority and status.

clickup_checklist_item_create

Create checklist item

Add a new item to an existing ClickUp task checklist.

Parameters

Name

Type

Required

Description

checklist_id

string

Required

Checklist ID (UUID)

name

string

Required

Item label

assignee

integer

Optional

User ID to assign to this item

clickup_comment_create

Create comment

clickup_comment_create_list

List comment create

clickup_comment_delete

Delete comment

clickup_comment_get_list

List comment get

clickup_comment_get_task

Comment Get Task

clickup_comment_update

Update comment

clickup_folder_create

Create folder

clickup_folder_delete

Delete folder

clickup_folder_get

Get folder

clickup_folder_get_all

Folder Get All

clickup_folder_update

Update folder

clickup_goal_create

Create goal

clickup_goal_delete

Delete goal

clickup_goal_get

Get goal

clickup_goal_get_all

Goal Get All

clickup_goal_update

Update goal

clickup_list_create

Create list

clickup_list_create_folderless

List Create Folderless

clickup_list_delete

Delete list

clickup_list_get

Get list

clickup_list_get_all

List Get All

clickup_list_get_folderless

List Get Folderless

clickup_list_members_list

List list members

clickup_list_update

Update list

clickup_list_views_list

List list views

clickup_space_create

Create space

clickup_space_delete

Delete space

clickup_space_get

Get space

clickup_space_get_all

Space Get All

For more tools, view docs.

Build your Agent

Drop the toolkit in, point it at the user, and your project management agent can use ClickUp from the first run.

import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["clickup"], toolNames: ["clickup_tasks_list", "clickup_task_get", "clickup_task_create"] },
  pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  schema: z.object({}).passthrough(),
  func: async (args) => {
    const { data } = await sk.tools.executeTool({
      toolName: t.tool.definition.name,
      identifier: "user_123",
      params: args,
    });
    return JSON.stringify(data);
  },
}));

const agent = createReactAgent({ llm, tools: lcTools });

import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["clickup"], toolNames: ["clickup_tasks_list", "clickup_task_get", "clickup_task_create"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  type: "function",
  function: {
    name: t.tool.definition.name,
    description: t.tool.definition.description,
    parameters: t.tool.definition.input_schema,
  },
}));

const resp = await openai.responses.create({
  model: "gpt-4o", input: prompt, tools: llmTools,
});

import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["clickup"], toolNames: ["clickup_tasks_list", "clickup_task_get", "clickup_task_create"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
  model: "claude-sonnet-4-6", max_tokens: 1024,
  tools: llmTools,
  messages: [{ role: "user", content: prompt }],
});

import { Agent } from "@google/adk/agents";
import {
  MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
  connectionParams: new StreamableHTTPConnectionParams({
    url: "https://mcp.scalekit.com/clickup",
    headers: { Authorization: `Bearer ${userScopedToken}` },
  }),
});

const agent = new Agent({
  name: "agent", model: "gemini-2.0-flash",
  tools: await toolset.getTools(),
});

Try these prompts

Paste any prompt into your agent to start using ClickUp.

Search & recall

Copy the prompt

Copied

List all tasks assigned to me in [list].

Copy the prompt

Copied

Show me overdue tasks in [space].

Copy the prompt

Copied

Find tasks with priority urgent.

Copy the prompt

Copied

What tasks have no assignee?

Action & creation

Copy the prompt

Copied

Create a task in [list]: [name], due [date], assignee [person].

Copy the prompt

Copied

Mark task [name] as complete.

Copy the prompt

Copied

Update priority of [task] to urgent.

Copy the prompt

Copied

Comment on [task]: [text].

Reporting & sprints

Copy the prompt

Copied

Which tasks shipped this week?

Copy the prompt

Copied

How many open tasks by status in [list]?

Copy the prompt

Copied

Show velocity for [team] this sprint.

Copy the prompt

Copied

Find tasks with no due date in [space].

SEE HOW AUTH WORKS

Users authorize ClickUp once. Their credentials stay vaulted, every call is checked, and every action is logged.

Authorize

Your user connects

ClickUp

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

ClickUp

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

ClickUp

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

ClickUp

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

Same per-user auth pattern across other project management agents and MCP connectors. Working code, live demos, fork what fits.

ENGINEERING

DevOps assistant agent

Triage GitHub incidents, open Linear tickets, and notify the on-call channel in Slack with context already attached.

ENGINEERING

Engineering standup agent

Aggregate GitHub and GitLab activity, link to Jira, and post a daily standup digest to Slack. No async updates.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.

01.

Task updates lose workspace attribution

A shared ClickUp token looks fine in a demo. In production, every task update, list write, and space change logs as the integration. Task ownership breaks. Workspace attribution breaks. Scalekit resolves the actual user's token so every ClickUp action is attributed to the right person.

// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

ClickUp today. Asana, Jira, Linear tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access ClickUp as the user or as a shared key?

As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the ClickUp oauth 2.0 stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in ClickUp?

Yes. Pass a tool name filter to listScopedTools so the project management agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches ClickUp.

What happens when a user revokes ClickUp access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Does the agent respect ClickUp workspace and space permissions?

Yes. Lists, folders, and spaces inherit the authorizing user's role. Guest access, member scope, and private space visibility all apply. The agent cannot read or write what the user cannot.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit