MCP Server for Zoom (No Auth) - Python & Node.js

Created By
peakmojoa year ago
A MCP server for accessing Zoom recordings and transcripts without requiring direct authentication from the end user.
Overview

What is MCP Server for Zoom (No Auth)?

MCP Server for Zoom (No Auth) is a Model Control Protocol server that allows users to access Zoom recordings and transcripts without requiring direct authentication from the end user. It simplifies the interaction with the Zoom API by managing OAuth flows internally.

How to use MCP Server for Zoom (No Auth)?

To use the MCP Server, clone the repository, install the required dependencies, and start the server. You can then use various tools provided by the server to interact with Zoom recordings and transcripts.

Key features of MCP Server for Zoom (No Auth)?

  • OAuth credential management through tool arguments (no local auth flow)
  • List user's cloud recordings with pagination
  • Get detailed information about specific meeting recordings
  • Access meeting transcripts

Use cases of MCP Server for Zoom (No Auth)?

  1. Accessing and managing Zoom cloud recordings without user authentication.
  2. Automating the retrieval of meeting transcripts for analysis.
  3. Integrating Zoom recording functionalities into other applications without user intervention.

FAQ from MCP Server for Zoom (No Auth)?

  • Do I need to authenticate to use this server?

No, this server is designed to operate without requiring direct user authentication.

  • How do I obtain OAuth credentials?

You need to create a Zoom OAuth app in the Zoom Marketplace and configure the required scopes for recordings access.

  • Can I run this server in a headless environment?

Yes, the server is designed to run in a headless environment without storing any credentials.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
peakmojo
Star
2
Language
Python
License
Apache-2.0 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
Crevio

2 days ago