Configure the Zoom MCP Server

Connect Zoom's official hosted MCP server to a Dtwo gateway via OAuth.

On this page
  1. Overview
  2. 1. Configure Zoom
  3. 2. Add the MCP server to your gateway config
  4. 3. Deploy and verify

Overview

Zoom operates official hosted MCP servers at mcp.zoom.us, covering meetings, recordings, and other Zoom data. Access is authorized through OAuth (with PKCE) via a Zoom OAuth app you register yourself.

1. Configure Zoom

  1. Go to the Zoom App Marketplace, sign in with developer permissions, and create a new OAuth app under Develop → Build App.
  2. On the app’s Basic Information page, under App Credentials, copy the OAuth Client ID and OAuth Client Secret, and set the redirect URL to your gateway’s OAuth callback URL — found in the Overview tab for your gateway in the Dtwo UI.
  3. Add the scopes your agents need — for example meeting:read:meeting, meeting:read:list_meetings, and cloud_recording:read:list_user_recordings.

2. Add the MCP server to your gateway config

Go to your gateway in the Dtwo UI and open Configuration → Advanced. In the mcp_servers section add the following entry:

  - name: zoom
    description: "Zoom's official hosted MCP server for meetings, recordings, and related Zoom data."
    url: https://mcp.zoom.us/mcp/zoom/streamable
    transport_type: streamablehttp
    authentication:
      type: oauth
      grant_type: authorization_code
      client_id: "<CLIENT_ID>"
      client_secret: "<CLIENT_SECRET>"
      token_url: "https://zoom.us/oauth/token"
      authorization_url: "https://zoom.us/oauth/authorize"
      redirect_uri: "<CALLBACK_URL>"
      pkce_enabled: true
      extra_authorize_params:
        resource: https://mcp.zoom.us/mcp/meeting/streamable
      scopes:
        - meeting:read:search
        - meeting:read:assets
        - meeting:read:meeting
        - meeting:read:list_meetings
        - zoomapp:inmeeting
        - cloud_recording:read:list_user_recordings
        - user:read:email
        - user:read:user

Replace the placeholder values:

  • <CLIENT_ID> and <CLIENT_SECRET> — come from the OAuth app you created in step 1.
  • <CALLBACK_URL> — the same redirect URL you set in step 1, found in the Overview tab for your gateway in the Dtwo UI.

3. Deploy and verify

Save the configuration and deploy the gateway.

Then, in your AI client, ask it to authorize Zoom via the gateway. This opens the Zoom login screen — sign in as the user whose permissions the agent should inherit, and approve the consent prompt. Once authorized, confirm the server’s tools appear and run a quick call to make sure the connection works.

If the tools don’t appear after you authorize, refresh the tool list in your AI client — some clients don’t pick it up automatically.

Having trouble?

Email us and we'll help you get set up.

Email support

↑↓ to navigate ↵ to open