ClickUp + Muse

How to connect ClickUp to Muse

Use Muse 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 Muse to prepare a handoff from a specific ClickUp task while keeping the work read-only. Ask Muse to create a custom connector for Agent200, then enter credentials through its secure credential interface. The ClickUp task description is source material for the handoff, not permission to send messages or change work.

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

Connector
ClickUp
Works with
Muse · 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.
  • Muse, with custom MCP servers allowed. Muse creates custom connectors from a chat, and your key goes into its secure credentials sheet, never into the chat. Muse Code reads servers from its settings file.

Connect ClickUp to Muse

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

    .env
    Conceptual example
    Store 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. 2

    Step 2: Ask Muse to create the connector

    Ask Muse to create a custom connector for Agent200’s remote MCP server at https://api.agent200.com/mcp/, using Streamable HTTP and an Authorization: Bearer header. Request a secure credential entry flow; do not put the key in the message.

    Muse chat
    MCP: message that asks Muse to create the custom connector
    Create a Custom Connector for the Agent200 remote MCP server and connect to it:
    Name: Agent200
    Transport: remote streamable HTTP
    URL: https://api.agent200.com/mcp/
    Auth: API key sent in the Authorization header as "Bearer <key>"
    Open the secure credentials store so I can enter the API key there, not in this chat.
    Then list its tools to confirm the connection works.
  3. 3

    Step 3: Enter the key securely and inspect tools

    Use the secure credential interface Muse provides, then ask it to list the available ClickUp read tools. If setup fails, inspect the reported error before asking for task data.

  4. 4

    Step 4: Authorize ClickUp and read one task

    Complete the ClickUp authorization link when requested. Identify an accessible task and run the read-only test below. Review the handoff in chat.

Test your connection

Run one request to check everything is wired up.

Ask

Read the ClickUp task I identify and prepare a short handoff for me to review. Include the assignees, due date and status only when returned. Ask for the task ID if needed. Do not send the handoff 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 Muse.

Agent brief
Goal: connect ClickUp to Muse with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/clickup/framework/muse/

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 Muse'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 Muse: 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 Muse'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 prepare a short handoff for me to review. Include the assignees, due date and status only when returned. Ask for the task ID if needed. Do not send the handoff 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/muse.md

ClickUp tools Muse 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 Muse

    In your own words, for something in ClickUp.

  2. 02

    Muse 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

    Muse 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

Does preparing a handoff send it to anyone?

No. Ask Muse to show the handoff in your conversation for review. Reading ClickUp through the tools on this page does not send a message, assign a task or mark it complete.

Use ClickUp with another framework

200 OK

ClickUp, connected to Muse.
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)