zoom

MCP server from mattcoatsworth/zoom-mcp-server

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio mattcoatsworth-zoom-mcp-server npx -y mattcoatsworth-zoom-mcp-server \
  --env ZOOM_CLIENT_ID="your_client_id" \
  --env ZOOM_ACCOUNT_ID="your_account_id" \
  --env ZOOM_CLIENT_SECRET="your_client_secret"

How to use

This MCP server provides a comprehensive bridge to the Zoom API within the Model Context Protocol framework. It exposes MCP-compatible endpoints for interacting with Zoom resources such as meetings, users, webinars, and more, while handling OAuth 2.0 authentication automatically using your Server-to-Server OAuth credentials. Once running, you can send MCP requests through the inspector or your client to create, read, update, or delete Zoom resources and to retrieve API documentation resources for reference.

The server offers categorized tools aligned with Zoom APIs, including Meetings, Users, Webinars, Accounts, Chat, Phone, Contacts, Recordings, Reports, Webhooks, and Zoom Rooms. Each tool includes validation and structured request/response formatting to ensure consistent MCP behavior and error handling. Environment configuration is required to supply Zoom credentials, after which the server will manage token acquisition and refreshing under the hood.

How to install

Prerequisites:

Node.js 16+ (as stated by the project)
npm (comes with Node.js)
Zoom API credentials: Client ID, Client Secret, and Account ID

Installation steps:

Clone the repository: git clone https://github.com/<owner>/mattcoatsworth-zoom-mcp-server.git cd mattcoatsworth-zoom-mcp-server
Install dependencies: npm install
Create a .env file with your Zoom API credentials: ZOOM_CLIENT_ID=your_client_id ZOOM_CLIENT_SECRET=your_client_secret ZOOM_ACCOUNT_ID=your_account_id
Start the server (development mode): npm run dev
(Optional) Run MCP Inspector to test endpoints: npm run inspect

Additional notes

Environment variables:

ZOOM_CLIENT_ID: Your Zoom OAuth client ID
ZOOM_CLIENT_SECRET: Your Zoom OAuth client secret
ZOOM_ACCOUNT_ID: Your Zoom account ID

Common issues:

Missing or invalid Zoom credentials will prevent token retrieval; ensure the credentials are correct and have the necessary permissions.
Ensure Node.js 16+ is installed and npm install completed successfully.
If using npm run dev, ensure the environment (.env) file is loaded; consider using a dotenv setup in your environment if you deploy elsewhere.

Configuration tips:

You can customize the server by adjusting Zoom API scopes on your OAuth app to match the features you need (meetings, users, webinars, etc.).
When testing, use the MCP Inspector to verify request shapes and responses before wiring to your client.

Related MCP Servers

zen

1.1k

Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage

MCP -Deepseek_R1

A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)

mcp-fhir

A Model Context Protocol implementation for FHIR

mcp

Inkdrop Model Context Protocol Server

mcp-appium-gestures

This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..

dubco -npm

The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.