list_meetingsLABSCO SUMMARY
Transcripts land on your disk in a structure you can still use a year later.
Each transcript is written as a .vtt under a YYYY-MM folder with a metadata JSON beside it, carrying the topic, start time, duration and the participants pulled out of the transcript itself. Search then runs locally over what you have already downloaded, so the searchable corpus is exactly the set of meetings you chose to keep.
What it is
An MCP server for Zoom Cloud Recording transcripts. It lists meetings, downloads their transcripts into a dated folder structure and searches what you have downloaded.
What you get
- List meetings that have recordings, filtered by date range or participant — list_meetings
- Download a transcript by meeting ID or UUID — download_transcript
- Grab the last few meetings in one call — get_recent_transcripts
- Search across everything you have downloaded — search_transcripts
- Storage organized by month, with a metadata JSON beside each .vtt holding topic, start time, duration and participants
Requirements
Node.js v16 or higher and a Zoom Server-to-Server OAuth app: ZOOM_ACCOUNT_ID, ZOOM_CLIENT_ID and ZOOM_CLIENT_SECRET, with the cloud_recording read scopes granted. TRANSCRIPTS_DIR sets where files land, defaulting to ./transcripts.
Setup effort
Build from source — git clone https://github.com/forayconsulting/zoom_transcript_mcp.git
USE CASES
01
Finding which meeting something was said in
Search your downloaded transcripts for the phrase instead of reopening recordings one by one.
02
Catching up after time away
Pull the last several meetings in one call and read them rather than watch them.
03
Grabbing one meeting you have the ID for
Download that transcript alone, by meeting ID or UUID.
04
Seeing what is available before downloading anything
List meetings with recordings over a date range, optionally filtered by participant.
4 tools
Listed in project docs. Your client may show a different list.
download_transcriptget_recent_transcriptssearch_transcriptsBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- Node.js
- ZOOM_ACCOUNT_ID in your environment
- ZOOM_CLIENT_ID in your environment
- ZOOM_CLIENT_SECRET in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/forayconsulting/zoom_transcript_mcp.git
cd zoom_transcript_mcp
npm install
npm run buildMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"zoom-transcripts": {
"command": "node",
"args": [
"<YOUR_PATH_TO_ZOOM_TRANSCRIPT_MCP>/build/index.js"
],
"env": {
"ZOOM_ACCOUNT_ID": "<YOUR_ZOOM_ACCOUNT_ID>",
"ZOOM_CLIENT_ID": "<YOUR_ZOOM_CLIENT_ID>",
"ZOOM_CLIENT_SECRET": "<YOUR_ZOOM_CLIENT_SECRET>",
"TRANSCRIPTS_DIR": "<YOUR_TRANSCRIPTS_DIR>"
}
}
}
}
