Zoom API MCP Server

# Zoom API MCP Server A comprehensive Model Context Protocol (MCP) server for interacting with the Zoom API. ## Features - Complete coverage of Zoom

Local serverstdio

What is the Zoom API MCP server?

Zoom API MCP Server A comprehensive Model Context Protocol (MCP) server for interacting with the Zoom API. ## Features - Complete coverage of Zoom API endpoints - OAuth 2.0 authentication - Structured tools with proper validation - API. Exposed over MCP by the zoom api mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Its toolset

Everything the assistant can do here goes through one of these:

  • Meetings — Create, read, update, and delete meetings
  • Users — Manage users in your Zoom account
  • Webinars — Create and manage webinars
  • Account — Manage account settings and profile
  • Chat — Manage Zoom Chat channels and messages
  • Phone — Manage Zoom Phone users and numbers
  • Contacts — Manage contacts
  • Recordings — Access and manage cloud recordings
  • Reports — Generate various reports
  • Webhooks — Set up event notifications

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

You will need 3 environment variables: ZOOM_CLIENT_ID, ZOOM_CLIENT_SECRET, ZOOM_ACCOUNT_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Zoom API's toolset — Meetings, Users, Webinars and 7 more — is a fair guide to whether it matches your workflow. It is maintained by mattcoatsworth; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • 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.
  • With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Zoom API.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the zoom api mcp server does with a few real requests.

Available tools

ToolWhat it does
MeetingsCreate, read, update, and delete meetings
UsersManage users in your Zoom account
WebinarsCreate and manage webinars
AccountManage account settings and profile
ChatManage Zoom Chat channels and messages
PhoneManage Zoom Phone users and numbers
ContactsManage contacts
RecordingsAccess and manage cloud recordings
ReportsGenerate various reports
WebhooksSet up event notifications

Configuration

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

Example prompts to try

  • Use Zoom API to Meetings.
  • Use Zoom API to Users.
  • Use Zoom API to Webinars.

Frequently asked questions

Node.js 16+ and Zoom API credentials (Client ID, Client Secret, Account ID) from a Server-to-Server OAuth app.