Zoom
Connect Zoom to schedule and update meetings and webinars, manage registrants, read recordings, transcripts and AI summaries, and post to Team Chat.
You copy the Account ID, Client ID and Client secret of a Server-to-Server OAuth app that you create and activate in the Zoom App Marketplace. There is no redirect URL, no sign-in screen and nothing to renew.
- Setup time
- 5 min
- Auth
- API credentials
- API base URL
- https://api.zoom.us/v2
- Rate limits
- Per Zoom account, shared by every app installed on it, by request class. Pro: Light 30 a second, Medium 20, Heavy 10, Resource-intensive 10 a minute, with 30,000 heavy and resource-intensive requests a day. Business and up: 80, 60 and 40 a second and 20 a minute, with 60,000 a day. Free accounts: 4, 2 and 1 a second with daily caps. Each user can create or update 100 meetings or webinars a day (UTC).
Before you begin
- A Zoom account. Reports, cloud recordings, transcripts and AI Companion summaries need a paid Zoom plan, and Phone, Rooms and Contact Center need their own licenses.
- The account owner or an admin, or a role with View and Edit ticked for Server-to-Server OAuth app (Zoom web portal: User Management, Roles, Role Settings, Advanced features).
- Admin rights for the admin scopes, which reach every user's meetings, recordings and chats, plus reports and account settings. Without them only the app owner's own data is reachable.
Get your credentials
Open Created Apps
Sign in at marketplace.zoom.us with the Zoom account you want to connect, then click Developers in the lower left corner to open Created Apps. If the page does not open, ask an admin to give your role the Server-to-Server OAuth app permission.
Created Apps
Apps you have built for your Zoom account.
| App name | App type | Status |
|---|---|---|
| Recording syncCreated by Dana Reid | Server-to-Server OAuth app | Activated |
The plus sign in the blue circle sits next to Developer in the upper left corner of this page.
Build a Server-to-Server OAuth app
Next to Developer in the upper left corner, click the plus sign in the blue circle and choose Build an app. Select Server-to-Server OAuth app and click Create.
Created Apps
A General app's Client ID and secret cannot connect this way: choose Server-to-Server OAuth app.
Copy the three credentials
The new app opens on App Credentials. Copy the Account ID, Client ID and Client secret (click the eye icon to reveal it) into PopMCP's Zoom form. This Account ID is not the account number on your Zoom profile.
PopMCP
Server-to-Server OAuth app
- Account ID
- 5yiP****lf32q
- Client ID
- aBcD****TuV
- Client secret
- •••••••• (click to reveal)
Regenerating the secret here stops the old one at once; paste the new one into PopMCP.
Fill in the Information page
Open Information. Add a short description and your company name, then fill in the developer contact Name and Email address. Zoom will not activate the app without them.
PopMCP
Server-to-Server OAuth app
Add the scopes
Skip Feature (PopMCP needs no event subscription). Open Scopes, click Add Scopes, and tick what the AI should reach: Meeting, Webinar, Cloud Recording, User and Team Chat cover the everyday work. Scopes ending in :admin reach every user in the account. For a read-only connection add only the scopes whose description starts with View.
PopMCP
Server-to-Server OAuth app
The scopes you can pick follow your Zoom role: admin scopes only appear for someone with admin rights.
Activate the app
Open Activation and click Activate your app. If Zoom lists something missing, fix it first. A deactivated app stops every token at once.
PopMCP
Server-to-Server OAuth app
You cannot get an access token until the app is activated.
Connect in PopMCP
Paste the three values into PopMCP's Zoom form and click Connect. PopMCP gets an hour-long token from Zoom whenever it needs one, so nothing expires on you, and scopes you add later work on the next call with no reconnect.
Connect in PopMCP
Open your workspace, choose Zoom in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Account IDtext | From a Server-to-Server OAuth app in the Zoom App Marketplace: sign in at marketplace.zoom.us, click Developers (lower left), then the plus sign and Build an app, choose Server-to-Server OAuth app and Create. All three values are on its App Credentials page. |
| Client IDtext | On the same App Credentials page, under Client ID. |
| Client secretsecret | On the same page (click to reveal). Stored encrypted; PopMCP uses it only to get hour-long access tokens from Zoom.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Zoom immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP shows Zoom as Connected with the app owner's name and email (or Zoom account and the Account ID when the app has no user scope), and zoom_get_user returns that person.
Troubleshooting
"That looks like the account number from your Zoom profile"
Why: The digits-only account number from your Zoom profile went into the Account ID field.
Fix: Copy the Account ID from the app's **App Credentials** page instead: letters and numbers, about 22 characters.
"Zoom says this Server-to-Server OAuth app is not active"
Why: The app was never activated, or someone deactivated it.
Fix: Fill in the developer name and email on **Information**, then open **Activation** and click **Activate your app**.
"These credentials are not from a Server-to-Server OAuth app"
Why: The Client ID and secret belong to a General app, which needs a sign-in and cannot connect with an Account ID.
Fix: Build a **Server-to-Server OAuth app** and copy its three values.
"Zoom did not accept the Account ID for this app" or "Zoom did not accept these app credentials"
Why: A value was mistyped, came from a different app, or the secret was regenerated after you copied it.
Fix: Copy all three values again from the same app's **App Credentials** page, regenerating the secret if unsure.
"Zoom refused because the connection's token lacks a permission"
Why: The app does not hold the scope that call needs. The message names it.
Fix: Add the scope on the app's **Scopes** page and run the request again. The next call gets a fresh token that includes it, with no reconnect.
"Zoom refused this for the account behind the Server-to-Server OAuth app"
Why: The Zoom plan lacks the feature (many reports, recordings and webinars need a paid plan or add-on), the feature is switched off in account settings, or the app owner's role lacks the permission.
Fix: Check the plan and the setting in the Zoom web portal (for example cloud recording, audio transcript or AI Companion), or have an admin own the app.
"Zoom's rate limit for this Zoom account was reached"
Why: Zoom limits requests per account, shared by every app installed on it, and each host can create or update 100 meetings or webinars a day.
Fix: Per-second limits clear in a moment, so retry after a short pause. Daily limits reset at 00:00 UTC.
Reference
Trello
Connect Trello to create and move cards across boards and lists, and manage comments, members, labels, and checklists. MCP setup for Claude and ChatGPT.
Chargebee
Connect Chargebee to manage customers, subscriptions, invoices, credit notes, transactions, coupons, and quotes. MCP setup guide for Claude and ChatGPT.