> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conversion.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Zoom to Conversion

> Create a Server-to-Server OAuth app in Zoom, then add the Zoom MCP server so Conversion AI chats and agents can work with your webinars and Zoom Events.

Connect Zoom through Conversion's hosted MCP wrapper to give AI chats and [agents](https://docs.conversion.ai/product-docs/conversion-ai/agents/overview.md) tools for webinars, meetings, Zoom Events, and the rest of Zoom's REST API.

> [!NOTE]
>
> To sync registrations and attendance with a Conversion webinar, use the separate [Zoom webinar integration](https://docs.conversion.ai/product-docs/campaigns/webinars/platform-sync/zoom/connecting-zoom.md). The MCP server is its own connection. It does not use that integration's Zoom sign-in, and connecting it does not change that integration.

## Set up Zoom

### Before you begin

* A Conversion **Administrator** account to add the server.
* A Zoom user whose role can view and edit Server-to-Server OAuth apps. A Zoom admin turns this on for the role.
* Role permission for each scope you plan to add. Zoom requires admin-level role permissions to add admin-level scopes.
* The Zoom licenses for the products you plan to use. The server cannot do anything your Zoom plan does not include. Hosting a webinar still needs a Webinar license.

The connection acts as the app, not as a person. The app's scopes decide what every workspace member can do through it.

### Step 1: Create a Server-to-Server OAuth app

1. Sign in to the [Zoom App Marketplace](https://marketplace.zoom.us/).
2. Select **Developers** in the lower left corner to open the **Created Apps** page.
3. Select the plus sign next to **Developer**.
4. Select **Build an app**.
5. Select **Server-to-Server OAuth app**.
6. Click **Create**.

A General app's client ID and secret do not work with this server. See [Zoom's guide](https://developers.zoom.us/docs/internal-apps/create/) for details.

### Step 2: Add scopes and activate the app

1. In **Information**, add the app's description, company name, and a developer name and email. Zoom requires the name and email to activate the app.
2. In **Scopes**, choose **Add Scopes**.
3. Add the scope for each action you want the tools to perform. Use the table below.
4. In **Activation**, activate the app. Zoom issues no access until the app is activated.

| To let the tools | Add this scope | Tool |
| - | - | - |
| List a host's webinars | `webinar:read:list_webinars:admin` | `zoom_meetings_webinars` |
| Read a webinar | `webinar:read:webinar:admin` | `zoom_meetings_webinar` |
| Create a webinar | `webinar:write:webinar:admin` | `zoom_meetings_webinar_create` |
| Update a webinar | `webinar:update:webinar:admin` | `zoom_meetings_webinar_update` |
| List a webinar's registrants | `webinar:read:list_registrants:admin` | `zoom_meetings_webinar_registrants` |
| Add a registrant | `webinar:write:registrant:admin` | `zoom_meetings_webinar_registrant_create` |
| List Zoom Events hubs | `zoom_events:read:list_hubs:admin` | `zoom_events_get_hub_list` |
| List Zoom Events events | `zoom_events:read:list_events:admin` | `zoom_events_get_events` |
| Read an event | `zoom_events:read:event:admin` | `zoom_events_get_event_info` |
| Create an event, or publish, duplicate, or cancel one | `zoom_events:write:event:admin` | `zoom_events_create_event`, `zoom_events_event_actions` |
| Update an event | `zoom_events:update:event:admin` | `zoom_events_update_event` |
| List an event's sessions | `zoom_events:read:list_sessions:admin` | `zoom_events_get_event_session_list` |
| List an event's tickets | `zoom_events:read:list_tickets:admin` | `zoom_events_get_tickets` |
| Create tickets (registrations) | `zoom_events:write:ticket:admin` | `zoom_events_create_tickets` |

Every other tool needs its own scope. Each tool's description names the Zoom endpoint it calls, and [Zoom's API reference](https://developers.zoom.us/docs/api/) lists the scope for that endpoint.

### Step 3: Copy the app credentials

1. Open **App credentials** in the app.
2. Copy the account ID.
3. Copy the client ID.
4. Copy the client secret.

Store all three securely. If your Conversion team is setting up the server for you, share them through a secure channel.

### Step 4: Choose a tool group

The full server exposes more than 2,000 tools, which is more than a chat or agent can use well. Add a group name after the account ID to expose one Zoom product's tools.

| Server URL | Tools |
| - | - |
| `https://map.mcp.conversion.ai/zoom/YOUR-ACCOUNT-ID.meetings/mcp` | Meetings and webinars (186 tools) |
| `https://map.mcp.conversion.ai/zoom/YOUR-ACCOUNT-ID.events/mcp` | Zoom Events (91 tools) |
| `https://map.mcp.conversion.ai/zoom/YOUR-ACCOUNT-ID/mcp` | Everything |

To use two groups, add two servers. A group only filters which tools are listed. What the connection can do is set by the app's scopes.

Every URL also exposes `zoom_rest_request`, which calls any Zoom REST endpoint the app's scopes allow.

### Step 5: Add the server in Conversion

In Conversion, go to **Settings → AI → Connections**. Under **MCP servers**, click **Add MCP server** (or **Add server** below an existing list). Fill in the fields below.

| Field | Value |
| - | - |
| **Name** | `Zoom` |
| **Server URL** | The URL you chose in Step 4 |
| **Transport** | **Streamable HTTP** |
| **Authentication** | **OAuth (per user)** |
| **OAuth client ID** | Your app's client ID |
| **OAuth client secret** | Your app's client secret |

Replace `YOUR-ACCOUNT-ID` with the account ID from Step 3.

### Step 6: Authorize the connection

1. Click **Add server**.
2. Click **Connect** on the Zoom server.
3. Confirm the server shows **Authorized**.

No Zoom sign-in page appears. The wrapper checks the saved credentials with Zoom.

Each member must connect individually. It does not matter who clicks **Connect**: every connection acts as the app, in the Zoom account from the server URL, with the app's scopes.

## Test the connection

1. Open the server's **Tools** tab and confirm Zoom tools are listed.
2. Start a Conversion AI chat and ask it to list up to three upcoming webinars for one of your hosts, without creating or changing anything. Give it the host's Zoom email address.
3. Approve the read-only tool call if prompted.
4. Compare the returned topics with the same host's webinars in Zoom.

Review [tool approval settings](https://docs.conversion.ai/product-docs/workspace-settings/ai/connections.md#server-page-and-tools) before using tools that change data.

## Using the tools

* Tools that act for a host, such as `zoom_meetings_webinar_create`, take the host's Zoom user ID or email address as `userId`. The app is not a host itself.
* A list tool returns one page. Pass the `next_page_token` or page number from the result to get the next page.
* File uploads and responses are limited to 10 MiB per call.
* The wrapper does not retry a failed call. A create may have succeeded even when its response was lost, so check Zoom before creating again.

## Troubleshooting

* **Not Found** or **Unreachable**: check the account ID, the group name, and the `/mcp` suffix in the server URL. An unknown group name is rejected.
* **Connect** fails: the client ID and client secret must come from a Server-to-Server OAuth app in the Zoom account whose account ID is in the server URL, and the app must be activated.
* A tool fails for a missing scope: add the scope to the app in Zoom, then run the tool again.
* A tool fails after connecting: check the app's scopes, your Zoom licenses, and the error returned by Zoom.
* The tools act on the wrong Zoom account: the server URL or the credentials belong to another account. Correct them with **Edit** on the server page. Changing **OAuth client ID** or **OAuth client secret** removes every member's connection, so each member clicks **Connect** again.

After correcting the settings, reconnect if needed and use **Refresh tools** on the server page. A tools list confirms discovery; a successful read-only call confirms access to Zoom.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.