ClickUp + Claude Duet

How to connect ClickUp to Claude Duet

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

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. ClickUp tools
  7. How it works
  8. Troubleshooting
  9. FAQ

Overview

Use Claude Duet for an on-demand ClickUp task briefing through the connectors on your Claude account. Ask it to distinguish the task's recorded state from its interpretation of the next step. An incomplete task alone does not establish whether a project is on track.

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 Duet documentation. For task identity and response scope, see ClickUp’s task reference.

Connector
ClickUp
Works with
Claude Duet · Agent app, through MCP
Authentication
Managed OAuth, per end user
Tools
8 tools
MCP server
https://api.agent200.com/mcp/

Before you start

  • An Agent200 API key. Create one on the API keys page 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 Duet, with custom MCP servers allowed. Claude Duet is a research preview for Pro, Max and Ultra users in the US, by invitation. It uses the connectors of your Claude account, and sending an API key needs Claude's Request headers option.

Connect ClickUp to Claude Duet

  1. 1

    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 Duet 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.

  2. 2

    Step 2: Add Agent200 as a custom connector in Claude

    Duet has no connector settings of its own: it uses those of your Claude account. In Claude, go to Customize > Connectors, choose Add > Add custom connector, enter the server URL, choose No sign-in and add the authorization request header with Bearer and your key.

    Add custom connector
    MCP: Claude custom connector (URL and request header)
    Remote MCP server URL:  https://api.agent200.com/mcp/
    Authentication:         No sign-in
    Request header name:    authorization
    Value:                  Bearer YOUR_AGENT200_API_KEY
  3. 3

    Step 3: Use it from Duet

    Open Claude Duet with the same Claude account. The connectors set up in Claude are there from your first message; manage them in your Claude settings.

  4. 4

    Step 4: Approve actions when Duet asks

    Duet asks before it sends a message, pays, signs or deletes anything. If you cannot approve right away, it finishes the rest and brings the approval back later.

  5. 5

    Step 5: Connect your ClickUp account

    The first time you ask Claude Duet 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 Duet or Agent200.

Test your connection

Run one request to check everything is wired up.

Ask

Read the ClickUp task I identify and tell me what its description says is needed next, who owns it and when it is due. If you cannot read it now, say so. Do not message anyone or change the task.

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.

Get your API key

Create a key in the Agent200 dashboard. It reaches ClickUp and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect ClickUp to Claude Duet.

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

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 Duet'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 Duet: 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 Duet'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 tell me what its description says is needed next, who owns it and when it is due. If you cannot read it now, say so. Do not message anyone or change the task."
   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.

The whole guide is also available as Markdown, for agents and LLMs: /connectors/clickup/framework/claude-duet.md

ClickUp tools Claude Duet can call

  • Read a task

    Read
    clickup_get_task

    Retrieve a task’s description, status, assignees and due date when available.

  • List tasks

    Read
    clickup_list_tasks

    Read tasks in a selected List, with attention to pagination and the requested task filters.

  • Read task comments

    Read
    clickup_get_task_comments

    Read comments on a task to add discussion context to a handoff.

  • Read a List

    Read
    clickup_get_list

    Read a List’s details to understand the container for the selected work.

  • List Lists in a Folder

    Read
    clickup_list_lists

    Find the Lists inside a selected Folder.

  • List folderless Lists

    Read
    clickup_list_folderless_lists

    Find Lists that sit directly in a Space rather than inside a Folder.

  • List Folders

    Read
    clickup_list_folders

    Read the Folders in a selected Space to locate the work the user requested.

  • List Spaces

    Read
    clickup_list_spaces

    Read the Spaces available in a selected Workspace.

How it works

  1. 01

    You ask Claude Duet

    In your own words, for something in ClickUp.

  2. 02

    Claude Duet picks a tool

    It sees the ClickUp tools on the Agent200 MCP server and calls the one the request needs.

  3. 03

    Agent200 runs the call

    With your own ClickUp connection, within the tools and scopes your project allows.

  4. 04

    Claude Duet 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.

FAQ

Is a task briefing a continuous ClickUp monitor?

No. This test checks one request in the current conversation. It does not establish background polling, a refresh interval or delivery of alerts. Review the returned task and the time of the read before acting on the briefing.

Use ClickUp with another framework

200 OK

ClickUp, connected to Claude Duet.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)