Zoom MCP Tools for AI Agents
Let an agent find upcoming or past Zoom meetings, then read invitations, summaries, transcripts, and recording links.
Available Tools
8 tools available in this integration
Zoom.FindMeetings Find the Zoom meeting a user means, from a phrase, a period, or a meeting id.
Zoom.GetMeetingInvitation Retrieve the invitation note for a specific Zoom meeting.
Zoom.GetMeetingRecording Get a past Zoom meeting's cloud recording as links that can be forwarded.
Zoom.GetMeetingSummary Read the AI Companion meeting summary of a past Zoom meeting.
Zoom.GetMeetingTranscript Read the transcript of a past Zoom meeting.
Zoom.ListUpcomingMeetings List the Zoom meetings a user is scheduled to join, soonest first.
Zoom.SearchMeetings Find the Zoom meetings a user means, from a phrase, a period, or a meeting id.
Zoom.WhoAmI Identify the Zoom user the connection is authenticated as.
Why agent-optimized tools matter
Built for intent, not API schemas
Ask the agent to "find the quarterly planning meeting from last week and summarize what I missed." Arcade picks the right Zoom tools without guessing a meeting ID or date range.
Up to 100x fewer tokens
Zoom meeting searches return lightweight meeting details first and fetch invitations, transcripts, summaries, or recording links only when asked, so the agent does not load every past meeting into the model.
Complete the workflow end to end
Find the meeting, read its invitation, retrieve the transcript and summary, and return the recording links through one toolkit designed around the complete meeting task.
Make actions predictable and controlled
Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.
Securing Zoom
The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.
This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.
Learn about Contextual Access PoliciesFor Zoom, you can implement some of these policies:
- Decide which tools an agent is allowed to see at all. A tool that is never listed cannot be called, whoever is asking.
- Inspect the inputs a call is about to run with, and block it or send it for human approval when they fall outside what the agent should do unsupervised.
- Deny the output of Zoom.GetMeetingRecording for meetings marked confidential, so recording links cannot reach the model or be forwarded by an agent.
- Redact participant names, email addresses, phone numbers, and customer data from Zoom.GetMeetingTranscript results before they reach the model.
- Strip meeting links, passcodes, and dial-in details from Zoom.GetMeetingInvitation results, so an agent cannot expose private access information.
How to use Zoom with your agent
Connect Zoom to your MCP client and give an agent authenticated access to each user's meetings. Follow the setup from authorization through your first meeting lookup.
Your questions, answered
A Zoom MCP server exposes Zoom capabilities as structured tools that an AI agent can call through the Model Context Protocol. After a user authorizes their Zoom account, the agent can find meetings, read invitations, and retrieve recordings, summaries, and transcripts.
Arcade provides Zoom access through its MCP gateway and adds per-user OAuth, agent-optimized meeting workflows, approval policies, redaction, and tool visibility controls. The same Zoom connection can be reached from supported agents and frameworks without each one implementing its own authorization flow.
Arcade agents can identify the authenticated Zoom user, list upcoming meetings, find a meeting by phrase, date range, or meeting ID, and read its invitation. For past meetings, they can retrieve cloud recording links, AI Companion summaries, and transcripts.
Arcade requests the Zoom OAuth permissions needed for the meeting information and read-only history your workflow uses. The required permissions depend on which meeting, recording, summary, and transcript data the user authorizes; grant only the access your workflow needs.
Yes. Each user authorizes their own Zoom account through OAuth, and Zoom actions run with that user's authorization. An agent can access only the meetings and history available to that user.
Yes. Contextual Access policies can require human approval before a Zoom call proceeds, redact fields from the response, or hide a Zoom action from the agent. The shipped Zoom actions are read-only, so they do not change meetings or send communications.
Arcade proxies Zoom API calls and does not persist Zoom content as part of normal tool execution. OAuth credentials are brokered and stored encrypted at rest, and the model never receives the raw credentials.
Any framework or client that can connect to Arcade's MCP gateway or tool APIs works with Arcade Zoom, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.
Arcade refreshes Zoom access while the user's authorization remains valid. If the authorization is revoked, rotated, or can no longer be refreshed, Zoom calls stop until the user reconnects the account.
Zoom's API rate limits and account-level quotas still apply to calls made through Arcade. The specific limit depends on the Zoom endpoint and account, so high-volume meeting searches and recording or transcript retrieval should be paced accordingly.