Skip to content
Last updated

Zoom integration

Zoom can be connected to Agen.co two ways, matching the Official / In-house filter in the connector picker:

  • Official — Agen.co connects through Zoom's own hosted MCP server (https://mcp.zoom.us/mcp/zoom/streamable), so your AI agents use the same meeting search, recording, and Zoom Docs tools Zoom exposes to MCP clients like Claude and ChatGPT.
  • In-house — Agen.co wraps the Zoom REST API directly through its own integration layer, using an OAuth app you register in the Zoom App Marketplace with granular scope options across meetings, webinars, recordings, and user management.

Pick Official if the built-in MCP tools cover what your agents need. Fall back to In-house if you need broader access — for example, creating or updating meetings and webinars, or managing users.


Connect via the official MCP server

Prerequisites

Create a Zoom OAuth app

  1. Go to marketplace.zoom.us and sign in.
  2. On the page that opens, click the blue + button in the top-left corner and select Build app. Select General App and click Create.
  3. Switch back to Agen.co and start adding the connector as usual — in the Agen.co portal, go to Connectors → Marketplace, click Add connector, filter Type to Official, and select Zoom.
  4. Get back to Zoom. Scroll down to App Credentials to find your Client ID and Client Secret — these are only shown once, so copy both values immediately.
  5. Scroll to OAuth Information. In the OAuth Redirect URL field, and under OAuth Allow Lists, add both URLs Agen.co generates when you open the Add Zoom panel with Official selected:
    • Callback URL — completes the initial OAuth handshake between Agen.co and your OAuth app.
    • Gateway callback URL — used by the Agen.co MCP gateway for per-user authorization at runtime.
  6. In the left sidebar, click Scopes, then + Add Scopes, and add the scopes for the Zoom product(s) you plan to use. For the default meeting product, Zoom's MCP setup guidance points to:
ScopeDescription
ai_companion:read:searchSemantic search over meeting content
meeting:read:searchSearch a user's meetings
meeting:read:assetsRead meeting-linked documents and resources
cloud_recording:read:list_user_recordingsList cloud recordings for a user
cloud_recording:read:contentAccess recording content and transcripts
docs:read:exportExport Zoom Docs content
docs:write:importCreate Zoom Docs from imported content
  1. Click Done to save the selected scopes.

Connect Zoom in Agen.co

Return to the Agen.co portal — the Add Zoom panel should already be open from the step above. Check that the following fields are filled in:

FieldRequiredDescription
Instance SlugNoDistinguishes multiple instances of this MCP connector — it prefixes each imported tool as slug__tool. Use lowercase kebab-case; leave empty for a single instance. This value is immutable after creation.
Zoom productYesSelects which Zoom MCP surface to connect: meeting (Meetings, the default), chat (Team Chat), docs (Docs), whiteboard (Whiteboard), tasks (Tasks), or revenue_accelerator (Revenue Accelerator). Each connects to a different set of tools.
Client IDYesThe Client ID from the OAuth app you created above.
Client SecretYesThe Client Secret from the OAuth app you created above.

Each connector instance connects to exactly one Zoom product. To expose tools from more than one (for example, both Meetings and Docs), add the Zoom connector again with a different Instance Slug and select the other product each time.

Click Connect. You're redirected to Zoom to sign in and approve access.

For the default meeting product, Zoom appears under My connectors with these tools:

ToolWhat it does
search_meetingsSearches a user's meetings (read-only)
get_recording_resourceRetrieves detailed content and metadata for a specific recording, including transcript text
get_meeting_assetsRetrieves all available assets for a specific meeting (read-only)
recordings_listLists all cloud recordings for a user

The number of tools a connected instance exposes depends only on which tools Zoom's MCP server implements for that product — it isn't affected by how many OAuth scopes the app was granted. The tools listed above were confirmed live for the meeting product; the tool sets for chat, docs, whiteboard, tasks, and revenue_accelerator haven't been verified yet.

Enabling the Zoom connector isn't enough on its own. Tool calls remain denied until you create a policy that grants access to the specific tools you want to expose.

Connect via the Zoom API

Integrating Zoom with Frontegg allows your application to access and manage Zoom meetings, webinars, and recordings on behalf of your users — all through Frontegg's integration layer using Zoom's OAuth 2.0.

Prerequisites

Create a Zoom OAuth app

Step 1: Open the Zoom App Marketplace developer portal

Go to marketplace.zoom.us, sign in, then click Develop in the top navigation bar and select Build app from the dropdown.

Zoom App Marketplace with Develop dropdown open showing Build app option

Step 2: Select app type and create

On the What kind of app are you creating dialog, select General App and click Create.

App type selection dialog with General App selected and Create button highlighted

Step 3: Copy your Client ID and Client Secret

After the app is created, you land on the Basic Information page. Scroll to the App Credentials section to find your Client ID and Client Secret. Copy both values and store them securely.

Save your Client Secret now

The Client Secret is shown only on this page. Store it securely before navigating away.

App Credentials section showing Client ID and hidden Client Secret

Step 4: Configure OAuth redirect URIs

Scroll down to the OAuth Information section on the same page.

  1. In the OAuth Redirect URL field, enter:
    https://YOUR_MCP_GATEWAY_URL/integration-callback
  2. Under OAuth Allow Lists, add the same URI:
    • https://YOUR_MCP_GATEWAY_URL/integration-callback

OAuth Redirect URL and OAuth Allow Lists fields filled with Frontegg callback URIs

Step 5: Add scopes

In the left sidebar, click Scopes, then click + Add Scopes. Use the search field or product tabs to find and select the required scopes:

ScopeDescription
user:read:userView a user's profile
user:update:userUpdate a user's profile
user:delete:userDelete or disassociate a user
meeting:read:meetingView a meeting
meeting:read:list_meetingsView a user's meetings
meeting:write:meetingCreate a meeting for a user
meeting:update:meetingUpdate a meeting
meeting:delete:meetingDelete a meeting
meeting:read:past_meetingView a past meeting instance
meeting:read:list_past_instancesList ended instances of a recurring meeting
meeting:read:list_past_participantsList participants of a past meeting
meeting:read:summaryView an AI Companion meeting summary
meeting:read:list_registrantsList meeting registrants
meeting:write:registrantAdd a meeting registrant
webinar:read:webinarView a webinar
webinar:read:list_webinarsView a user's webinars
webinar:write:webinarCreate a webinar for a user
webinar:update:webinarUpdate a webinar
webinar:delete:webinarDelete a webinar
webinar:read:list_registrantsList webinar registrants
webinar:write:registrantAdd a webinar registrant
cloud_recording:read:list_user_recordingsList all cloud recordings for a user
cloud_recording:read:list_recording_filesReturn all recordings for a meeting
cloud_recording:read:meeting_transcriptView an AI Companion meeting transcript
cloud_recording:delete:meeting_recordingDelete a meeting's cloud recordings
cloud_recording:update:recover_meeting_recordingsRecover a meeting's recordings from trash

Click Done to save the selected scopes.

Add Scopes dialog with multiple scopes selected across Meeting and Recording categories

Scopes page showing all selected scopes in a table

Configure the Frontegg portal

Once you have your Client ID and Client Secret, enter them in the Frontegg portal:

  1. Open the Frontegg portal and navigate to [ENVIRONMENT] → Integrations → Zoom.
  2. Enter the Client ID and Client Secret in the corresponding fields.
  3. Select the required scopes.
  4. Click Save.

Keep your credentials secure

Never share or commit your Client Secret to version control.

Additional resources