Package Exports
- @sweatco/zoom-mcp
- @sweatco/zoom-mcp/dist/index.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@sweatco/zoom-mcp) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
@sweatco/zoom-mcp
MCP server for Zoom - access meeting transcripts and AI summaries from Claude.
Features
- List meetings - Browse your recent Zoom meetings
- Get transcripts - Full verbatim transcripts from recorded meetings
- Get AI summaries - AI Companion meeting summaries with action items
- Search - Find meetings by keywords
- Admin queries - Admins can query any user's meetings (with proxy)
Quick Start (Basic Setup)
Works with any organization. Just needs a Zoom OAuth app.
Prerequisites
- Zoom Pro, Business, or Enterprise account
- Cloud recording OR AI Companion enabled for meetings
Installation
Add to Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"zoom": {
"command": "npx",
"args": ["-y", "@sweatco/zoom-mcp"],
"env": {
"ZOOM_CLIENT_ID": "12HSakNTRpGJCHXGOgbPFQ",
"ZOOM_OAUTH_URL": "https://europe-west1-zoom-mcp-oauth.cloudfunctions.net/zoom-mcp-oauth"
}
}
}
}First Use
- Restart Claude after adding the config
- Ask Claude about your Zoom meetings
- Browser opens for one-time Zoom authorization
- Done! No re-authorization needed.
Zoom API Limitations
The basic setup uses Zoom's standard API, which has some limitations:
| Limitation | Impact |
|---|---|
| Only hosted meetings | You can only access meetings you hosted, not meetings you attended |
| 6-month history | Report API only returns meetings from the last 6 months |
| No cross-user queries | Cannot query another user's meetings, even as admin |
| Rate limits | ~10 requests/second |
To overcome these limitations, set up the Organization Proxy.
Organization Proxy
The proxy removes API limitations by indexing meeting participation in your own infrastructure (Google Cloud). Benefits:
What the Proxy Enables
| Feature | Without Proxy | With Proxy |
|---|---|---|
| Meetings you hosted | ✅ | ✅ |
| Meetings you attended | ❌ | ✅ |
| Historical data | 6 months | Unlimited (with backfill) |
| Admin: query any user | ❌ | ✅ |
| Admin: org-wide search | ❌ | ✅ |
How It Works
- Webhook captures
meeting.endedevents and indexes all participants - Firestore stores participant records in your GCP project
- Proxy API verifies user identity and returns authorized meetings
- Backfill script imports historical data
All data stays in your organization's infrastructure.
Admin Capabilities
With the proxy, Zoom Owners and Admins (role_id 0 or 1) can:
- Query any user's meetings:
list_meetingswithuser_emailparameter - Access any meeting's transcript/summary: No participation check required
- Audit access: All queries logged in Cloud Functions
Example: As admin, ask Claude "Show me meetings for user@company.com last week"
Setup
See the full Proxy Setup Guide for step-by-step instructions.
Quick overview:
- Create GCP project with Firestore
- Create Zoom Server-to-Server OAuth app with admin scopes
- Configure
meeting.endedwebhook - Deploy Cloud Functions (webhook handler, proxy API, cleanup job)
- Run backfill script for historical data
- Add
ZOOM_PROXY_URLto MCP client config
Configuration with Proxy
{
"mcpServers": {
"zoom": {
"command": "npx",
"args": ["-y", "@sweatco/zoom-mcp"],
"env": {
"ZOOM_CLIENT_ID": "your-zoom-client-id",
"ZOOM_OAUTH_URL": "https://REGION-PROJECT.cloudfunctions.net/zoom-mcp-oauth",
"ZOOM_PROXY_URL": "https://REGION-PROJECT.cloudfunctions.net/zoom-proxy-api"
}
}
}
}Available Tools
| Tool | Description |
|---|---|
list_meetings |
List recent meetings with transcript/summary availability |
get_transcript |
Get full meeting transcript |
get_summary |
Get AI Companion meeting summary |
get_meeting |
Get meeting details and participants |
search_meetings |
Search meetings by keywords |
Admin-only Parameters
With proxy configured:
list_meetings:
user_email: "user@company.com" # Query another user's meetings (admin only)Example Prompts
Basic:
- "Show me my Zoom meetings from last week"
- "Get the transcript from my meeting with John yesterday"
- "What were the action items from yesterday's standup?"
- "Summarize my meeting from this morning"
Admin (with proxy):
- "Show me meetings for katie@company.com last week"
- "Get the summary of the all-hands meeting"
- "What did the product team discuss in their sync?"
Transcript Sources
The MCP automatically finds the best available transcript:
| Source | When Available |
|---|---|
| Cloud Recording VTT | Meeting was cloud recorded with "Audio transcript" enabled |
| AI Companion Summary | AI Companion was enabled (recording not required) |
Troubleshooting
"No meetings found"
- Check that you have cloud recordings or AI Companion enabled
- Verify your Zoom account is Pro/Business/Enterprise
- Without proxy: you can only see meetings you hosted
"Authorization required" keeps appearing
- Run
npx @sweatco/zoom-mcp --logoutand re-authorize - Check your Zoom account permissions
"No transcript available"
- The meeting may not have been recorded
- AI Companion may not have been enabled
- Transcript may still be processing (wait ~2x meeting duration)
"Admin access required"
- Only Zoom Owners (role_id=0) and Admins (role_id=1) can query other users
- Requires proxy to be configured
"You must supply a command" or npx errors
- This happens when Claude Desktop uses an old Node.js version (e.g., Node 14)
- If you use nvm, GUI apps like Claude Desktop don't run your shell profile
- Fix: Add PATH to your MCP config to point to the correct Node version:
{
"mcpServers": {
"zoom": {
"command": "npx",
"args": ["-y", "@sweatco/zoom-mcp"],
"env": {
"PATH": "/Users/YOUR_USERNAME/.nvm/versions/node/v20.19.4/bin:/usr/bin:/bin",
"ZOOM_CLIENT_ID": "12HSakNTRpGJCHXGOgbPFQ",
"ZOOM_OAUTH_URL": "https://europe-west1-zoom-mcp-oauth.cloudfunctions.net/zoom-mcp-oauth"
}
}
}
}- Replace
YOUR_USERNAMEand Node version with your actual values - Find your Node path with:
which node
Privacy & Data
Basic setup:
- Credentials stored in your OS keychain (or
~/.config/zoom-mcp/) - Data flows only between your machine and Zoom's API
With proxy:
- Meeting participant data stored in your organization's GCP Firestore
- All data stays within your infrastructure
- Monthly cleanup job removes records older than 1 year
Revoke access anytime: Zoom App Marketplace
Development
# Install dependencies
npm install
# Build
npm run build
# Test locally
npx .
# Test with MCP Inspector
npx @modelcontextprotocol/inspector node dist/index.js
# Clear stored tokens
npx . --logoutCloud Functions
cd cloud-functions
npm install
npm run build
npm run deploy:oauth # Deploy OAuth function
npm run deploy:webhook # Deploy webhook handler
npm run deploy:api # Deploy proxy API
npm run deploy:cleanup # Deploy cleanup jobScripts
# Backfill historical data
npx tsx scripts/backfill.ts --from=2025-08-01 --to=2025-08-31
# Debug: check user meetings from Zoom API
npx tsx scripts/check-user-meetings.ts user@company.com
# Debug: check Firestore records
npx tsx scripts/check-firestore.ts user@company.comLicense
MIT