Zoom AI · MCP · Claude

How do you connect Claude AI agents to Zoom MCP?

By Michael Obraitis, Managing Partner, and Michael Dale, CEO · Published August 28, 2026 · Last reviewed August 2026 · ADAM Pulse Knowledge Base

Verification date.

Product names, APIs, connector lists, licensing notes, and MCP setup steps were checked against Zoom and Microsoft documentation on 28 August 2026. These details change. Confirm against live vendor pages and your own tenant before you buy, connect, or process regulated data.

Short answer

To give Claude Zoom meeting and workplace context, use Zoom's MCP path. The short route is the Zoom for Claude Connector in Claude's connector directory. The builder route is a Zoom Marketplace General app plus a custom connector in Claude.ai pointed at a Zoom MCP server URL, with OAuth and PKCE. There is no Dynamic Client Registration.

That connection is how Claude (and Codex, ChatGPT Developer Mode, Cursor, VS Code) reach Zoom's context layer, including Agentic Search's Search API and Ask API when those tools are on the server you connected. Permissions still follow Zoom and source ACLs. Empty results are usually admin settings, not a model failure.

Why the layer exists: Agentic Search complete guide. Which API to call once you are connected: Search API vs Ask API.

What are the two Claude paths?

Published connector versus custom MCP client, from Zoom developer docs.
Path	When to use it	Zoom-side work
Zoom for Claude Connector	Claude users who need meeting search, chat search, docs/Canvas, summaries, recordings	Licensed Zoom Workplace user; owner/admin as Zoom documents; enable Smart Recording and Meeting Summary; complete OAuth in Claude's directory
Custom connector on Claude.ai	You must pin a specific Zoom MCP server URL and Marketplace app	Build a General app; add scopes from that server's tool list; put `https://claude.ai/api/mcp/auth_callback` in the Zoom redirect URL; paste client ID/secret into Claude

Zoom's Claude connector notes: you only get meeting assets when you hosted the meeting or the host granted access, and Smart Recording and/or Meeting Summary are enabled for those assets. Video features need cloud recording with Smart Recording. If legal has blocked cloud recording, this connector will not magically transcribe from nothing.

How do you set up a custom Claude.ai connector?

Condensed from Zoom's Connect to Zoom MCP Servers page. Always prefer that page if the UI labels have moved.

In Zoom App Marketplace, Develop → Build app → General app.
Add OAuth scopes from the tool list on the Zoom MCP server you intend to use (for example meeting search scopes on the Meetings server). Zoom's plugin docs list MCP-specific scopes such as meeting:read:search and ai_companion:read:search that are not aliases of the older REST meeting:read scope.
In Claude.ai: Customize → Connectors → add custom connector. Name, remote MCP server URL (from Zoom's server page), OAuth client ID, OAuth client secret.
On the Zoom app, OAuth redirect URL: https://claude.ai/api/mcp/auth_callback.
Complete the OAuth consent as the Zoom user who should be the permission boundary. MCP calls run as that user.

Token exchange: POST https://zoom.us/oauth/token. Zoom uses OAuth 2.0 at that endpoint; the MCP spec wants OAuth 2.1, so the client must send code_verifier (PKCE). Subsequent MCP requests carry Authorization: Bearer.

Which Zoom MCP servers exist?

Zoom maps MCP servers to product areas. The developer table of contents lists at least: unified Zoom, Meetings, Chat, Canvas, Tasks, Whiteboard, and Revenue Accelerator. Overview transport examples:

Streamable HTTP: https://zoom.us/mcp/meeting/streamable
SSE: https://zoom.us/mcp/meeting/sse

Zoom also hosts mcp.zoom.us paths used by the official Claude plugin (unified /mcp/zoom/streamable, plus docs and whiteboard variants). Treat tools/list on the server you connected as authoritative. Do not assume every server exposes Agentic Search Ask API. Do not assume REST meeting CRUD exists on MCP; Zoom's own MCP skill guidance says deterministic meeting CRUD still belongs on REST.

How do Codex and ChatGPT connect?

Zoom documents a Zoom for Codex plugin aimed at turning transcripts and AI Companion summaries into follow-up artifacts, with the same warning: without recording or transcription, Codex may not have source material.

For ChatGPT, Zoom's MCP connect guide uses Developer Mode: Settings → Apps → Advanced → Developer mode, then Create app, MCP server URL, Authentication = OAuth, registration method User-Defined OAuth Client, token endpoint auth client_secret_basic. Put ChatGPT's callback URL into the Zoom app redirect field. Same General app pattern. Same PKCE requirement.

What should admins lock before the first connect?

Which users may authorize the Marketplace app.
Whether Meeting Summary and Smart Recording are allowed for the pilot group.
Which AI Studio data sources, if any, the mapped user can reach — Claude will retrieve what that user can see.
A rule that Claude drafts, humans send. ADAM Pulse does not auto-send mail or file tickets from an MCP session.

Frequently asked questions

What is the fastest way to connect Claude to Zoom?

Zoom's documented consumer path is the Zoom for Claude Connector in Claude's connector directory, then complete OAuth. That path searches meetings, chat, and docs / Canvas and retrieves summaries, recordings, and related assets, subject to Smart Recording and Meeting Summary being enabled and to host access.

How do I connect Claude.ai with a custom MCP server?

Zoom's Connect to Zoom MCP Servers guide: Claude.ai → Customize → Connectors → add custom connector. Enter the remote MCP server URL from the Zoom server page, plus OAuth client ID and secret from a Zoom Marketplace General app. Set the Zoom app redirect URL to https://claude.ai/api/mcp/auth_callback.

Does Zoom MCP support Dynamic Client Registration?

No. Zoom remote MCP servers require manual client registration: create a General app on the Zoom App Marketplace. Dynamic Client Registration and Client ID Metadata Documents are not supported.

Which URL do I use?

Use the URL printed on the Zoom MCP server page for the product you need. Zoom's overview example is https://zoom.us/mcp/meeting/streamable (Streamable HTTP) and a matching /sse path. Zoom's Claude plugin catalog also documents https://mcp.zoom.us/mcp/zoom/streamable for the unified server. Do not mix examples. Confirm with a live tools/list after connect.

What about Codex, ChatGPT, Cursor, or VS Code?

Zoom documents a Zoom for Codex plugin and a ChatGPT Developer Mode custom-app flow (OAuth, user-defined client, PKCE). Zoom's MCP FAQ lists Claude, Cursor, and VS Code as example clients. Each client has its own connector UI; the Zoom-side work is always a General app, scopes, and a redirect URI that client publishes.

Why does search return nothing?

Common causes Zoom documents: Smart Recording / Meeting Summary off; you were not the host and were not granted asset access; missing MCP scopes such as meeting:read:search; expired Bearer token; wrong server URL; identity mapping incomplete on AI Studio sources. Fix configuration before rewriting the agent prompt.

This page is part of the ADAM Pulse Zoom Agentic Search cluster. Existing Zoom AI Companion guides are related, not duplicates.

References

Primary vendor documentation. Where a vendor has not published a claim, this article says so rather than filling the gap.

ADAM Pulse can help design an Agentic Search pilot

ADAM Pulse helps Zoom customers pick sources, map identities, choose Search API versus Ask API, connect Claude or other MCP clients, and run a phased pilot with human review. This is a design engagement, not a product claim about Zoom. Support: (888) 989-4872 · support@adampulse.us

Prepared by ADAM Pulse (USA Telecom Consulting LLC) — managed Zoom and network services. Support: (888) 989-4872 · support@adampulse.us