Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Zoom to Claude Code

Let Claude schedule meetings and act on recordings in Zoom. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Zoom to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Zoom, you add a Zoom MCP server: a small hosted service that exposes Zoom's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Zoom account. No API keys pasted into config files.

claude mcp add --transport http zoom https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Zoom once connected?

Full read-write Zoom access lets Claude schedule a meeting, update its time or settings, manage registrants on a registration-enabled meeting, and pull the recording and transcript to summarize and follow up. The scheduling and post-meeting work that used to mean switching tabs happens where the meetings already live.

  • Schedule a Zoom meeting with the right host, time, and settings
  • Update an existing meeting's time, topic, or settings
  • Add or remove registrants on a registration-enabled meeting
  • Pull a recording and transcript to draft a summary and action items
  • Cancel or delete a meeting after you approve it
  • Create a recurring meeting series from a single request

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Zoom access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Zoom API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Zoom changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Zoom connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Zoom connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Zoom account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Zoom's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Zoom?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Zoom account it signs in with. Revoking access is one click in Zoom.

More on the Zoom connector

Zoom connector for claude.aiMicrosoft Teams + Claude CodeSlack + Claude CodeCalendly + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us