# How to connect ClickUp to Claude

> Use Claude with Agent200 to read ClickUp task statuses, assignees and due dates. Build clear handoffs through the user’s own connection.

- Page: https://www.agent200.com/connectors/clickup/framework/claude/
- Connector: [ClickUp](https://www.agent200.com/connectors/clickup.md)
- Framework: Claude
- Updated: 2026-11-17

## Instructions for AI agents

Goal: connect ClickUp to Claude with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/clickup/framework/claude/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Claude's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure ClickUp is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Claude: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Claude's exact menus or commands.
4. The first ClickUp request returns an authorization link if the user has not connected ClickUp yet: show it to them and continue once they have approved access on ClickUp's own page.
5. Check it works with this request: "Read the ClickUp task I identify and summarize its assignees, due date, status and next steps stated in its description. Ask me for the task ID if it is missing. Do not change anything."
   What should come back:
   - The selected task is identified clearly.
   - The answer preserves its returned status, includes all returned assignees and reports its due date when available.
   - Missing data and access failures are stated clearly; no ClickUp records or comments are changed.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in ClickUp, then retry.

## Overview

Use Claude to turn a selected task into a concise briefing before a meeting. Start with one task whose ID you already know, so you can compare the returned record with ClickUp. Separate what the task says from questions you still need to ask its assignees.

Begin with one task the connected user can access. The ClickUp catalogue on this page is read-only: a briefing does not create, assign, complete or delete work. Discover the available tools and use their returned schemas before running the test.

Product reference: [Claude documentation](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp). For task identity and response scope, see [ClickUp’s task reference](https://developer.clickup.com/reference/gettask).

- **Connector:** [ClickUp](https://www.agent200.com/connectors/clickup/)
- **Works with:** Claude · Agent app, through MCP
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [8 tools](https://www.agent200.com/connectors/clickup/framework/claude/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **ClickUp enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a ClickUp account.** They approve access once, on ClickUp's own page.
- **Claude, with custom MCP servers allowed.** Custom connectors are on every Claude plan (Free: one). Sending an API key uses the Request headers option, a beta that only some accounts have; on Team and Enterprise an Owner adds the connector for everyone.

## Connect ClickUp to Claude

### Step 1: Create your Agent200 API key

Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude in the next step, as "Authorization: Bearer <your key>". One key covers ClickUp and every other connector enabled for your project. Keep it out of chats and source control.

Create an API key: https://agent200.com/platform/apikeys/

### Step 2: Open Connectors in Claude

On a Free, Pro, Max or Ultra plan, go to **Customize > Connectors**. On Team or Enterprise, an Owner goes to **Organization settings > Connectors**; members then find the connector under Customize > Connectors.

### Step 3: Add a custom connector

Select **Add**, then **Add custom connector**. Enter a name, Agent200, and the remote MCP server URL, then choose **Continue**.

### Step 4: Send your key as a request header

Under Authentication choose **No sign-in**. Open **Request headers**, pick `authorization`, enter `Bearer` followed by a space and your key, mark it Required and choose **Add**. Claude sends the value exactly as typed.

File `Add custom connector`:

```text
Remote MCP server URL:  https://api.agent200.com/mcp/
Authentication:         No sign-in
Request header name:    authorization
Value:                  Bearer YOUR_AGENT200_API_KEY
```

### Step 5: Turn it on in a chat

In a chat, select **+ > Connectors** and turn Agent200 on. Ask Claude to list the Agent200 tools to check the connection; Claude asks before a tool runs the first time.

### Step 6: Connect your ClickUp account

The first time you ask Claude for something in ClickUp, Agent200 returns an authorization link. Open it and approve access on ClickUp's own page. Agent200 stores the connection and keeps it working; your password never reaches Claude or Agent200.

## Test your connection

Ask: "Read the ClickUp task I identify and summarize its assignees, due date, status and next steps stated in its description. Ask me for the task ID if it is missing. Do not change anything."

What should come back:

- The selected task is identified clearly.
- The answer preserves its returned status, includes all returned assignees and reports its due date when available.
- Missing data and access failures are stated clearly; no ClickUp records or comments are changed.

Use a task the connected user can open in the authorized Workspace. Check the runtime schema if using a custom task ID. Report missing data and preserve the task’s returned status label.

## ClickUp tools Claude can call

- **Read a task** (`clickup_get_task`, read): Retrieve a task’s description, status, assignees and due date when available.
- **List tasks** (`clickup_list_tasks`, read): Read tasks in a selected List, with attention to pagination and the requested task filters.
- **Read task comments** (`clickup_get_task_comments`, read): Read comments on a task to add discussion context to a handoff.
- **Read a List** (`clickup_get_list`, read): Read a List’s details to understand the container for the selected work.
- **List Lists in a Folder** (`clickup_list_lists`, read): Find the Lists inside a selected Folder.
- **List folderless Lists** (`clickup_list_folderless_lists`, read): Find Lists that sit directly in a Space rather than inside a Folder.
- **List Folders** (`clickup_list_folders`, read): Read the Folders in a selected Space to locate the work the user requested.
- **List Spaces** (`clickup_list_spaces`, read): Read the Spaces available in a selected Workspace.

## How it works

1. **You ask Claude.** In your own words, for something in ClickUp.
2. **Claude picks a tool.** It sees the ClickUp tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** With your own ClickUp connection, within the tools and scopes your project allows.
4. **Claude answers.** It gets the result back from the MCP server and uses it in its reply or its next step.

**Each user's own connection.** Connections belong to individual end users. A request for one user never reaches another user's ClickUp account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and ClickUp enforces what its API grants.

## Troubleshooting

### The task cannot be found or read

Check the selected task and authorized ClickUp Workspace. Distinguish native task IDs from custom IDs and use the inputs your tool actually supports. Report a refused call instead of guessing a task or a successful result.

### The answer names only one person or changes the status meaning

Compare the answer with the returned record. Keep every returned assignee and the recorded status label. A missing field is not evidence that a task is unassigned or complete.

### The List summary seems incomplete

Check pagination and the task filters available in the runtime. State the result scope and avoid treating one page as the full List. See [ClickUp’s List task reference](https://developer.clickup.com/reference/gettasks).

## FAQ

### Should my first Claude test summarize a whole List?

Start with one identified task and compare the answer with ClickUp. Once that read works, ask for a List briefing with an explicit scope. Review pagination and filters before accepting a claim that all work was included.

## Use ClickUp with another framework

- [ClickUp + ChatGPT](https://www.agent200.com/connectors/clickup/framework/chatgpt.md)
- [ClickUp + Claude Code](https://www.agent200.com/connectors/clickup/framework/claude-code.md)
- [ClickUp + Muse](https://www.agent200.com/connectors/clickup/framework/muse.md)
- [ClickUp + Grok Bot](https://www.agent200.com/connectors/clickup/framework/grok-bot.md)
- [ClickUp + OpenAI Dots](https://www.agent200.com/connectors/clickup/framework/openai-dots.md)
- [ClickUp + Claude Duet](https://www.agent200.com/connectors/clickup/framework/claude-duet.md)
- [ClickUp + Hermes Agent](https://www.agent200.com/connectors/clickup/framework/hermes-agent.md)
- [ClickUp + OpenClaw](https://www.agent200.com/connectors/clickup/framework/openclaw.md)
- [ClickUp + LangGraph](https://www.agent200.com/connectors/clickup/framework/langgraph.md)
- [ClickUp + OpenAI Agents SDK](https://www.agent200.com/connectors/clickup/framework/openai-agents-sdk.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
