zoom-whiteboard

warnings

mcp.zoom.us

Zoom Whiteboard server for creating boards and diagrams and locating existing boards.

https://mcp.zoom.us/mcp/whiteboard/streamableOAuthlast checked 3 Sep 2026spoke MCP on 3 of 3 checks (30 days)initialize in 206 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects with setup

Neither RFC 7591 registration nor a Client ID Metadata Document is advertised, so register a client with the issuer yourself and give Claude Code the client ID.

claude mcp add --transport http --client-id <your-client-id> --client-secret --callback-port 8080 zoom-whiteboard https://mcp.zoom.us/mcp/whiteboard/streamable

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects with setup

Neither RFC 7591 registration nor a Client ID Metadata Document is advertised, so register a client with the issuer yourself and give Claude (claude.ai & Desktop) the client ID.

Settings → Connectors → Add custom connector, then paste https://mcp.zoom.us/mcp/whiteboard/streamable. Under Advanced settings, enter the OAuth Client ID and Secret the issuer gave you.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✕ChatGPTNot supported

Registering a client by hand is not a flow ChatGPT documents, and this server advertises none that it does.

ChatGPT docs · read on 2026-08-30

✓CursorConnects with setup

Neither RFC 7591 registration nor a Client ID Metadata Document is advertised, so register a client with the issuer yourself and give Cursor the client ID.

{
  "mcpServers": {
    "zoom-whiteboard": {
      "url": "https://mcp.zoom.us/mcp/whiteboard/streamable"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects with setup

Neither RFC 7591 registration nor a Client ID Metadata Document is advertised, so register a client with the issuer yourself and give VS Code (Copilot) the client ID.

{
  "servers": {
    "zoom-whiteboard": {
      "oauth": {
        "clientId": "<your-client-id>"
      },
      "type": "http",
      "url": "https://mcp.zoom.us/mcp/whiteboard/streamable"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 3 Sep 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://zoom.us
Dynamic client registration	✕Not advertised A client that cannot register itself needs credentials issued out of band before it can begin the flow.
Client ID Metadata Document	✕Not advertised
PKCE	✓S256
Grant types	authorization_code, refresh_token, client_credentials, urn:ietf:params:oauth:grant-type:jwt-bearer
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Refused — credentials required

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

Contract history

No contract recorded yet — the server has not answered an anonymous connection.

Run this server? A verified owner can publish snapshots with their own credentials, and the contract history starts here, marked owner-reported.

mcpi-cli publish https://mcp.zoom.us/mcp/whiteboard/streamable

Get alerted when this contract changes

Depend on this server? Leave an email. No contract is on record here yet, so alerts can only start once one is published — and alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Own this server?

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/zoom-whiteboard/badge.svg)](https://mcpi.app/servers/zoom-whiteboard)