Knowledge-work-plugins zoom-mcp/whiteboard
install
source · Clone the upstream repo
git clone https://github.com/anthropics/knowledge-work-plugins
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/anthropics/knowledge-work-plugins "$T" && mkdir -p ~/.claude/skills && cp -r "$T/partner-built/zoom-plugin/skills/zoom-mcp/whiteboard" ~/.claude/skills/anthropics-knowledge-work-plugins-zoom-mcp-whiteboard && rm -rf "$T"
manifest:
partner-built/zoom-plugin/skills/zoom-mcp/whiteboard/SKILL.mdsource content
Zoom MCP Whiteboard
Dedicated guidance for Zoom's Whiteboard MCP server.
Endpoints
| Transport | URL |
|---|---|
| Streamable HTTP (recommended) | |
| SSE (fallback) | |
Authentication
- User OAuth with Whiteboard scopes is the verified working path for
andlist_whiteboards
.get_a_whiteboard - S2S OAuth can reach the Whiteboard MCP gateway and complete
, but tool execution must be validated separately for your app and Whiteboard scopes.tools/list - Practical rule: start with user OAuth for Whiteboard MCP unless you have already proven your S2S app can mint and execute with the required Whiteboard scopes.
- The bundled connector expects the token in
.ZOOM_WHITEBOARD_MCP_ACCESS_TOKEN
Reference: references/authentication-and-identifiers.md
Required Scopes
Whiteboard MCP read scopes:
whiteboard:read:list_whiteboardswhiteboard:read:whiteboard
Write-capable Whiteboard metadata advertised by the gateway:
whiteboard:write:whiteboard
Whiteboard ID Mapping
For 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
Available Tools
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_analysis
Some MCP clients namespace server tools in the UI. Treat the raw tool names above as authoritative.
Reference: references/tools.md
Read Workflow
- Use a user OAuth token with the Whiteboard read scopes.
- Call
to discover accessible whiteboards and confirm the correctlist_whiteboards
.whiteboard_id - Call
with thatget_a_whiteboard
.whiteboard_id
Chaining
- Parent MCP skill: ../SKILL.md
- OAuth guidance: ../concepts/oauth-setup.md
- General routing: ../../general/SKILL.md
References
- references/authentication-and-identifiers.md - Auth behavior and Whiteboard ID mapping.
- references/tools.md - Whiteboard MCP tool catalog.