MA
Developer Tools

Manage Zoom Meetings MCP Server

Manage Zoom meetings on the MCP server: create, update, read, and delete meetings quickly and securely.

View on GitHub

Overview

The Manage Zoom Meetings MCP Server is a small REST service that exposes CRUD (create, read, update, delete) operations for Zoom meetings and provides an MCP-compatible interface so AI agents or external tools can call those operations programmatically. It acts as a thin adapter between your Zoom account and Model Context Protocol (MCP) workflows, letting agent-driven systems schedule, modify, fetch, or remove meetings without embedding Zoom credentials or API logic into the agent itself.

This server is useful when you want a reliable, auditable, and secure boundary between AI-driven decision-making and Zoom operations. By centralizing Zoom access behind an MCP endpoint, you can enforce access control, logging, rate limiting, and credential rotation while exposing a simple, consistent tools surface to agents and developer clients.

Features

  • CRUD endpoints for Zoom meetings (create, read, update, delete)
  • MCP-compatible tool descriptor for agent integration
  • Uses environment variables for Zoom credentials and server configuration
  • Simple REST API usable by HTTP clients, agents, or workflows
  • Example client calls (curl) and JSON payloads for common operations
  • Optional Docker support for easy deployment

Installation / Configuration

Clone the repository and install dependencies:

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

Create an .env file (example values shown):

PORT=3000
ZOOM_API_KEY=your_zoom_api_key
ZOOM_API_SECRET=your_zoom_api_secret
ZOOM_OAUTH_TOKEN=your_zoom_oauth_token     # optional if using OAuth
MCP_API_KEY=your_internal_mcp_api_key      # optional: server-level auth for agents

Run locally:

npm start
# or, for development
npm run dev

Docker:

docker build -t zoom-mcp-server .
docker run -d -p 3000:3000 \
  -e PORT=3000 \
  -e ZOOM_API_KEY=... \
  -e ZOOM_API_SECRET=... \
  zoom-mcp-server

Security notes:

  • Use HTTPS in production and never commit secrets to source control.
  • Prefer OAuth or short-lived tokens for Zoom where possible.
  • Protect MCP endpoints with API keys or other auth layers.

Available Resources

  • Source code and issues: https://github.com/Prathamesh0901/zoom-mcp-server
  • API endpoints (typical):
    • GET /meetings — list meetings
    • GET /meetings/:id — fetch meeting details
    • POST /meetings — create a meeting
    • PUT /meetings/:id — update a meeting
    • DELETE /meetings/:id — delete a meeting
    • GET /mcp/tools (or /openapi.json) — MCP/OpenAPI descriptor for agent consumption

If the repository exposes OpenAPI or a Postman collection, use those artifacts to generate client code or import tests.

API Reference (quick table)

EndpointMethodDescription
/meetingsGETList meetings (filtering via query params)
/meetingsPOSTCreate a new Zoom meeting
/meetings/:idGETRetrieve details for a specific meeting
/meetings/:idPUTUpdate meeting metadata (time, topic, settings)
/meetings/:idDELETERemove a meeting
/mcp/toolsGETMCP-compatible tools descriptor for agent integration

Example create request:

curl -X POST "http://localhost:3000/meetings" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $MCP_API_KEY" \
  -d '{
    "topic": "Planning Sync",
    "start_time": "2026-05-01T15:00:00Z",
    "duration": 30,
    "timezone": "UTC",
    "agenda": "Sprint planning"
  }'

Example response (abridged):

{
  "id": "123456789",
  "topic": "Planning Sync",
  "start_time": "2026-05-01T15:00:00Z",
  "join_url": "https://zoom.us/j/123456789"
}

Use Cases

  • AI assistant schedules a meeting: An assistant decides a meeting is needed and calls the MCP tool to create a Zoom meeting with the chosen topic, time, and invite list. The server returns the meeting link which the assistant can share.
  • Automated calendar sync: A background workflow reads calendar events and uses the MCP server to create or update Zoom meetings so event attendees always have working join URLs.
  • Bulk updates and administration: Admin scripts can query meetings across accounts and bulk-update settings (e.g., enable waiting rooms) without direct access to Zoom credentials.
  • Agent sandboxing: When you expose tools to generative agents, using this server keeps Zoom credentials out of the agent environment while providing a constrained, auditable surface for meeting operations.

Troubleshooting & Best Practices

  • If calls fail, first verify Zoom credentials and token expiry. Switch to OAuth tokens for production where feasible.
  • Check server logs for request/response details and Zoom API error codes.
  • Rate limit agent access and add request validation to avoid malformed meeting data.
  • Maintain an OpenAPI or tools descriptor to allow agents to discover the server capabilities automatically.

For full implementation details, examples, and issues, see the project repository: https://github.com/Prathamesh0901/zoom-mcp-server.

Tags:developer-tools