zoom.com

This server does not support automatic client registration (no DCR or CIMD), so the MCP client cannot register itself. Create an OAuth app in the provider's developer settings, allow-list your MCP client's OAuth callback URL as a redirect URL, and give the client that app's client ID and secret. Then connect and approve access in the browser.

Create a Server-to-Server OAuth app in the Zoom App Marketplace following Create a Server-to-Server OAuth app. After creation, copy the app's account_id, client_id, and client_secret from the app credentials page, add the scopes you need, and activate the app. To mint an access token, call POST https://zoom.us/oauth/token with grant_type=account_credentials, your account_id, and Basic auth using client_id:client_secret as documented in OAuth 2.0.

Open Platform Studio or the legacy Build platform app settings. Under API keys, copy your API Key (and associated API Secret if you also generate JWTs). The Make API requests guide states Build Platform APIs can authenticate with either Authorization: Bearer TOKEN using your API key or JWT, or x-api-key: ZOOM_API_KEY using the API key directly.

Open Platform Studio or the legacy Build platform app settings. Under API keys, click View JWT Token to generate a token directly, or use your Build Platform API Key and API Secret to generate your own JWT as described in Build platform app settings and Make API requests. Use the JWT as Authorization: Bearer TOKEN.

Enable the Zoom Rooms Control System API per room in the Zoom web portal as described in Zoom Rooms Control System API. Set the room's SSH passcode in the Zoom Room configuration. Connect to the Zoom Room over SSH on port 2244 using username zoom; the password is the per-room SSH passcode from the portal. The docs note the default password may be blank when first enabled and should be changed immediately.