Zoom Transcript MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZOOM_CLIENT_ID | Yes | Your Zoom client ID from the Server-to-Server OAuth app | |
| TRANSCRIPTS_DIR | No | Path to the directory where transcripts will be stored | ./transcripts |
| ZOOM_ACCOUNT_ID | Yes | Your Zoom account ID | |
| ZOOM_CLIENT_SECRET | Yes | Your Zoom client secret from the Server-to-Server OAuth app |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_recent_transcriptsC | Get and download transcripts from recent Zoom meetings. This tool will access the Zoom cloud API to fetch and download recent meeting transcripts. |
| search_transcriptsB | Search across Zoom meeting transcripts for specific content. This tool will search through locally stored transcripts first. |
| extract_action_itemsC | Identify and extract action items, tasks and commitments from meeting transcripts |
| check_local_transcriptsC | Check what transcripts are already downloaded and available locally |
| download_transcriptA | Download a specific Zoom meeting transcript from the cloud to local storage |
| list_meetingsC | List available Zoom meetings with recordings that exist in the cloud |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no ambiguity: checking local transcripts, downloading from cloud, extracting action items, getting recent transcripts, listing meetings, and searching transcripts. The descriptions clearly differentiate their functions, such as distinguishing between local vs. cloud operations and specific tasks like extraction vs. searching.
All tool names follow a consistent verb_noun pattern using snake_case, such as check_local_transcripts, download_transcript, and extract_action_items. The naming is predictable and readable throughout, with no deviations in style or convention.
With 6 tools, the server is well-scoped for managing Zoom transcripts, covering core operations like listing, downloading, extracting, and searching. Each tool earns its place by addressing a specific need in the workflow, avoiding bloat or thin coverage.
The tool set provides strong coverage for the transcript management domain, including listing, downloading, extracting, and searching. A minor gap exists in update or delete operations for transcripts, but agents can work around this, and the core workflows are well-supported.