Zoom MCP Server

Created By
Prathamesh0901a year ago
Overview

What is Zoom MCP Server?

Zoom MCP Server is a Model Context Protocol (MCP) server designed for managing Zoom meetings through AI tools like Claude and Cursor. It allows users to create, update, delete, and retrieve Zoom meetings using a standardized interface.

How to use Zoom MCP Server?

To use the Zoom MCP Server, configure it in your MCP config file for Claude or Cursor with your Zoom App credentials. You can then execute commands to manage your Zoom meetings.

Key features of Zoom MCP Server?

  • Retrieve all active Zoom meetings with get_meetings command.
  • Create new Zoom meetings using create_meeting command.
  • Update existing meetings with update_meeting command.
  • Delete Zoom meetings using delete_meeting command.

Use cases of Zoom MCP Server?

  1. Automating Zoom meeting management for applications.
  2. Integrating Zoom functionalities into AI-driven tools.
  3. Streamlining meeting scheduling and updates for users.

FAQ from Zoom MCP Server?

  • How do I configure the server with my Zoom credentials?

You need to replace the placeholders in the MCP config file with your actual Zoom App credentials.

  • Is there a way to run this server locally?

Yes! You can clone the repository, install dependencies, and run it in development mode.

  • What programming language is used in this project?

The project is developed using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Prathamesh0901
Star
1
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago