Zoom MCP Server

Zoom mcp server to create, update, read or delete zoom meetings using natural language commands through Cursor and Claude

Local serverstdio

What is the Zoom MCP server?

Most developer tooling work still happens through a UI a human drives. Zoom MCP server moves it into the conversation instead. Zoom mcp server to create, update, read or delete zoom meetings using natural language commands through Cursor and Claude.

The short version

A Model Context Protocol (MCP) server for managing Zoom meetings via Claude or Cursor.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

The tools it exposes

The server publishes 4 tools. What each one is for:

  • get_meetings — Retrieve all active Zoom meetings
  • create_meeting — Create a new Zoom meeting
  • update_meeting — Update an existing meeting
  • delete_meeting — Delete a Zoom meeting

What it needs from you

Configuration is passed through the environment: ZOOM_ACCOUNT_ID, ZOOM_CLIENT_ID, ZOOM_CLIENT_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Zoom's toolset — get_meetings, create_meeting, update_meeting and 1 more — is a fair guide to whether it matches your workflow. It is maintained by Prathamesh0901; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
get_meetingsRetrieve all active Zoom meetings
create_meetingCreate a new Zoom meeting
update_meetingUpdate an existing meeting
delete_meetingDelete a Zoom meeting

How to install the Zoom MCP server

{
  "mcpServers": {
    "zoom": {
      "command": "npx",
      "args": [
        "-y", "@prathamesh0901/zoom-mcp-server"
      ],
      "env": {
        "ZOOM_ACCOUNT_ID": "Your Zoom Account ID",
        "ZOOM_CLIENT_ID": "Your Zoom Client ID",
        "ZOOM_CLIENT_SECRET": "Your Zoom Client Secret"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
ZOOM_ACCOUNT_IDConfiguration value read at startup.Optional
ZOOM_CLIENT_IDConfiguration value read at startup.Optional
ZOOM_CLIENT_SECRETCredential the server authenticates with.Yes

Example prompts to try

  • Use Zoom to get meetings.
  • Use Zoom to create meeting.
  • Use Zoom to update meeting.

Frequently asked questions

You need a Zoom Account ID, Client ID, and Client Secret from a Server-to-Server OAuth App created on the Zoom Marketplace with all Meeting permissions enabled.