zoom-mcp/whiteboard — Claude Code skill: features and setup
This Claude Code skill guides agents through Zoom Whiteboard tasks over MCP. It covers requests to find boards, retrieve their contents, and handle authentication or board IDs.
MIT ★ 36,654 updated 2026-10-24
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install zoom-plugin@knowledge-work-pluginsWhat zoom-mcp/whiteboard does
The skill explains the Zoom Whiteboard MCP connection, its endpoints, OAuth setup, and available tools. list_whiteboards finds accessible boards, while get_a_whiteboard retrieves one; other tools can create boards or change their metadata.
Reading requires a user OAuth token with whiteboard:read:list_whiteboards and whiteboard:read:whiteboard scopes. The connector reads it from ZOOM_WHITEBOARD_MCP_ACCESS_TOKEN. First call list_whiteboards, then pass the returned whiteboard_id to get_a_whiteboard. Use the ID after /wb/db/ in a board URL, not the numeric value after /p/.
What it helps with
- find Zoom Whiteboards available to the user
- retrieve a board by its identifier
- distinguish the board ID from its page ID
- configure OAuth access for Whiteboard MCP
Example prompts for the agent
- List the Zoom Whiteboards I can access.
- Retrieve the contents of the board with the ID from its link.
- Explain the OAuth scopes needed for Zoom Whiteboard MCP.
How to install zoom-mcp/whiteboard
1Plugin marketplace
/plugin marketplace add anthropics/knowledge-work-plugins/plugin install zoom-plugin@knowledge-work-pluginsThis installs the whole zoom-plugin plugin with all its skills
2Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill zoom-mcp/whiteboard -a claude-code3Manually: put the files in place
~/.claude/skills/whiteboard/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/whiteboard/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill zoom-mcp/whiteboard -a codex2Manually: put the files in place
.agents/skills/whiteboard/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill zoom-mcp/whiteboard -a cursor2Manually: put the files in place
.cursor/skills/whiteboard/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthropics/knowledge-work-plugins partner-built/zoom-plugin/skills/zoom-mcp/whiteboard2Manually: put the files in place
.github/skills/whiteboard/SKILL.md1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill zoom-mcp/whiteboard -a gemini-cli2Platform CLI
gemini skills install https://github.com/anthropics/knowledge-work-plugins --path partner-built/zoom-plugin/skills/zoom-mcp/whiteboardManually: put the files in place
.devin/skills/whiteboard/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about zoom-mcp/whiteboard
How do I install zoom-mcp/whiteboard in Claude Code?
Run these commands in order: /plugin marketplace add anthropics/knowledge-work-plugins, then /plugin install zoom-plugin@knowledge-work-plugins.
What does zoom-mcp/whiteboard do?
It guides an agent through Zoom Whiteboard MCP authentication, board discovery, and retrieval. It also documents tools for creating boards and editing metadata.
What does zoom-mcp/whiteboard need to read boards?
Use a user OAuth token with the whiteboard:read:list_whiteboards and whiteboard:read:whiteboard scopes. The connector expects it in ZOOM_WHITEBOARD_MCP_ACCESS_TOKEN.
Source text
SKILL.md · MIT
---
name: zoom-mcp/whiteboard
description: |
Guidance for the bundled Zoom Whiteboard MCP connector. Use for Whiteboard MCP auth,
endpoints, ID mapping, and tool workflows such as list_whiteboards and get_a_whiteboard.
Prefer this skill when the request is specifically about Whiteboard MCP rather than general Zoom MCP.
user-invocable: false
triggers:
- "whiteboard mcp"
- "zoom whiteboard mcp"
- "zoom mcp whiteboard"
- "zoom whiteboard tools"
- "list zoom whiteboards"
- "get zoom whiteboard"
- "zoom whiteboard id"
- "zoom wb/db"
---
# Zoom MCP Whiteboard
Dedicated guidance for Zoom's Whiteboard MCP server.
## Endpoints
| Transport | URL |
|-----------|-----|
| Streamable HTTP (recommended) | `https://mcp-us.zoom.us/mcp/whiteboard/streamable` |
| SSE (fallback) | `https://mcp-us.zoom.us/mcp/whiteboard/sse` |
## Authentication
- **User OAuth with Whiteboard scopes** is the verified working path for `list_whiteboards`
and `get_a_whiteboard`.
- **S2S OAuth** can reach the Whiteboard MCP gateway and complete `tools/list`, but tool
execution must be validated separately for your app and Whiteboard scopes.
- 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](references/authentication-and-identifiers.md)
## Required Scopes
Whiteboard MCP read scopes:
- `whiteboard:read:list_whiteboards`
- `whiteboard: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:
```text
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_brainstorming`
- `list_whiteboards`
- `create_a_whiteboard`
- `get_a_whiteboard`
- `create_a_whiteboard_by_script`
- `update_a_whiteboard_metadata`
- `create_a_whiteboard_for_meeting_summary`
- `create_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](references/tools.md)
## Read Workflow
1. Use a user OAuth token with the Whiteboard read scopes.
2. Call `list_whiteboards` to discover accessible whiteboards and confirm the correct `whiteboard_id`.
3. Call `get_a_whiteboard` with that `whiteboard_id`.
## Chaining
- Parent MCP skill: [../SKILL.md](../SKILL.md)
- OAuth guidance: [../concepts/oauth-setup.md](../concepts/oauth-setup.md)
- General routing: [../../general/SKILL.md](../../general/SKILL.md)
## References
- [references/authentication-and-identifiers.md](references/authentication-and-identifiers.md) - Auth behavior and Whiteboard ID mapping.
- [references/tools.md](references/tools.md) - Whiteboard MCP tool catalog.
© Zoom · MIT · anthropics/knowledge-work-plugins