Merge Unified's Zoom integration Merge Agent Handler's Zoom MCP server

Connect your AI Agents to Zoom in minutes

Merge lets you securely connect your agents to Zoom and thousands of tools instantly

Start building for free

Read docs

Zoom

Learn more about Merge Agent Handler

Available tools

list_meetings

List Zoom meetings for a user

create_meeting

Create a new Zoom meeting. All parameters are optional. Common fields: topic, type (1=instant, 2=scheduled), start_time, duration, timezone, password, agenda, settings

get_meeting

Get Zoom meeting details

update_meeting

Update a Zoom meeting

delete_meeting

Delete a Zoom meeting

get_meeting_invitation

Get meeting invitation

update_meeting_status

Update meeting status

get_meeting_participants

Get participants from completed/past meetings (not live meetings)

list_recordings

List Zoom recordings

get_meeting_recordings

Get meeting recordings

get_transcript

Download the audio transcript text for a meeting's cloud recording. Returns raw WebVTT content plus parsed speaker segments. Requires cloud recording with audio transcription enabled on the account. Use getmeetingrecordings first to confirm a TRANSCRIPT file exists.

delete_meeting_recordings

Delete meeting recordings

recover_meeting_recordings

Recover meeting recordings

delete_recording_file

Delete recording file

get_recording_download_token

Get recording download token

get_user

Get Zoom user details

update_user

Update a Zoom user

get_user_settings

Get user settings. For userid, use the email address or userid of the user.

update_user_settings

Update user settings

get_user_permissions

Get user permissions

validate_credential

Validate Zoom credentials. Verifies credentials during setup.

View all tools by creating a free account See more tools

How to set up Merge Agent Handler

In an mcp.json file, add the configuration below, and restart Cursor.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Copy Code

Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.

Make sure Claude is using the Node v20+.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "command": "npx",
5      "args": [
6        "-y",
7        "mcp-remote@latest",
8        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9        "--header",
10        "Authorization: Bearer ${AUTH_TOKEN}"
11      ],
12      "env": {
13        "AUTH_TOKEN": "yMt*****"
14      }
15    }
16  }
17}

Copy Code

Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.

Learn more in the official documentation ↗

1{
2    "mcpServers": {
3      "agent-handler": {
4        "command": "npx",
5        "args": [
6          "-y",
7          "mcp-remote@latest",
8          "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9          "--header",
10          "Authorization: Bearer ${AUTH_TOKEN}"
11        ],
12        "env": {
13          "AUTH_TOKEN": "<ah-production-access-key>"
14        }
15      }
16    }
17  }

Copy Code

In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".

You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.

Learn more in the official documentation ↗

1{
2  "inputs": [
3    {
4      "type": "promptString",
5      "id": "agent-handler-auth",
6      "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7      "password": true
8    }
9  ],
10  "servers": {
11    "agent-handler": {
12      "type": "stdio",
13      "command": "npx",
14      "args": [
15        "-y",
16        "mcp-remote@latest",
17        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18        "--header",
19        "Authorization: Bearer ${input:agent-handler-auth}"
20      ]
21    }
22  }
23}

Copy Code

FAQs on using Merge's Zoom MCP server

How can I use the Zoom MCP server?

Here are are just a few ways your agents can use a Zoom MCP server:

• Meeting coordination: Your agent can create Zoom meetings automatically when a trigger happens (e.g., a deal reaches “Contract Sent”), set the topic/agenda, and return the join link for invites

• Rescheduling and updates: Your agent can look up a meeting by ID, update the time/settings when attendees change availability, and share the updated details back to your calendar/workflow tool

• Meeting cleanup: Your agent can detect duplicate/test meetings and delete them to keep your Zoom account tidy

• Post-meeting summaries from transcripts: If you use a transcript-focused Zoom MCP server, your agent can download the transcript for a specific recorded meeting and generate a summary and key decisions

• Searchable “meeting memory”: Your agent can search across downloaded transcripts for terms like “pricing exception” or “launch date,” then surface the exact meeting(s) where it was discussed

What are popular tools for Zoom’s MCP server?

Here are some popular tools across data types:

Meetings

<code class="blog_inline-code">list_meetings</code>
<code class="blog_inline-code">create_meeting</code>
<code class="blog_inline-code">get_meeting</code>
<code class="blog_inline-code">update_meeting</code>

Recordings

<code class="blog_inline-code">get_meeting_recordings</code>
<code class="blog_inline-code">recover_meeting_recordings</code>
<code class="blog_inline-code">delete_meeting_recordings</code>
<code class="blog_inline-code">list_recordings</code>

Users

<code class="blog_inline-code">get_user</code>
<code class="blog_inline-code">update_user</code>
<code class="blog_inline-code">get_user_settings</code>
<code class="blog_inline-code">get_user_permissions</code>

What makes Merge Agent Handler’s Zoom MCP server better than alternative Zoom MCP servers?

Here are just a few reasons:

Enterprise-grade security and DLP: All tool inputs and outputs are scanned by a security gateway with configurable data-loss-prevention rules, allowing you to block, redact, or mask sensitive data before it reaches Zoom

Authentication and credential management: Merge handles OAuth and credential storage, including guided user authentication flows and support for both shared and per-user authentication

Tool Pack–based access control: Zoom tools can be bundled into Tool Packs and selectively exposed to agents based on use case, limiting unnecessary access

Real-time observability and auditability: Every tool call is logged, with fully searchable logs that support auditing, debugging, and optimization of agent behavior. This completes a full audit trail for Zoom interactions

Can I set custom security rules for Zoom tool calls in Merge Agent Handler?

Yes, you can set a wide range of custom security rules for Zoom tool calls in Merge Agent Handler.

Here are a few examples:

Credit card numbers: Block any Zoom tool calls that attempt to include credit card numbers in meeting titles, descriptions, or chat messages before they're created or sent

Social security numbers: Prevent your agents from sharing SSNs in Zoom meeting invitations, calendar descriptions, or chat messages by blocking tool calls that contain this sensitive data

Email addresses: Redact email addresses from Zoom meeting participant lists or chat message responses, so agents only see masked versions (e.g., j*@merge.dev) when retrieving meeting details

Phone numbers: Automatically redact phone numbers from Zoom meeting details, participant information, or chat messages when agents retrieve them

External meeting access: Block tool calls that attempt to create Zoom meetings with participant email addresses outside your organization's domain

Recording restrictions: Log any tool calls that start or access Zoom meeting recordings to give your team visibility into when agents interact with recorded content

How can I start using Merge Agent Handler’s Zoom MCP server?

You can follow these steps:

1. Sign up for Agent Handler. Register for a free account here.‍

2. Set up a Tool Pack. Navigate to "Tool Packs" in the left sidebar and select "Create New Tool Pack." Give it a relevant name (e.g., "Zoom Collaboration Tools").

3. Select the Zoom connector. Browse the available connectors and add Zoom to your Tool Pack.

4. Choose your authentication method. Decide whether to use individual authentication (each user connects their own Zoom account) or shared authentication (one set of organization-level credentials for all users).

5. Choose which tools to enable. Pick specific Zoom tools for your agent to access, or allow access to all available tools.

6. Create a Registered User. Go to "Registered Users" in the sidebar and add a new registered user. This identity represents who will execute actions via your agent.

7. Finalize your Tool Pack configuration. Review and save all your Tool Pack settings.

8. Link the Tool Pack to your agent. Copy the MCP entry URL from your Tool Pack settings and connect it to your agent. Your agent can now use the Zoom tools you've configured!