How to integrate Zoom MCP with OpenCode

Trusted by teams at
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Zoom logo
OpenCode logo
divider

How to integrate Zoom MCP with OpenCode

This guide explains how to connect Zoom MCP to OpenCode using Composio Connect, which simplifies OAuth, API changes, and reliability concerns.

There are two ways to set this up:

Also integrate Zoom with

Why use Composio?

Composio provides a single MCP server or CLI tool that exposes a set of meta-tools, allowing you to:

  • Connect to 1,000+ apps with on-demand tool loading, so you do not fill your LLM context window with unnecessary tool definitions.
  • Use programmatic tool calling through a remote Bash tool, letting LLMs write their own code to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Handle large tool responses outside the LLM context to keep conversations lean.

Connect Zoom with OpenCode

Option 1: Using Composio CLI

1. Install Composio CLI

Install the Composio CLI, authenticate, and initialize your project:

bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Authenticate with Composio
composio login

During login, you will be redirected to the sign-in page. Finish the flow and you are all set.

Composio CLI authorization screen

2. Authorize Zoom

Once the CLI is installed, it is essentially done. Give OpenCode access to your apps with these steps:

  1. Launch OpenCode.
  2. Prompt it to "Authenticate with Zoom Composio".
  3. Complete the authentication and authorization flow, and your Zoom integration is all set.
  4. Start asking anything you want.

Option 2: Using Composio MCP

You can also connect Zoom to OpenCode by adding Composio as an MCP server through the OpenCode CLI.

1. Add the Composio MCP server

bash
opencode mcp add

This launches an interactive prompt.

2. Fill in the fields

FieldValue
Namecomposio
Typeremote
URLhttps://connect.composio.dev/mcp
Require OAuthYes
Have client IDNo
OpenCode MCP server interactive prompt for Composio

Alternatively, you can skip the interactive prompt and paste the configuration directly into your OpenCode config file.

Open your global OpenCode config:

bash
open ~/.config/opencode/opencode.json

Add this under the mcp key and save the file.

bash
{
  "mcp": {
    "composio": {
      "type": "remote",
      "url": "https://connect.composio.dev/mcp",
      "enabled": true
    }
  }
}

3. Authenticate

Authenticate the Composio MCP server you just added:

bash
opencode mcp auth composio

This opens a browser session. Authorize Composio and you are done.

Composio browser authorization for OpenCode MCP

4. Verify installation

bash
opencode mcp list

5. Connect Zoom with OpenCode

Now, in the chat, ask the agent to connect to Zoom or give it any Zoom-related task.

For example, ask it to:

  • "Schedule a Zoom meeting for tomorrow"
  • "Add a registrant to your next webinar"
  • "Summarize your last recorded meeting"

It will prompt you to authenticate and authorize access to Zoom.

That is it. Composio tools are now available in OpenCode, and your Zoom account is ready to use.

Supported Tools & Triggers

Tools
Triggers
Add a meeting registrantThis text guides on creating and customizing a user's registration for a zoom meeting, with a max of 4,999 registrants.
Add a webinar registrantZoom users with a webinar plan can create and manage webinars, broadcasting to up to 10,000 attendees.
Create a meetingEnable zoom meeting creation via user-level apps with "me".
Delete meeting recordingsSummary: to delete all meeting recordings, ensure the user's account has cloud recording enabled.
Get a meetingThe text provides details on api permissions for reading meeting information, categorizing permissions into general and granular scopes, and labels the rate limit as 'light'.
Get a meeting summaryMeeting summary info requires a pro+ host plan, ai companion enabled, excluding e2ee meetings.
Get a webinarAccess zoom webinar details requires pro or higher plan and webinar add-on.
Get daily usage reportThe daily report provides zoom service usage details, like new users, meetings, participants, and minutes per day for a month, requiring a pro plan or higher.
Get meeting recordingsTo download meeting recordings, use `download url`.
Get past meeting participantsApi allows paid users (pro+) to fetch past meeting attendee info, excluding solo participants.
List all recordingsThis text details how to list zoom cloud recordings for a user, notably by using "me" for user-level apps and requiring an oauth token for access.
List archived filesZoom's archiving solution enables administrators to automatically record and archive meeting data to third-party platforms for compliance, needing the meeting and webinar archiving feature enabled.
List devicesThis api lets you list devices.
List meetingsThis zoom api lists a user's scheduled meetings using the `me` value for user-level apps, excluding instant meetings and only showing unexpired ones.
List webinar participantsGet a list of past webinar participants with a pro plan or above plus an add-on.
List webinarsThe api lists all scheduled webinars for zoom users with a webinar plan, using `me` for user-level apps.
Update a meetingTo update a meeting via api, ensure `start time` is future-dated; `recurrence` is needed.

Way Forward

Now that Zoom is connected, extend your setup by connecting the other apps you already use every day, so your agent can run true cross-app workflows end to end.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single MCP endpoint, your agent can coordinate multiple tools safely and reliably in one conversation.

How to build Zoom MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Zoom MCP?

With a standalone Zoom MCP server, the agents and LLMs can only access a fixed set of Zoom tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Zoom and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with OpenCode?

Yes, you can. OpenCode fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Zoom tools.

Can I manage the permissions and scopes for Zoom while using Tool Router?

Yes, absolutely. You can configure which Zoom scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Zoom data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.