clickup-mcp: Command for Claude Code

.claude/commands/add-tool.md

add-tool is a command for Claude Code from TwoFeetUp/clickup-mcp. It costs 0 tokens per session (604 once invoked), scanned A, original, MIT.

A guide for adding a new MCP tool to a ClickUp server. MCP tools let an AI agent call specific actions in another application.

In plain words
What is it for?
Use it when creating a new ClickUp tool, choosing its schema, implementing its handler, and checking whether an existing tool should be extended instead.
Why use it?
It gives developers a defined process for designing the tool's inputs and connecting them to ClickUp operations. This reduces guesswork when deciding where the code belongs and how it should behave.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md.

This is TwoFeetUp/clickup-mcp's own configuration. It tells Claude Code how to work on clickup-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything clickup-mcp configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is CLICKUP_API_KEY=pk_xxx CLICKUP_TEAM_ID=xxx node playground/test-new-tool.js.

Reuse

Borrowing it

Nothing to install: this file belongs to TwoFeetUp/clickup-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/TwoFeetUp/clickup-mcp/main/.claude/commands/add-tool.md
Clone the repo
git clone --depth 1 https://github.com/TwoFeetUp/clickup-mcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for add-tool

README.md
[![agentmods](https://agentmods.dev/badge/commands/twofeetup/clickup-mcp/add-tool/github.svg)](https://agentmods.dev/commands/twofeetup/clickup-mcp/add-tool)
Your own site
<a href="https://agentmods.dev/commands/twofeetup/clickup-mcp/add-tool"><img src="https://agentmods.dev/badge/commands/twofeetup/clickup-mcp/add-tool/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for add-tool

Your own site · 80×15
<a href="https://agentmods.dev/commands/twofeetup/clickup-mcp/add-tool"><img src="https://agentmods.dev/badge/commands/twofeetup/clickup-mcp/add-tool.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 604 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00604
Opus 5.5 $0.00000 $0.00242
Sonnet 5.5 $0.00000 $0.00121
Haiku 4.5 $0.00000 $0.00060

Measured 1mo ago against content hash 8cf34b170bba, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

add-tool scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/add-tool.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Add New Tool

Guide for adding a new MCP tool to the ClickUp server.

Before Starting

  1. Read MCP_DESIGN_PRINCIPLES.md for AI-first design guidelines
  2. Check if functionality can be added to an existing consolidated tool
  3. Consider: Does this tool follow user intent or API structure?

Steps

1. Design the Tool Schema

Create or update tool schema in src/tools/:

  • Task-related: src/tools/task/consolidated-tools.ts
  • Container-related: src/tools/container-tools.ts
  • New category: Create src/tools/$ARGUMENTS-tools.ts
export const myNewTool = {
  name: "tool_name",
  description: "AI-friendly description of what this tool does. Include when to use it.",
  inputSchema: {
    type: "object",
    properties: {
      action: {
        type: "string",
        enum: ["get", "create", "update", "delete"],
        description: "REQUIRED: Operation to perform"
      },
      // ... other parameters
    },
    required: ["action"]
  }
};

2. Implement the Handler

Create handler in corresponding file:

export async function handleMyNewTool(params: any) {
  const { action, ...rest } = params;

  // Validate required parameters
  if (!action) {
    return { isError: true, content: [{ type: "text", text: "Missing required parameter: action" }] };
  }

  // Route to appropriate action
  switch (action) {
    case "get": return handleGet(rest);
    case "create": return handleCreate(rest);
    default: return { isError: true, content: [{ type: "text", text: `Unknown action: ${action}` }] };
  }
}

3. Register the Tool

In src/server.ts:

  1. Import the tool schema and handler
  2. Add tool to ListToolsRequestSchema handler
  3. Add case to CallToolRequestSchema switch statement

4. Test

npm run build
# Create test in playground/
CLICKUP_API_KEY=pk_xxx CLICKUP_TEAM_ID=xxx node playground/test-new-tool.js

5. Document

Update root CLAUDE.md with new tool in "Available MCP Tools" section.

Read the full file on GitHub · 90 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 90 lines · 0 tokens per session scan A 8cf34b170bba

Subscribe to this mod's changes

add-tool is a command published in the GitHub repository TwoFeetUp/clickup-mcp (0 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 604 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.