ClickUp + OpenClaw
How to connect ClickUp to OpenClaw
Use OpenClaw with Agent200 to read ClickUp task statuses, assignees and due dates. Build clear handoffs through the user’s own connection.
On this page
Overview
Use OpenClaw to read a selected ClickUp task from a conversation. Verify that the saved Agent200 server actually returns tools before asking for task data: saving a server definition and making a successful connection are different checks. Restrict the first request to one task you can open in ClickUp.
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: OpenClaw documentation. For task identity and response scope, see ClickUp’s task reference.
- Connector
- ClickUp
- Works with
- OpenClaw · Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- 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.
- OpenClaw, with custom MCP servers allowed. OpenClaw is open source and self-hosted: anyone running it can add MCP servers, from the CLI, the config file or the Control UI.
Connect ClickUp to OpenClaw
-
1
Step 1: Create your Agent200 API key
Create a key on the API keys page. Enable ClickUp and the read operations needed for this task in your project. Keep credentials out of chats and source control.
.envConceptual exampleStore the Agent200 API key as an environment variable # Keep the key out of your code, prompts and chats. export AGENT200_API_KEY="paste-your-key-here" -
2
Step 2: Store your key in ~/.openclaw/.env
OpenClaw fills
${AGENT200_API_KEY}in its config from~/.openclaw/.env, so the key never sits in the config itself.~/.openclaw/.envMCP: OpenClaw key in ~/.openclaw/.env AGENT200_API_KEY=your-agent200-api-key -
3
Step 3: Save the server
openclaw mcp settakes one JSON object. Always set the transport tostreamable-http: without it OpenClaw uses SSE. Keep the single quotes so your shell leaves${AGENT200_API_KEY}for OpenClaw. In the Control UI, add it under Settings > MCP, then put the header in the config editor on the same page.On current OpenClaw versions, stop the Gateway before CLI changes or live probes against its state. Use the Control UI for supported changes while the Gateway is running.
TerminalMCP: OpenClaw save the server from the CLI openclaw mcp set agent200 '{"url":"https://api.agent200.com/mcp/","transport":"streamable-http","headers":{"Authorization":"Bearer ${AGENT200_API_KEY}"}}' -
4
Step 4: Probe the server
Open a live connection and list the tools Agent200 offers. If a Gateway runs elsewhere, reload or restart it.
A successful probe lists capabilities; the task read below is a separate check of ClickUp access. Restart or reload the appropriate Gateway after configuration.
TerminalMCP: OpenClaw probe the server openclaw mcp doctor agent200 --probe openclaw mcp status --verbose -
5
Step 5: Authorize ClickUp and select a task
Complete the ClickUp authorization link when requested and supply the task ID of a task you can open. Run the read-only test below.
Test your connection
Run one request to check everything is wired up.
Ask
Use Agent200 to read the ClickUp task I identify and summarize its assignees, due date and status. Ask for the task ID if missing. Do not create, assign, complete or delete 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.
Get your API key
Create a key in the Agent200 dashboard. It reaches ClickUp and every other connector enabled for your project.
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 OpenClaw.
Goal: connect ClickUp to OpenClaw with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/clickup/framework/openclaw/ 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 OpenClaw'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 OpenClaw: 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 OpenClaw'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: "Use Agent200 to read the ClickUp task I identify and summarize its assignees, due date and status. Ask for the task ID if missing. Do not create, assign, complete or delete 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.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/clickup/framework/openclaw.md
ClickUp tools OpenClaw can call
-
Read a task
Readclickup_get_taskRetrieve a task’s description, status, assignees and due date when available.
-
List tasks
Readclickup_list_tasksRead tasks in a selected List, with attention to pagination and the requested task filters.
-
Read task comments
Readclickup_get_task_commentsRead comments on a task to add discussion context to a handoff.
-
Read a List
Readclickup_get_listRead a List’s details to understand the container for the selected work.
-
List Lists in a Folder
Readclickup_list_listsFind the Lists inside a selected Folder.
-
List folderless Lists
Readclickup_list_folderless_listsFind Lists that sit directly in a Space rather than inside a Folder.
-
List Folders
Readclickup_list_foldersRead the Folders in a selected Space to locate the work the user requested.
-
List Spaces
Readclickup_list_spacesRead the Spaces available in a selected Workspace.
No tool matches that search.
How it works
-
01
You ask OpenClaw
In your own words, for something in ClickUp.
-
02
OpenClaw picks a tool
It sees the ClickUp tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own ClickUp connection, within the tools and scopes your project allows.
-
04
OpenClaw 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
Why does saving the MCP server not prove ClickUp works?
Saving records a configuration. A live MCP probe checks discovery; a task read checks the selected tool and the connected ClickUp account. Complete both checks and inspect the returned task rather than treating a saved configuration as a successful integration.
