Skip to main content

Zoom MCP

The Zoom Model Context Protocol (MCP) server lets external AI agents work with Zoom meetings, cloud recordings, in-meeting assets, and related content through a remote streamable HTTP endpoint. Use it from Cequence AI Gateway so assistants can search meetings, list recordings, fetch summaries and transcripts where available, and work with Zoom-hosted files—subject to the signed-in user’s permissions and your Zoom app’s OAuth scopes.

Zoom publishes multiple product-specific MCP endpoints (for example meetings, chat, or whiteboard). This page describes the Zoom product MCP used in the AI Gateway catalogue. For the full list of servers, URLs, and scope guidance, see Zoom MCP servers in the Zoom Developer Docs.

Overview​

Zoom MCP is a remote, vendor-hosted MCP server. You connect to it from Cequence AI Gateway; you do not run the server yourself.

  • Server URL: https://mcp.zoom.us/mcp/zoom/streamable
  • Transport: HTTP (Streamable HTTP)
  • Hosted by: Zoom

The catalogue entry aligns with the third-party MCP manifest: streamable transport, 30-second request timeout, and OAuth toward Zoom’s authorization server. Capabilities depend on the tools enabled for your gateway and the scopes granted on your Zoom Marketplace app.

Supported authentication types​

TypeSupportedNotes
OAuth 2.1YesRecommended for Cequence AI Gateway. Zoom follows the MCP authorization model and uses OAuth for remote MCP. Manual client registration applies: create a General app on the Zoom App Marketplace and use that app’s Client ID and Client Secret. Zoom does not support Dynamic Client Registration (DCR) or Client ID Metadata Documents (CIMD) for these MCP servers—see Connect to Zoom MCP servers.
API keyNoRemote Zoom MCP expects OAuth access tokens (Bearer), not static API keys.

Token exchange uses Zoom’s standard OAuth token endpoint (POST to https://zoom.us/oauth/token). The MCP specification expects OAuth 2.1-style behavior: use PKCE (code_verifier / code_challenge) when performing the authorization code exchange. After you obtain an access token, MCP requests to Zoom must send it in an Authorization header whose value is the word Bearer followed by a space and the access token, as described in Zoom’s connection guide.

What can you do with this MCP server​

Exact tool names and schemas come from the catalogue tools.json and may evolve. Typical areas covered by the Zoom (meetings-oriented) MCP include:

  • Meeting discovery — Search the signed-in user’s meetings by keywords, time range, and optional inclusion of Zoom “My Notes,” with pagination for large result sets.
  • Cross-Zoom search — Broader search entry points over Zoom content where the server exposes them.
  • Meeting assets — Retrieve assets tied to a meeting instance (for example summaries or related resources when available and permitted).
  • Recordings — List cloud recordings and access recording-related resources where scopes and licensing allow.
  • Files and markdown — Create or read file-oriented content (such as markdown-backed resources) exposed by the MCP for workflows like notes or structured outputs.

All operations are constrained by OAuth scopes you add on the Marketplace app, account and user permissions, and product licensing (Zoom documents licenses per product area). Rate limits are aligned with Zoom Open APIs and your plan; some tools may have user-level or concurrency limits—see Zoom MCP servers overview.

Prerequisites​

Before adding Zoom MCP in Cequence AI Gateway, ensure you have:

  • Access to Cequence AI Gateway at aigateway.cequence.ai
  • A Zoom account with administrator or developer privileges sufficient to create and configure a Marketplace app
  • A Zoom App Marketplace app (Develop → Build app → General app) used as the integration point, with OAuth redirect URLs configured for the AI Gateway (or your IdP/client) exactly as required by your OAuth flow
  • OAuth scopes added under the app’s Scopes tab to match the tools you enable—Zoom documents required scopes per tool in the product MCP documentation (Zoom MCP)
  • Licenses for the Zoom products you intend to use (meetings, recordings, AI Companion features, and so on), where applicable

Because remote Zoom MCP uses manual OAuth client configuration, have your Marketplace app Client ID, Client Secret, authorization URL, token URL, and optional scope string ready when the gateway prompts for manual OAuth (the gateway may not rely on DCR for this server).

Example workflows​

Once connected, you can run workflows like these from your AI client (subject to tools and permissions).

  • “Find meetings from last week that mentioned the Q4 budget.”
  • “List my recent Zoom cloud recordings and show titles and durations.”
  • “For meeting UUID …, what meeting assets or summaries are available?”
  • “Search Zoom for content related to onboarding.”

Always ensure the assistant has the user’s timezone when tools require it (for example natural-language date ranges for meeting search).

Connecting MCP server from Cequence AI Gateway​

  1. Log in to Cequence AI Gateway.
  2. Choose your tenant.
  3. Go to App catalogue.
  4. Filter by Remote MCP server.
  5. Search for Zoom MCP and select it.
  6. Select Create MCP server.
  7. Configure OAuth using credentials from your Zoom Marketplace General app (manual registration: Client ID, Client Secret, and standard Zoom authorization/token endpoints). Enable PKCE as required by your client and Zoom’s OAuth 2.1 expectations.
  8. Add the gateway’s (or your OAuth client’s) redirect URI to the app under Basic Information → OAuth Information in the Marketplace, consistent with Connect to Zoom MCP servers.
  9. Complete the setup, select tools that match the scopes you granted, and deploy.

Use the generated MCP server URL in your client as described in the Client Configuration docs. For detailed UI steps and screenshots, see Create a third-party MCP Server.

Additional information specific to Zoom MCP​

  • Streamable HTTP: Use the streamable endpoint (…/streamable) when configuring transport as Streamable HTTP in the gateway; Zoom also documents SSE endpoints for clients that use SSE instead—see Zoom MCP servers overview.
  • No DCR: Plan on registering a Marketplace app and supplying client credentials to the gateway; do not assume Dynamic Client Registration.
  • PKCE: Include PKCE parameters on the token exchange to stay aligned with MCP OAuth 2.1 expectations and Zoom’s documentation.
  • Scopes and re-authorization: If a tool fails with insufficient scope, add the scope on the Marketplace app and re-run the OAuth consent / token flow.
  • Timeout: The catalogue manifest uses a 30-second timeout for remote requests.
  • Official documentation: