Zoom for Claude MCP server icon

Zoom for Claude

by Zoom for Claude

HIPAA CompliantSOC2 ReadyISO 27001 Ready
Productivity12 tools

Search Zoom meetings, read recording transcripts and summaries, and create Zoom Docs from an AI agent. Zoom documents 12 tools; Anthropic's directory lists 9. Eleven named OAuth scopes separate reading from writing.

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.

Connect Zoom for Claude via MCP

https://mcp.zoom.us/mcp/zoom/streamable

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Zoom for Claude Tools & Capabilities (12)

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

Limits

  • Anthropic's tool list is three names short and one name wrong. It omits ask, search, search_describe_capabilities and my_notes_get_note_content, and includes search_zoom, which no Zoom source acknowledges. Build against Zoom's documented twelve.
  • Scopes are a real boundary, and one of them is the sharp one. Eleven named scopes separate reading from writing, so document creation can be withheld. But cloud_recording:read:content is the scope that unlocks verbatim transcripts of other people's speech, and no finer grant exists below it — you cannot grant summaries without granting the full transcript.
  • Nothing here schedules a meeting or sends anything. If that is what you wanted, this is the wrong Zoom server; Zoom operates separate Chat, Docs and Whiteboard MCP servers at other endpoints, and its Chat server is documented as sending and editing messages.
  • The connector is useless without AI Companion. Zoom states it depends on Smart Recording and Meeting Summary, and that functionality is limited without both. You also reach only meetings you hosted or were granted access to.
  • 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 installed on the account, and vary by account plan. Zoom's tool documentation grades each tool LIGHT, MEDIUM or HEAVY, and the two Canvas tools carry their own CANVAS-IMPORT and CANVAS-EXPORT classes. Zoom does not publish the numeric limits on the MCP page.
  • Content is capped at 100 KB. Both write tools reject content above that size.
  • We could not read tool safety annotations. The endpoint returned 401 to an anonymous request, so no readOnlyHint or destructiveHint is published here. The read/write split comes from Zoom's documented per-tool scopes, which is strong but is not the server's own declaration.
  • The server declares resources, and they are UI widgets rather than data. Zoom's MCP catalogue card marks this server resources: true and prompts: false, and the three resources its docs list — meeting-recap, meeting-recording and meeting-list-card — are OpenAI Apps SDK display widgets. They are not a readable context surface, and we could not list them live.
  • SSE is documented for the server family but not offered here. Zoom's general MCP page says its servers support both SSE and streamable HTTP; this server's own entry publishes a streamable endpoint only.
  • Zoom's connector page is missing from its own llms.txt. The 250 KB index at developers.zoom.us/llms.txt lists every other MCP page but not /docs/mcp/zoom/, the URL Anthropic's directory nominates as this connector's documentation. An agent following the machine index alone would never find the tool list.
  • Whether reading a recording notifies its host is unresolved. We found no Zoom documentation stating whether transcript access is logged or surfaced to the meeting host, and we did not test it. Treat it as unknown rather than as a no.

Frequently asked questions

No. None of the 12 tools Zoom documents creates, schedules, starts or ends a meeting, and no OAuth scope on the server grants meeting write access. The words schedule and invitee appear only as read-side output fields describing meetings that already exist. The connector reads your meeting history and writes documents, nothing else.

No. Nothing on this server sends mail, posts a chat message or notifies a person. There is no recipient, participant or invitee input parameter on any tool, and no messaging scope in the eleven the server advertises. The only outbound-shaped path is a created Zoom Doc placed in a shared folder, which is visibility rather than delivery.

Yes, verbatim and with speaker names. The get_recording_resource tool returns transcript text in timestamped segments, chapter summaries, next steps and CDN playback links. Reading a transcript therefore puts other participants' recorded speech into the agent's context, and it needs the cloud_recording:read:content scope specifically.

Zoom documents 12 tools; Anthropic's directory lists 9. Zoom's own developer page enumerates all 12 with schemas, and the server's RFC 9728 descriptor advertises exactly 11 scopes that map one-to-one onto those 12 names. Two independent Zoom sources agree on 12, so treat the directory's 9 as the stale list.

It is a name in Anthropic's directory that Zoom's documentation does not contain. Zoom documents a tool called search with the same job — a multi-datasource query across meetings, chat, Canvas and calendar. The most likely explanation is a rename that the directory listing did not follow. Do not write integration code against search_zoom.

Eleven named application scopes, split nine read to two write. The server's RFC 9728 descriptor lists them, including meeting:read:search, cloud_recording:read:content, docs:write:import and hub:write:content. Because the two write scopes are separate from the nine read ones, you can genuinely grant search and transcript access without granting document creation.

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.

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 in Agentman

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

Open in Agentman Studio

Resources

Server Info

Category
Productivity
Developer
Zoom for Claude
Tools
12
Domain
mcp.zoom.us

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.

Similar MCP Servers for Productivity

Asana logo

Asana

by Asana

Coming Soon
Productivity42 tools
View detailsConnect
Atlassian logo

Atlassian

by Atlassian

Coming Soon
Productivity25 tools
View detailsConnect
ClickUp logo

ClickUp

by ClickUp

Coming Soon
Productivity9 tools
View detailsConnect

Related Resources

Browse All MCP ServersClaude & ChatGPT Setup GuideBrowse AI Skills