Get the FREE Ultimate OpenClaw Setup Guide →

zoom

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

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio prathamesh0901-zoom-mcp-server npx -y @prathamesh0901/zoom-mcp-server \
  --env ZOOM_CLIENT_ID="Your Zoom Client ID" \
  --env ZOOM_ACCOUNT_ID="Your Zoom Account ID" \
  --env ZOOM_CLIENT_SECRET="Your Zoom Client Secret"

How to use

This MCP server provides a standardized interface to manage Zoom meetings via the Model Context Protocol. You can create, update, delete, and retrieve Zoom meetings using tools like get_meetings, create_meeting, update_meeting, and delete_meeting. Each tool is designed with parameter validation (via Zod schemas) to ensure you pass the correct fields for the corresponding operation. By integrating with Claude or Cursor through your MCP config, you can harness these capabilities within AI workflows to programmatically manage Zoom meetings.

To use the server, configure your MCP with the provided environment variables (Account ID, Client ID, and Client Secret) and then invoke the tools from your client or AI assistant. For example, use create_meeting with the desired meeting details (topic, start_time, duration, agenda, etc.), or get_meetings to fetch active meetings. The tools map to standard Zoom actions, wrapped behind a stable MCP API so you don’t need to manage Zoom API calls directly.

How to install

Prerequisites:

  • Node.js and npm installed on your machine
  • Access to modify your MCP config and provide Zoom credentials

Installation steps:

  1. Clone the repository
  2. Navigate to the project directory
    • cd zoom-mcp-server
  3. Install dependencies
    • npm install
  4. Set up environment variables for Zoom credentials (either in your MCP config or a local env file depending on your setup)
    • ZOOM_ACCOUNT_ID=Your Zoom Account ID
    • ZOOM_CLIENT_ID=Your Zoom Client ID
    • ZOOM_CLIENT_SECRET=Your Zoom Client Secret
  5. Run in development mode to test
    • npm run dev
  6. Build for production (optional)
    • npm run build
  7. Start the compiled server (production)
    • npm start

Additional notes

Tips:

  • Ensure your Zoom app is configured as a Server-to-Server OAuth app and has the appropriate Meeting scopes.
  • When using the MCP config, protect your credentials and avoid committing them to version control.
  • The tools validate inputs with Zod; provide the required fields such as topic, start_time, duration, and any meeting settings as per the tool you invoke.
  • If you encounter authentication errors, double-check the Zoom Account ID, Client ID, and Client Secret, and ensure they are correctly wired in your MCP configuration.
  • Monitor logs from npm run dev or the production start script to diagnose issues with meeting operations or MCP integration.

Related MCP Servers

Sponsor this space

Reach thousands of developers