$ loading_
Guides Zoom Whiteboard MCP auth, endpoints, ID mapping, and tool workflows.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "zoom-mcp/whiteboard" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/partner-built/zoom-plugin/skills/zoom-mcp/whiteboard/SKILL.md 2. Save it as ~/.claude/skills/whiteboard/SKILL.md 3. Reload skills and tell me it's ready
Based on Zoom Whiteboard MCP guidance, explain the correct flow for reading a whiteboard, including the auth method, required scopes, and which tools to call in order.
A step-by-step read workflow, such as using user OAuth with read scopes, then calling list_whiteboards and get_a_whiteboard.
Which part of this Zoom Whiteboard URL is the whiteboard_id? Please explain what the value after /wb/db/ means and what the value after /p/ means. URL: https://us05whiteboard.zoom.us/wb/db/6iktP8hJT3e5qaCuwFuAGg/p/180968285929472
It identifies the string after /wb/db/ as the whiteboard_id, and the value after /p/ as a page or subresource ID.
Tell me which Zoom Whiteboard MCP endpoint is recommended, when the SSE endpoint should be used as a fallback, and which environment variable should store the access token.
It returns the recommended Streamable HTTP URL, the SSE fallback URL, and the ZOOM_WHITEBOARD_MCP_ACCESS_TOKEN variable name.
When integrating Zoom Whiteboard MCP, developers can use it to confirm the recommended endpoint, token environment variable, and whether to prefer user OAuth or a validated S2S OAuth setup.
When a team has a whiteboard URL but is unsure which ID to pass, this skill helps distinguish the whiteboard_id from the page or subresource ID to avoid calling get_a_whiteboard with the wrong parameter.
When you need to list accessible whiteboards and then fetch details, this skill provides the tool catalog and read workflow to discover boards first and retrieve the target board next.
The documentation explains how to use Zoom's Whiteboard MCP server, including the recommended Streamable HTTP endpoint, the SSE fallback, and the preferred authentication path. It covers required Whiteboard scopes, the token environment variable, and how to extract the correct whiteboard_id from a URL. It also lists the available Whiteboard MCP tools and outlines the standard read workflow: first call list_whiteboards, then use get_a_whiteboard with the confirmed whiteboard_id.
Dedicated guidance for Zoom's Whiteboard MCP server.
| Transport | URL |
|---|---|
| Streamable HTTP (recommended) | https://mcp-us.zoom.us/mcp/whiteboard/streamable |
| SSE (fallback) | https://mcp-us.zoom.us/mcp/whiteboard/sse |
list_whiteboards
and get_a_whiteboard.tools/list, but tool
execution must be validated separately for your app and Whiteboard scopes.ZOOM_WHITEBOARD_MCP_ACCESS_TOKEN.Reference: references/authentication-and-identifiers.md
Whiteboard MCP read scopes:
whiteboard:read:list_whiteboardswhiteboard:read:whiteboardWrite-capable Whiteboard metadata advertised by the gateway:
whiteboard:write:whiteboardFor Whiteboard MCP, use the identifier from the URL segment after /wb/db/, not the numeric
segment after /p/.
Example:
https://us05whiteboard.zoom.us/wb/db/6iktP8hJT3e5qaCuwFuAGg/p/180968285929472
^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^
whiteboard_id page/subresource id
The current Whiteboard MCP tool surface is:
create_a_whiteboard_for_brainstorminglist_whiteboardscreate_a_whiteboardget_a_whiteboardcreate_a_whiteboard_by_scriptupdate_a_whiteboard_metadatacreate_a_whiteboard_for_meeting_summarycreate_a_whiteboard_for_strategy_analysisSome MCP clients namespace server tools in the UI. Treat the raw tool names above as authoritative.
Reference: references/tools.md
list_whiteboards to discover accessible whiteboards and confirm the correct whiteboard_id.get_a_whiteboard with that whiteboard_id.It provides dedicated guidance for Zoom Whiteboard MCP, covering authentication, endpoints, whiteboard ID mapping, and tool workflows such as list_whiteboards and get_a_whiteboard. It is intended for Whiteboard MCP specifically rather than general Zoom MCP questions.
The docs state that user OAuth with Whiteboard read scopes is the verified working path. S2S OAuth can reach the gateway and complete tools/list, but tool execution still needs to be validated for your app and scopes.
You should use the identifier after /wb/db/ in the whiteboard URL, not the numeric segment after /p/. The documentation clearly distinguishes the whiteboard_id from the page or subresource ID.
Identify, categorize, and prioritize technical debt for smarter refactoring decisions.
Research contacts with Common Room data to assess background and lead warmth.
Draft and adapt marketing content with channel-specific formatting and SEO suggestions.
Quickly isolate and debug failing Zoom integrations across auth, webhooks, SDK, and media.
Identify, evaluate, and mitigate risks across projects, processes, or vendors.
Create stakeholder updates tailored to audience, cadence, and communication goals.
Plan and troubleshoot MCP access to Zoom meetings, recordings, assets, and transcripts.
Collaboratively draw and annotate Excalidraw whiteboards with AI in real time.
Get shared Zoom platform guidance for auth, scopes, app models, and routing.
Decide when Zoom MCP fits and create a safe Claude setup plan.
Manage Zoom meetings, recordings, users, webinars, and reports via API.
Design Zoom MCP workflows for Claude and split MCP versus API responsibilities.