Skip to main content
Glama
alexfdez1010

ClickUp API MCP

by alexfdez1010
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CLICKUP_API_KEYYesYour ClickUp personal API token (starts with pk_). Required to authenticate with the ClickUp API. Must be the raw token without a Bearer prefix.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
clickup_search_operationsA

Search the offline API catalog by words, tag, or version. Returns paginated summaries.

clickup_get_operationB

Inspect an operation's description, required path/query parameters, and body schema.

clickup_readC

Execute a catalog GET operation. Inspect its schema first. Returns {status, data}.

clickup_writeA

Execute a catalog POST/PUT/PATCH/DELETE operation with user authorization.

        Inspect the schema first. Uploads use files [{field, filename, content_base64,
        content_type}]; maximum 10 MiB decoded total. For v2 attachments use field
        attachment[0], attachment[1], etc. Never automatically retry failed writes.
        Returns {status, data}.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

TDQS

A3.5/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct role: search the catalog, inspect a specific operation, execute read-only GET calls, and execute mutating calls. The descriptions explicitly guide the agent to inspect schemas before execution, preventing confusion between inspection and execution. There is no overlap in purpose.

Naming Consistency4/5

All tools share the clickup_ prefix and use snake_case, which is consistent. However, two tools follow a verb_noun pattern (search_operations, get_operation) while two are bare verbs (read, write), and the noun is sometimes plural and sometimes singular. This is a minor deviation but still readable and predictable.

Tool Count5/5

Four tools is well-scoped for an API abstraction layer that covers discovery, inspection, and execution of both read and write operations. Each tool earns its place without redundancy, and the count is neither thin nor bloated.

Completeness5/5

The set covers the full lifecycle of interacting with the ClickUp API catalog: discover operations, inspect their schemas, execute GET requests, and execute POST/PUT/PATCH/DELETE requests with file upload support. No obvious gaps remain for an agent to accomplish typical API tasks.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources