Zoom and MCP: meeting notes and scheduling drafts for an agent

Zoom has an official MCP server that lets a compatible AI agent work with meeting information and scheduling operations. For meeting notes and scheduling drafts, start with read access and keep actual meeting changes behind explicit approval; this workflow gives an assistant no role as your representative in calls. See the Zoom MCP overview.

Documentation and offer details below are stated as of 30 Oct 2026. This guide belongs to MCP servers for apps.

What it can do

A useful starting task is a handover after a project meeting: use an authorized summary to draft decisions, unresolved questions and proposed next actions. Ask the assistant to keep the meeting reference beside each conclusion. Treat a suggested owner or deadline as unconfirmed unless the source supports it. Someone reviewing the draft should be able to distinguish a recorded decision from the assistant's interpretation without reopening every document.

For scheduling, prepare a proposal containing the host, topic, date, time zone, duration and intended invitees. Keep it as text until reviewed. Do not assume that seeing scheduled meetings proves everyone is free: make availability verification a separate requirement before approving a booking.

The official catalogue distinguishes tools and permissions:

Exclude in_meeting_control (meeting:update:in_meeting_controls) from this workflow. Confirm these mappings in the Meetings reference before configuring access.

Reading data still sends information into the assistant's context. Give it only the meetings needed for the task, and decide where the resulting notes may be stored. A request to summarize a discussion does not authorize emailing participants, changing invitees or publishing the summary. The MCP permissions guide explains how to make that boundary explicit.

MCP access and API access are different choices

Zoom documents remote MCP authentication using OAuth 2.1 with PKCE for the authorization-code flow. Its server overview also explains that MCP rate limits are shared with Zoom Open APIs at account level. A connector does not create a separate allowance.

A custom API adapter is another route. The Meetings API documents GET /meetings/{meetingId}/meeting_summary, using the meeting UUID, with granular scopes meeting:read:summary or meeting:read:summary:admin. That API permission is distinct from the MCP asset permission above. Do not copy scopes between recipes just because both mention summaries.

Choose the narrowest account reach that satisfies the job. Require a reason before granting an admin scope. If you build an adapter, document its exposed operations and failure handling; an API endpoint's existence does not establish that a particular MCP server exposes it. See MCP versus APIs and function calling for the architectural distinction.

How to connect it safely

1. Define the deliverable. Start with a meeting you are authorized to inspect. Write down the allowed inputs and expected output, such as a private follow-up draft. Explicitly exclude joining calls, live controls, sending messages and modifying meetings. A prompt is useful guidance; enforce the same limits through permissions and tool selection.

2. Register the integration. Zoom's connection instructions require a General app in Zoom App Marketplace, appropriate admin or developer authorization, and relevant product licenses. Registration is manual; automatic dynamic client registration is unsupported. Configure the client's actual redirect URL and only the scopes needed for the chosen tools.

3. Verify authentication compatibility. Follow the client-specific OAuth setup, including PKCE. The client must send the resulting access token as a Bearer token. Check that it supports Zoom's manual registration before proceeding. Keep secrets out of prompts, meeting notes and committed configuration. Do not substitute your ordinary Zoom password for application credentials.

4. Add the remote server in the editor. In a compatible VS Code agent client, open the command palette, run MCP: Add Server, choose HTTP and enter https://mcp.zoom.us/mcp/meeting/streamable. Use the endpoint from the Meetings catalogue rather than an unrelated server's configuration. Follow the VS Code setup documentation for the selected client and configuration destination. Adding a URL alone does not finish Zoom authorization.

5. Restrict tools and verify a read. Enable only the needed retrieval tools, inspect the actual tool call and compare its result with the known meeting. Then request a draft and verify its evidence. Keep create, update, delete and live-control tools unavailable during this trial. The VS Code MCP guide provides broader client setup context.

6. Approve writes separately. If booking is later required, review the exact host, time zone, recurrence, participants and meeting settings before authorizing it. Afterward, inspect the returned meeting and confirm the intended change. If a write times out, inspect the current state before repeating it; an uncertain response should not become a duplicate booking.

When this does not work

The summary was never available. Zoom's Meeting Summary guidance requires an eligible licensed user and the feature enabled; availability also varies by region and industry. It does not support breakout rooms. Check those prerequisites before expecting a summary retrieval task to succeed.

Authentication works but access fails. The summary API documents restrictions involving email-only sharing, allowed IP ranges and summaries moved to Trash; it also excludes end-to-end encrypted meetings. Diagnose the restriction rather than widening permissions automatically. See the API reference for the applicable requirements.

The answer has weak evidence. A draft can sound precise while mixing an unresolved suggestion with a decision. Require source references and mark missing owners or dates as unknown. Read source-linked answers before turning meeting notes into commitments.

The client cannot complete registration. Check the current documentation for supported authentication settings. Keep a manual workflow using an authorized excerpt until the integration is configured; never work around access failures with someone else's credentials.

Where Tvijo fits

As of 30 Oct 2026, the DSHREM VS Code extension offers an editor entry for selected context and bounded tasks. A practical starting point is to attach an authorized, minimized meeting summary and request a follow-up draft. Review the text before copying it elsewhere. That is a document workflow, not a ready Zoom connector.

TvijoCode is a test build with the extension embedded. Tvijo MCP makes Tvijo callable from a compatible MCP client; it does not automatically make the editor a client for every other server. Editor MCP integration and safe delegation remain planned work in the published product account. Keep those directions separate when designing a Zoom workflow.

Use Tvijo here to prepare meeting summaries and scheduling drafts from material you may submit. This proposal includes no acting as the user in calls. Review permissions and data flow before attaching private meeting content.

The Tvijo workspace lists Try at $0 as of 31 Oct 2026: up to 50 tasks, 100,000 tokens or $0.05 of sponsored usage, whichever is reached first, sharing a $1 daily pool funded by TVIJO. Service credit is shown as $10: prepaid credit is requested, usage is metered with an 8% service markup, payment collection is not activated, and an order is not a charge.

FAQ

Is there an official Zoom MCP server?

Yes. Zoom publishes a product-specific Meetings server and connection documentation, linked above. Check the current documentation for access requirements before choosing a client.

Can an agent prepare notes without attending the call?

Design the workflow around an existing, authorized summary or excerpt. Keep call participation outside its permissions and verify the resulting notes against that material.

Does connecting MCP authorize automatic scheduling?

Define booking as a separate approved action. Keep the initial deliverable as a scheduling draft and enable write access only when the exact change is authorized.

Zoom is a trademark of its owner. Tvijo is not affiliated with or endorsed by it.