To sync registrations and attendance with a Conversion webinar, use the separate Zoom webinar integration. 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.
Step 1: Create a Server-to-Server OAuth app
- Sign in to the Zoom App Marketplace.
- Select Developers in the lower left corner to open the Created Apps page.
- Select the plus sign next to Developer.
- Select Build an app.
- Select Server-to-Server OAuth app.
- Click Create.
Step 2: Add scopes and activate the app
- 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.
- In Scopes, choose Add Scopes.
- Add the scope for each action you want the tools to perform. Use the table below.
- In Activation, activate the app. Zoom issues no access until the app is activated.
Every other tool needs its own scope. Each tool’s description names the Zoom endpoint it calls, and Zoom’s API reference lists the scope for that endpoint.
Step 3: Copy the app credentials
- Open App credentials in the app.
- Copy the account ID.
- Copy the client ID.
- Copy the client secret.
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.
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.
Replace
YOUR-ACCOUNT-ID with the account ID from Step 3.
Step 6: Authorize the connection
- Click Add server.
- Click Connect on the Zoom server.
- Confirm the server shows Authorized.
Test the connection
- Open the server’s Tools tab and confirm Zoom tools are listed.
- 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.
- Approve the read-only tool call if prompted.
- Compare the returned topics with the same host’s webinars in Zoom.
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 asuserId. The app is not a host itself. - A list tool returns one page. Pass the
next_page_tokenor 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
/mcpsuffix 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.