Zoom Transcript MCP Server

If you already use Zoom Transcript MCP, the zoom transcript mcp mcp server is the piece that lets your assistant work with it directly. MCP server for managing Zoom Cloud Recording transcripts.

What the server does

An MCP (Model Context Protocol) server for interacting with Zoom Cloud Recording transcripts. This server allows you to list, download, search, and manage your Zoom meeting transcripts through a structured interface.

• List Meetings — View all available Zoom meetings with recordings
• Download Transcripts — Download transcripts from specific meetings by ID or UUID
• Get Recent Transcripts — Automatically download transcripts from recent meetings
• Search Transcripts — Search across all downloaded transcripts for specific content
• Organized Storage — Transcripts are stored in a structured file system by month

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Building — The Building tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: ZOOM_ACCOUNT_ID, ZOOM_CLIENT_ID, ZOOM_CLIENT_SECRET, TRANSCRIPTS_DIR. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js (v16 or higher) - Zoom Account with Cloud Recording enabled - Zoom OAuth App credentials (Account ID, Client ID, Client Secret)

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

This sits in the file and storage access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Zoom Transcript MCP's toolset — Building — is a fair guide to whether it matches your workflow. It is maintained by forayconsulting; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Zoom Transcript MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.