Zoom API MCP Server

Created By
mattcoatswortha year ago
Overview

what is Zoom API MCP Server?

Zoom API MCP Server is a comprehensive Model Context Protocol (MCP) server designed for seamless interaction with the Zoom API, enabling developers to manage various Zoom functionalities.

how to use Zoom API MCP Server?

To use the Zoom API MCP Server, clone the repository, install the necessary dependencies, set up your Zoom API credentials in a .env file, and run the server using Node.js.

key features of Zoom API MCP Server?

  • Complete coverage of Zoom API endpoints
  • OAuth 2.0 authentication support
  • Structured tools with proper validation
  • Comprehensive API documentation resources
  • Robust error handling and response formatting

use cases of Zoom API MCP Server?

  1. Creating and managing Zoom meetings programmatically.
  2. Automating user management within a Zoom account.
  3. Generating reports and accessing cloud recordings.

FAQ from Zoom API MCP Server?

  • What are the prerequisites for using the server?

You need Node.js 16+ and valid Zoom API credentials (Client ID, Client Secret, Account ID).

  • How do I run the server?

After setting up your environment, run the server using the command npm run dev.

  • Can I test the server functionality?

Yes! You can test the server using the MCP Inspector with the command npm run inspect.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mattcoatsworth
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Alloy

2 days ago
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)

12 hours ago
Crevio

a day ago