MCP MCP Server

Zoom MCP Pack

Local serverstdio

What is the MCP MCP server?

MCP MCP server exists for a simple reason — assistants are far more useful when they can act on MCP directly instead of describing what you should do. Zoom MCP Pack.

What you get

Part of Pipeworx — an MCP gateway connecting AI agents to 1394+ live data sources.

What the assistant can call

Once MCP is connected, these are the calls the assistant has available:

  • zoom_list_meetings — List Zoom meetings for the signed-in user (upcoming, scheduled, or currently live video calls). Returns compact meeting summaries (id, topic, start
  • zoom_get_meeting — Get the full details of a single Zoom meeting by its meeting ID, including topic, start time, duration, timezone, agenda, join URL, status, and key
  • zoom_list_recordings — List the signed-in user's Zoom cloud recordings of past meetings and video calls. Returns each recording's id, topic, start time, duration, total
  • zoom_get_user — Get the signed-in Zoom user's profile: id, email, first/last name, account type, account id, timezone, and personal meeting id (PMI). Use to identify

Setting it up

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.

Choosing this one

Plenty of team communication 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. MCP's toolset — zoom_list_meetings, zoom_get_meeting, zoom_list_recordings and 1 more — is a fair guide to whether it matches your workflow. It is maintained by mojibake-ai; 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.

Before you rely on it

  • 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.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
zoom_list_meetingsList Zoom meetings for the signed-in user (upcoming, scheduled, or currently live video calls). Returns compact meeting summaries (id, topic, start time, duration, join URL, timezone). Use to browse a user's Zoom meeting
zoom_get_meetingGet the full details of a single Zoom meeting by its meeting ID, including topic, start time, duration, timezone, agenda, join URL, status, and key video/security settings (host video, participant video, waiting room). U
zoom_list_recordingsList the signed-in user's Zoom cloud recordings of past meetings and video calls. Returns each recording's id, topic, start time, duration, total size, recording count, and downloadable/playable files (video, audio, tran
zoom_get_userGet the signed-in Zoom user's profile: id, email, first/last name, account type, account id, timezone, and personal meeting id (PMI). Use to identify whose Zoom account is connected.

How to install the MCP MCP server

{
  "mcpServers": {
    "zoom": {
      "url": "https://gateway.pipeworx.io/zoom/mcp"
    }
  }
}

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

Example prompts to try

  • Use MCP to zoom list meetings.
  • Use MCP to zoom get meeting.
  • Use MCP to zoom list recordings.

Frequently asked questions

It connects MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (zoom_list_meetings, zoom_get_meeting, zoom_list_recordings, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP directly.