Ranked roundup · Zoom
Best MCP Server for Zoom
The strongest MCP server for Zoom is the one Zoom ships itself — a rarity in this category, where most vendors leave the work to the community. Zoom hosts a remote MCP server at mcp.zoom.us, expanded in May 2026 into a family of product-scoped servers (Meetings, Team Chat, Docs, Whiteboard, Tasks, Workspace, Revenue Accelerator) that pull transcripts, AI Companion summaries, recordings and action items into Claude, ChatGPT and other MCP clients. The community layer is thinner than for most tools: the most-starred community repo has 29 stars and hasn't been touched since March 2025. So the real choice is between Zoom's official server, a managed aggregator like Composio (89 Zoom tools), and a couple of small transcript-focused projects. We ranked the five below on verifiable criteria — official status, last-commit dates, star counts, auth model, and documented capability coverage. No paid placement, no invented benchmarks; every number was checked against the GitHub API on the date below.
Facts checked September 1, 2026 · ranked on verifiable criteria · placement is never for sale
Founder, Automation Squad ·
The ranking
- Official · Zoom
Anyone on a paid Zoom plan who wants meeting summaries, transcripts and recordings inside Claude or ChatGPT with zero hosting
Meeting search, recordings, transcripts, AI Companion summaries, notes and action items, plus product-scoped servers for Team Chat, Docs (create/retrieve docs from Markdown), Whiteboard, Tasks, Calendar/Workspace and Revenue Accelerator; scheduling and workflow automation per Zoom's docs. Expanded May 2026 with agentic search across connected enterprise systems.
Remote, Zoom-hosted over streamable HTTP (endpoint mcp.zoom.us/mcp/zoom/streamable) — nothing to run locally · OAuth 2.1 with PKCE; manual registration of your own Zoom OAuth app (no dynamic client registration)
- Client registration is manual: you must create a Zoom OAuth app and register the client ID before connecting — there is no dynamic client registration, and the OAuth 2.1/PKCE handshake trips up some MCP clients
- Transcripts, summaries and recordings depend on paid-plan features (cloud recording, AI Companion); free accounts get little out of it
- The server implementation is closed-source; the last-pushed date above is for Zoom's public registry-metadata repo (zoom/mcp-registry), not the server code, so the star count is not a meaningful adoption signal
- Requires a Zoom account with admin/developer authorization and the respective product licenses for each product-scoped server
- Community
Agent builders who need write actions — creating meetings, managing webinars and users — without running or maintaining a server
89 tools and 11 triggers per Composio's docs: create/update/delete meetings, webinar and registrant management, recording access and deletion, whiteboards, user and device management, and Zoom Revenue Accelerator workflows — the broadest write surface of anything on this list.
Fully hosted by Composio; works with Claude, ChatGPT and Cursor with no server to run · Managed OAuth2 with automatic token refresh and rotation; built-in Zoom app for testing, own OAuth credentials recommended for production
- A third-party hosted layer sits between your Zoom account and your agent — meeting data transits Composio's infrastructure
- Several tools require paid Zoom tiers: meeting summaries need a paid Zoom account, webinar tools need a Pro plan with the webinar add-on
- Composio's own docs recommend configuring your own OAuth credentials for production rather than relying on its built-in app
- Community
Claude Desktop users who mainly want transcripts and AI Companion summaries of their own hosted meetings, installed in minutes
List recent meetings, full verbatim transcripts from recorded meetings, AI Companion summaries with action items, keyword search, and admin queries of other users' meetings when the org proxy is deployed.
Local via npx (Node 18+) in Claude Desktop; optional self-hosted org proxy · Zoom OAuth app with one-time browser sign-in; optional self-hosted organization proxy for admin/cross-user queries · MIT · 1★
- Tiny adoption: 1 GitHub star at verification
- Standard-API mode only reaches meetings you hosted, with a roughly 6-month report-history window and ~10 req/s rate limits — the documented fix requires deploying the project's organization proxy yourself
- Requires Zoom Pro, Business, or Enterprise with cloud recording or AI Companion enabled
- Community
Teams that want a self-hosted Python base to fork and extend against the raw Zoom API
General-purpose bridge to the Zoom API: user info, meeting details, recordings, account settings, with a debug mode. The most-starred community Zoom MCP repo.
Self-hosted local Python server (uv, Python 3.11+), stdio transport · Server-to-Server OAuth (account ID, client ID, client secret in a .env file); requires a Zoom admin to create the app · MIT · 29★
- No commits since March 4, 2025 — roughly 18 months stale at verification
- Thin implemented coverage: the README documents /users/me and says additional endpoints 'will be implemented as needed'
- Server-to-Server OAuth credentials are account-wide and admin-issued — a heavier security footprint than per-user OAuth
- Community
Building a local, searchable archive of Zoom cloud-recording transcripts
List meetings with cloud recordings, download transcripts by meeting ID or UUID, pull recent transcripts in bulk, and search across everything downloaded.
Self-hosted local Node.js server, stdio transport; transcripts stored on local disk organized by month · Server-to-Server OAuth (account ID, client ID, client secret in a .env file); requires a Zoom admin to create the app · MIT · 10★
- No commits since March 13, 2025 — roughly 18 months stale at verification
- Transcript-only: no meeting creation, AI summaries, or account administration
- Requires cloud recording (a paid-plan feature) and admin-created Server-to-Server OAuth credentials; transcripts are written to the local filesystem
Zoom MCP servers compared
| Server | Maintained by | Runs | Auth | License |
|---|---|---|---|---|
| Zoom MCP Server (official) | Zoom | Remote, Zoom-hosted over streamable HTTP (endpoint mcp.zoom.us/mcp/zoom/streamable) — nothing to run locally | OAuth 2.1 with PKCE; manual registration of your own Zoom OAuth app (no dynamic client registration) | — |
| Composio Zoom MCP (managed) | Community | Fully hosted by Composio; works with Claude, ChatGPT and Cursor with no server to run | Managed OAuth2 with automatic token refresh and rotation; built-in Zoom app for testing, own OAuth credentials recommended for production | — |
| @sweatco/zoom-mcp | Community | Local via npx (Node 18+) in Claude Desktop; optional self-hosted org proxy | Zoom OAuth app with one-time browser sign-in; optional self-hosted organization proxy for admin/cross-user queries | MIT |
| echelon-ai-labs/zoom-mcp | Community | Self-hosted local Python server (uv, Python 3.11+), stdio transport | Server-to-Server OAuth (account ID, client ID, client secret in a .env file); requires a Zoom admin to create the app | MIT |
| forayconsulting/zoom_transcript_mcp | Community | Self-hosted local Node.js server, stdio transport; transcripts stored on local disk organized by month | Server-to-Server OAuth (account ID, client ID, client secret in a .env file); requires a Zoom admin to create the app | MIT |
How to choose
Pick Zoom's official server if you're on a paid plan and mainly want meeting intelligence — transcripts, summaries, recordings — with nothing to host. Pick Composio if you need write-heavy automation (creating meetings, managing webinars and users) and will accept a third party in the data path. Pick @sweatco/zoom-mcp if you want a quick npx install for transcripts and summaries of meetings you hosted. Only reach for echelon-ai-labs or forayconsulting if you plan to fork and maintain the code yourself — both have sat untouched since March 2025.
How this ranking works
Every server here is real and was checked against its repository or vendor documentation on the date above — stars and licenses come from the GitHub API, not from memory. Order reflects verifiable criteria only: official support, maintenance recency, adoption, auth model, and documented capability coverage. We do not run paid placements, and we list every caveat we find, including the unflattering ones.
Common questions
- Does Zoom have an official MCP server?
- Yes. Zoom hosts a remote MCP server (endpoint mcp.zoom.us/mcp/zoom/streamable) plus product-scoped servers for Meetings, Team Chat, Docs, Whiteboard, Tasks, Workspace and Revenue Accelerator, with metadata published to the public MCP registry. Capabilities were expanded in May 2026 to cover summaries, transcripts, recordings, notes and action items in clients like Claude and ChatGPT.
- What does Zoom MCP authentication actually involve?
- The official server uses OAuth 2.1 with PKCE, but client registration is manual — you create a Zoom OAuth app and register your client ID before connecting, because Zoom doesn't support dynamic client registration. Community servers mostly use Server-to-Server OAuth instead, which means a Zoom admin issuing account-wide credentials (account ID, client ID, client secret) into environment variables.
- Can I pull meeting transcripts through MCP?
- Yes — that's the main use case — but transcripts require cloud recording or AI Companion, which are paid-plan features. Community servers using the standard API can generally only reach meetings you hosted, and Zoom's report API only covers roughly the last six months.
- Is there a no-code or managed option?
- Composio runs a hosted Zoom MCP with 89 tools and 11 triggers and handles OAuth token refresh for you. It has the widest tool surface of anything on this page, at the cost of routing your meeting data through a third party.
MCP servers we build
Automation Squad publishes its own open-source MCP servers and agent skills, documented with the same rules this ranking uses.