Skip to main content
Back to the ClickUp MCP server

MCP Gateway · OpenCode

ClickUp icon

Connect ClickUp to OpenCode

OpenCode users can keep ClickUp current without opening a browser tab: logging time, reassigning tasks and reading the team's chat. Speakeasy hosts ClickUp behind its MCP Gateway, so OpenCode connects to it as a remote server and signs in when prompted. Token and cost totals come through the OpenCode plugin, reported per turn.

Category
Project management
Tools
51
Authentication
OAuth
OpenCode
Terminal

Behind the MCP Gateway

Run ClickUp MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every ClickUp call inspected and logged.

Deploy on MCP Gateway

Set up

Add ClickUp to OpenCode in 4 steps

  1. 01

    Add ClickUp from the catalog

    An admin finds ClickUp in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    ClickUp uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use ClickUp

    Give teams the mcp:connect scope on the ClickUp server through team access or a role. OpenCode connects to the ClickUp server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect OpenCode

    Add the server to OpenCode's own mcp config block as a remote server.

    Copy the server's URL from its hosted install page in Speakeasy.

    Add it to the mcp block of your OpenCode config with type set to remote.

    Restart OpenCode and sign in when prompted.

    {
      "mcp": {
        "<server slug>": {
          "type": "remote",
          "url": "<URL from the hosted install page>"
        }
      }
    }
  4. 04

    Sign in and use ClickUp from OpenCode

    The first time OpenCode connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    ClickUp needs its own OAuth grant, so each person connects it once. Until they do, ClickUp calls fail while the rest of the gateway keeps working.

    From then on, ClickUp's tools appear in OpenCode, limited to what the person's access allows, and every call lands in the gateway's tool logs.

OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.

Use cases

What OpenCode users do with ClickUp

Log hours from the terminal

At the end of the day, OpenCode adds manual time entries to the tasks you worked on and reads back what's logged, so timesheets don't wait until Friday.

clickup_add_time_entryclickup_get_task_time_entries

Hand a task to a teammate

OpenCode looks up a teammate by name or email and assigns them the ClickUp task, changing its status as part of the handoff.

clickup_find_member_by_nameclickup_update_task

Read team chat before a change

Before touching shared code, OpenCode reads the team's ClickUp chat channel and its threads for recent decisions about that area.

clickup_get_chat_channel_messagesclickup_get_chat_message_replies

Tools

51 tools

Each ClickUp tool can be allowed or denied per team and role at the MCP Gateway before OpenCode sees it.

clickup_get_workspace_hierarchy

Get workspace hierarchy (spaces, folders, lists) from your authenticated workspace with pagination support. Workspace ID is automatically detected from your session. Returns tree structure with names and IDs for navigation.

clickup_create_task

Create task in a ClickUp list. Requires task name and list_id. ALWAYS ask user which list to use - never guess. Use clickup_get_list to resolve list names to IDs. Supports assignees as array of user IDs, emails, usernames, or "me". , 'Bug', 'Feature').

clickup_get_task

Get task details by task_id (works with regular/custom IDs). Set subtasks=true to include all subtask details.

clickup_filter_tasks

Retrieve tasks with combined filters. Supports filtering by tags, lists, folders, spaces, statuses, assignees, due date range, and completion date range. , tags: ["bug", "feature"] returns tasks with either tag).

clickup_update_task

Update task properties. Requires task_id and at least one update field. Custom fields supported as array of {id, value}. Supports assignees as array of user IDs, emails, usernames, or "me". , 'Bug', 'Feature'), or null to reset to default.

See all 51 tools

Control

What Speakeasy can see and stop in OpenCode

The gateway covers every client the same way. The rest depends on what OpenCode exposes to Speakeasy.

Tool logs

Gateway

Every ClickUp call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the ClickUp tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to ClickUp can reject a tool request before it reaches the server, or withhold a result from OpenCode. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

OpenCode

The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.

Usage telemetry

OpenCode

Token and cost totals flow through the plugin, reported per turn.

Device agent

OpenCode

The device agent installs and maintains the observability package.

  • OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
  • Tool output is blocked at the gateway rather than in OpenCode's hooks.

Questions

Frequently asked questions

Can OpenCode post to ClickUp chat?
Only if the role allows clickup_send_chat_message. Reading channels and sending messages are separate tools, each allowed or denied per team and role at the MCP Gateway.
Where are ClickUp calls from OpenCode checked?
The OpenCode plugin asks Speakeasy to allow or deny each prompt and tool call before it runs. Tool output is blocked at the gateway rather than in OpenCode's hooks.
How do OpenCode users get ClickUp?
An admin adds ClickUp from the Speakeasy MCP Catalog and grants access by team or role. Add the server to OpenCode's own mcp config block as a remote server. Each person then sees only the ClickUp tools their access allows.
Are ClickUp calls from OpenCode logged?
Yes. ClickUp calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

ClickUp in other clients

AI everywhere.

Control here.