MCP Connector

Manage Zoom meetings through AI assistants

MCP server that creates, updates, deletes, and retrieves Zoom meetings from Claude or Cursor via a Server-to-Server OAuth app.

Works with zoomclaudecursor

26
Spark score
out of 100
Updated Jun 2025
Source checked Sep 10, 2026
Version 1.0.0

Add to Favorites

Why it matters

Enable AI assistants like Claude and Cursor to programmatically create, update, retrieve, and delete Zoom meetings on your behalf, eliminating manual scheduling tasks and integrating video conferencing directly into AI-powered workflows.

Outcomes

What it gets done

01

Create new Zoom meetings with custom settings via natural language

02

Retrieve a list of all active Zoom meetings in your account

03

Update existing meeting details like time, duration, or settings

04

Delete Zoom meetings that are no longer needed

Source

Get it from source

Spark does not host a copy of it.

Open source

Reports

Agent outcome reports

No reports yet

Overview

Zoom

Zoom MCP Server gives an assistant tools to create, update, delete, and retrieve Zoom meetings through a standardized MCP interface, with Zod schema validation on every tool's parameters. Use it when Claude or Cursor needs to manage a Zoom account's meetings directly. It requires a Server-to-Server OAuth app with meeting permissions created in the Zoom Marketplace.

What it does

Zoom MCP Server gives Claude, Cursor, or another MCP client a standardized interface for managing Zoom meetings - it exposes tools to create, update, delete, and retrieve meetings, each validated with Zod schemas for its parameters.

When to use - and when NOT to

Use it when an assistant needs to manage a Zoom account's meetings directly - scheduling, editing, cancelling, or listing them - without switching to the Zoom dashboard. It works the same way with either Claude or Cursor, since both read the same MCP server block, but each keeps it in its own config file (claude_desktop_config.json for Claude, .cursor/mcp.json for Cursor). It requires a Server-to-Server OAuth app registered in the Zoom Marketplace with all Meeting permissions enabled, so it isn't a fit if you can't create that app or don't want to hand an assistant credentials with meeting-management scope.

Capabilities

  • 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.
  • Parameter validation on every tool via Zod schemas.

How to install

First create a Server-to-Server OAuth app in the Zoom Marketplace (Build App → Server to Server OAuth App → add all Meeting permissions → activate) to get an Account ID, Client ID, and Client Secret. Then configure the MCP client:

{
  "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"
      }
    }
  }
}

For local development, clone the repository, run npm install, then npm run dev (or npm run build followed by npm start for the compiled server). It is licensed under the MIT License.

Who it's for

Teams that want an assistant to schedule, edit, or clean up Zoom meetings directly from Claude or Cursor instead of the Zoom web dashboard.

Source README

Zoom MCP Server

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

This server enables you to create, update, delete, and retrieve Zoom meetings using a standardized MCP interface, making it easy to integrate with AI tools like Claude and Cursor.


⚙️ Claude / Cursor Configuration

To use this MCP server with Claude or Cursor, add the following to your MCP config file( Claude: claude_desktop_config.json | Cursor: .cursor/mcp.json ):

Step 1. Get Zoom Client ID, Zoom Client Secret and Account ID

  1. visit Zoom Marketplace
  2. Build App and choose Server to Server OAuth App
  3. Add Scope > Meeting > Select All Meeting Permissions
  4. Active your app
    then you can get Account ID, Client ID, Client Secret in App Credentials page

Step 2. Config 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"
      }
    }
  }
}

🛡️ Replace the credentials with your Zoom App credentials created on the Zoom Marketplace.


🛠 Features

Tool Description
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

Each tool is implemented using Zod schema validation for parameters.


🧑‍💻 Local Development

Clone the repo:

git clone https://github.com/Prathamesh0901/zoom-mcp-server.git
cd zoom-mcp-server

Install dependencies:

npm install

Run in development mode:

npm run dev

Build for production:

npm run build

Run the compiled server:

npm start

🤝 Contributing

Contributions are welcome and appreciated! To contribute:

  1. Fork the repository
  2. Create a new branch:
    git checkout -b feature/your-feature-name
    
  3. Make your changes and commit:
    git commit -m "Add some feature"
    
  4. Push to your fork and open a pull request.

📄 License

This project is licensed under the MIT License.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.