Secure Zoom access for AI agents

Through Zoom, agents can search meetings, pull recordings and transcripts, and read or create Zoom Docs — every call runs through your policies and is logged for audit.

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

Setup

1. Navigate to Resources and click Add Resource
2. Select Zoom from the catalog
3. Provide your Zoom OAuth app credentials (see Bring your own app)
4. Click Add

Each user connects their own Zoom account via OAuth when they first use a Zoom tool; there is no shared service account. Navigate to Connections to manage linked accounts.

Credential modes

Zoom supports one mode:

• Bring your own app: a Zoom OAuth app owned by your organization. Zoom does not support dynamic client registration, so an app registered in your Zoom account is required.

See Credential modes for the full comparison.

Bring your own app

A Zoom account admin registers a user-authorized OAuth app in the Zoom App Marketplace, then returns to SecureAuth with the Client ID and Client Secret.

In the Agent Authority console, go to Resources → Add Resource → Zoom and copy the redirect URI shown on the form. Zoom is bring-your-own-app only, so the credentials form opens as soon as you select Zoom — there's no mode to pick.

In the Zoom App Marketplace, go to Develop → Build App and create a General App (user-authorized OAuth app):

• Under OAuth, set the Redirect URL for OAuth to the redirect URI you copied, and add the same URL to the OAuth Allow List
• Under Scopes, add every scope listed under Required scopes
• Copy the Client ID and Client Secret from Basic Information

Paste both back into the Zoom resource page in the Agent Authority console, then click Add.

An unpublished app works for your own account. If your Zoom account requires marketplace apps to be pre-approved, a Zoom account owner or admin must approve the app once at marketplace.zoom.us → Manage → Permissions before other users can connect.

Available tools

Required scopes

• meeting:read:search: search the user's meetings
• meeting:read:assets: read meeting summaries, notes, and assets
• cloud_recording:read:list_user_recordings: list cloud recordings
• cloud_recording:read:content: read recording transcripts and summaries
• ai_companion:read:search: search AI Companion content
• docs:read:export: read Zoom Docs content
• docs:write:import: create Zoom Docs

Policy examples

Rules are evaluated first-match-wins from the top of the list, and every org starts with a seeded Allow all rule sitting at the bottom — so a recipe made only of allow rules restricts nothing. Deny-based examples like these work by adding denies above it.

• Read-only access: deny create_new_file_with_markdown — it's the only tool that writes
• Meetings without transcripts or playback: deny recordings_list and get_recording_resource, which are what surface transcripts, topic summaries, and playback URLs. Note that get_meeting_assets still returns the meeting's recording among its assets, so this narrows recording access rather than walling it off — deny get_meeting_assets too if agents shouldn't reach recordings at all.
• Docs workflows only: allow search_zoom, get_file_content, and create_new_file_with_markdown, and deny the meeting and recording tools (search_meetings, get_meeting_assets, recordings_list, get_recording_resource) — the allow rules alone wouldn't exclude them.

Next steps

• Create a policy — start from the read-only pattern in Policy examples above.
• Credential modes — see why Zoom requires bringing your own app.