Zoom MCP server
Inspect and maintain the connected user’s Zoom meetings with Arc0’s tools. Recording reads return metadata, while meeting creation schedules a one-time meeting without sending attendee invitations. Connect through Arc0 to use the actions your identity is allowed to call.
Working with Zoom
Before adjusting a meeting, zoom.get_account confirms the connected Zoom user and account IDs. zoom.list_meetings helps locate the meeting, and zoom.get_meeting reads its scheduling details. The outputs omit host credentials, join links, and passcodes, so they are suitable for a schedule review rather than distributing access to a meeting.
zoom.create_meeting schedules a one-time meeting as the connected user. It does not supply invitees or send attendee invitations. Use zoom.update_meeting when the requested change is a new topic; this action does not reschedule the meeting. For a recurring meeting, the rename applies to the series, and existing settings can notify alternative hosts or scheduling delegates.
zoom.list_recordings retrieves cloud recording metadata over a window of at most 28 days when the account has the required recording access. It does not fetch transcripts or playback links. zoom.delete_meeting cancels the entire recurring series rather than one occurrence. Read back the meeting after an uncertain update or cancellation before deciding what to do next.
Official MCP reference: Zoom documentation.
Agent workflows for Zoom.
Check the meeting schedule
Use zoom.list_meetings and zoom.get_meeting to inspect IDs, timing, and meeting state.
Schedule a one-time meeting
Use zoom.create_meeting for an approved time and topic; it does not return a join link or invite attendees.
Rename a meeting
Use zoom.update_meeting to change the topic, including the whole series for a recurring meeting.
Find recording metadata
Use zoom.list_recordings for a bounded date window without downloading recordings or transcripts.
7 Zoom actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
4Look things up, subject to your permissions.
- zoom.get_accountGet connected account
Use when you need to confirm the connected Zoom user and account IDs or license type. Returns structural account details only, without names, email addresses, or personal meeting links.
- zoom.list_meetingsList meetings
Use when finding the connected user’s meeting IDs. Filter by scheduled (default), live, upcoming/upcoming_meetings, or previous_meetings. Upcoming/previous filters cover at most six months. Returns up to 100 per page; pass next_page_token within 15 minutes to continue.
- zoom.get_meetingGet meeting
Use when inspecting a meeting by its numeric ID or reading back a write with an uncertain outcome before retrying. Returns scheduling details without host credentials, join links, or passcodes.
- zoom.list_recordingsList recording metadata
Use when finding cloud recording metadata for the connected user in a UTC date window of at most 28 days, optionally for one meeting. Requires Pro or higher with cloud recording enabled. No downloads, transcripts, participant data, or playback links.
write
2Create and change things. Allow, or ask the user first.
- zoom.create_meetingCreate meeting
Use when scheduling a one-time meeting as the connected user. No invitees or join link returned. Emails to alternative hosts/scheduling delegates and registrants, and auto-recording, are disabled. Not for sending invitations; list meetings before retrying an unknown outcome.
- zoom.update_meetingUpdate meeting topic
Use when renaming a meeting or whole recurring series. Sends only the topic. Zoom may email alternative hosts and scheduling delegates under existing settings. Not a silent-update guarantee or attendee invitation; read back before retrying an uncertain outcome.
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- zoom.delete_meetingDelete meeting
Use when explicitly asked to cancel a meeting. Deletes the entire recurring series. Suppresses cancellation emails to hosts, alternative hosts, and registrants. Not for cancelling one occurrence or notifying attendees; read back after an uncertain outcome.
Control access to Zoom.
Connect the intended Zoom account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
- zoom.create_meeting: require approval
- zoom.delete_meeting: deny
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How Zoom connects.
Connect Zoom using OAuth. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- OAuth
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Zoom with your AI client.
Sign in to Arc0 and connect Zoom in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
Zoom with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpFull MCP setup and troubleshootingZoom with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingZoom with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpFull MCP setup and troubleshootingZoom with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingZoom with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingZoom with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
Zoom and Arc0, answered.
Is there an official Zoom MCP server, and how does Arc0 differ?
Yes. Zoom documents a remote MCP server. Arc0’s current Zoom tools use a limited REST action set for scheduling details and recording metadata, with shared Arc0 policies and audit logging.
Which permissions does Arc0 need for Zoom?
User-managed OAuth requests user:read:user, meeting:read:list_meetings, meeting:read:meeting, meeting:write:meeting, meeting:update:meeting, meeting:delete:meeting and cloud_recording:read:list_user_recordings. Recording access also depends on the Zoom license and cloud recording settings.
Does this work with Claude, ChatGPT, Codex and Cursor?
Yes, through Arc0 MCP when your Claude, ChatGPT, Codex, or Cursor client supports remote MCP and your account permits it. Connect the app in Arc0 and configure your client using the Arc0 setup guide. App permissions still apply.
How are credentials stored, refreshed and revoked?
Credentials are encrypted in Arc0’s vault. Arc0 stores and refreshes OAuth credentials, keeping the rotated refresh token. Disconnect attempts Zoom token revocation. You can also remove the app in Zoom; provider-side removal and local disconnect should not be confused with a guarantee that every cleanup request succeeded.
What happens with rate limits or errors?
Zoom limits methods according to account and API rules. Arc0 reports throttling, scope failures, and missing resources. Meeting-list continuation tokens expire, so restart discovery if one is refused. Check meetings before repeating a creation with an unknown outcome.
What is the availability of these Zoom tools?
These tools are available. Connect the app in Arc0 and authorize your AI client. The action list describes the current implementation.
Plug Zoom into your agent.
Zoom MCP server: 7 actions including get connected account, list meetings, get meeting. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
Zoom and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Zoom.