Zoom for Claude

Search Zoom meetings and transcripts, schedule, edit or delete meetings, share Canvas docs.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Zoom for Claude connector does

The Zoom for Claude MCP server connects your Zoom account to Claude, ChatGPT and any MCP-compatible agent. Zoom documents 24 tools: search meetings, chat and Canvas, read transcripts and summaries, create Zoom Docs, and now schedule, update and delete meetings and manage who sees a Canvas file. Two tools delete things. Sign-in is OAuth against zoom.us, with 22 named scopes.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Zoom for Claude tools (24)

  • search_meetings
  • recordings_list
  • get_meeting_assets
  • get_recording_resource
  • create_new_file_with_markdown
  • get_file_content
  • hub_create_file_from_content
  • hub_get_file_content
  • search
  • my_notes_get_note_content
  • search_describe_capabilities
  • ask
  • meeting_create
  • meeting_update
  • capabilities_invoke_read
  • capabilities_invoke_write
  • capabilities_describe
  • capabilities_discover
  • meeting_delete
  • canvas_add_file_collaborators
  • canvas_list_file_collaborators
  • canvas_modify_file_collaborator_role
  • canvas_remove_file_collaborator
  • in_meeting_control

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Two tools delete things, and one deletes a whole series. meeting_delete removes every occurrence of a recurring meeting unless given an occurrence_id; canvas_remove_file_collaborator revokes someone's access to a doc. Withhold their scopes unless you need them.
  • Meeting writes are capped per host. Zoom limits meeting_create and meeting_update to 100 requests per day each, counted against the meeting host.
  • Live controls need the host and a live meeting. in_meeting_control works only when the caller is the host or alternative host, and its recording controls apply to cloud recordings only.
  • Scopes are a real boundary, with one sharp edge. Twenty-two named scopes separate reading, writing and deleting. But cloud_recording:read:content unlocks full transcripts of other people's speech, and no finer grant exists below it.
  • The discovery tools publish no scope of their own. What capabilities_invoke_write can do depends on the servers it reaches; Zoom's docs show the Workflows server today.
  • The connector is thin without AI Companion. Zoom states it depends on Smart Recording and Meeting Summary. You also reach only meetings you hosted or were granted access to, and ask requires Zoom AI Credits.
  • Rate limits are shared and account-wide. Zoom states MCP rate limits are shared with Zoom Open APIs, applied at the account level across all apps on the account, and vary by plan. Zoom grades each direct tool LIGHT or MEDIUM, with CANVAS-IMPORT and CANVAS-EXPORT classes for the Docs and hub tools. It does not publish the numbers on the MCP page.
  • Content is capped at 100 KB. Both document-creating tools reject content above that size.
  • We could not read tool safety annotations or schemas. The endpoint returned 401 to an anonymous request, so no readOnlyHint or destructiveHint is published here, and Zoom's page no longer publishes input or output schemas. The effect of each tool comes from its documented scope.
  • The server declares resources we could not list. Zoom's MCP server card marks this server resources: true and prompts: false. Without signing in we could not list them.
  • Zoom's connector page is missing from its own llms.txt. The index at developers.zoom.us/llms.txt lists the Claude connector and server overview pages but not /docs/mcp/zoom/, the page with the tool list.
  • Whether reading a recording notifies its host is unresolved. We found no Zoom documentation stating whether transcript access is logged or shown to the meeting host, and we did not test it.

Frequently asked questions

Can the Zoom connector schedule or start a meeting?

It can schedule one, and it can control one in progress. Zoom now documents meeting_create, meeting_update and meeting_delete, plus in_meeting_control, which lets the host start or stop a cloud recording and invite participants during a live meeting. Each needs its own OAuth scope, so you can grant search without granting meeting changes.

Can the Zoom connector send a meeting invitation to anyone?

Partly. in_meeting_control can invite participants into a meeting that is already live, and canvas_add_file_collaborators shares a Canvas doc with Zoom users or Team Chat channels. Zoom's description of meeting_create does not say it emails invitees, and the server's input schemas are not published, so do not rely on it to send invitations.

Can the Zoom connector read my meeting transcripts?

Yes. Zoom documents get_recording_resource as returning a recording's transcript, summary, next steps and playback link, and my_notes_get_note_content can attach the meeting transcript to a note. Reading a transcript puts other participants' recorded speech into the agent's context, and it needs the cloud_recording:read:content scope specifically.

How many tools does the Zoom for Claude MCP server have?

Twenty-four. Zoom's developer page lists 24 tools for this server, and Anthropic's directory listing names the same 24 on 2026-11-17. Twenty are direct tools with a published OAuth scope; four capabilities_ discovery tools reach further tools on Zoom's separate Workflows server. The server's descriptor advertises 22 OAuth scopes.

What are the capabilities tools in the Zoom connector?

They are a gateway to other Zoom MCP servers. capabilities_discover finds tools across connected sources, capabilities_describe returns their schemas, and capabilities_invoke_read and capabilities_invoke_write call them. Zoom's docs show this reaching the Zoom Workflows server, whose nine tools can deploy, run, resume and undeploy workflow automations.

What OAuth permissions does the Zoom MCP server request?

Twenty-two named application scopes: twelve read and ten that create, update or delete. The server's RFC 9728 descriptor lists them, including meeting:write:meeting, meeting:delete:meeting and docs:delete:collaborator. Because the delete scopes are separate from the read ones, you can grant search and transcript access while withholding the power to delete meetings.

Why does the Zoom connector return nothing for my meetings?

Almost certainly because AI Companion is off. Zoom states the connector depends on the Smart Recording and Meeting Summary features, and that without both enabled the app may have limited functionality. You also only reach assets for meetings you hosted or were granted access to, and video features require the meeting to have been cloud-recorded with Smart Recording.

What plan do I need for the Zoom for Claude connector?

A paid Zoom Workplace plan and admin involvement. Zoom requires a licensed user on Workplace Pro, Pro Plus, Business, Business Plus, Enterprise, Enterprise Plus or Enterprise Bundle, plus a Zoom account owner or admin with privileges and a Claude account. The recordings_list tool separately states it needs a Pro or higher plan with Cloud Recording enabled.

Sources

Use it in an agent

Put Zoom for Claude to work.

Connect Zoom for Claude once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.