How do I install the Zoom Mcp/whiteboard skill?

Run npx skillmds@latest add aibot88/zoom-mcp-whiteboard in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Zoom Mcp/whiteboard safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Zoom Mcp/whiteboard?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Zoom Mcp/whiteboard free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Zoom Mcp/whiteboard?

aibot88 (@aibot88) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Zoom Mcp/whiteboard by aibot88 — Agent Skill

Name: Zoom Mcp/whiteboard
Rating: 4.5 (4 reviews)
Author: aibot88

Zoom Mcp/whiteboard

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.

aibot88 Updated Sep 9, 2026 3 repo stars

File contents

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

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:

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

Read Workflow

Use a user OAuth token with the Whiteboard read scopes.
Call list_whiteboards to discover accessible whiteboards and confirm the correct whiteboard_id.
Call get_a_whiteboard with that 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.

---name: zoom-mcp-whiteboarddescription: 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.---# Zoom MCP WhiteboardDedicated 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 ScopesWhiteboard MCP read scopes:- `whiteboard:read:list_whiteboards`- `whiteboard:read:whiteboard`Write-capable Whiteboard metadata advertised by the gateway:- `whiteboard:write:whiteboard`## Whiteboard ID MappingFor Whiteboard MCP, use the identifier from the URL segment after `/wb/db/`, not the numericsegment after `/p/`.Example:```texthttps://us05whiteboard.zoom.us/wb/db/6iktP8hJT3e5qaCuwFuAGg/p/180968285929472 ^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^ whiteboard_id page/subresource id```## Available ToolsThe 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 asauthoritative.Reference: [references/tools.md](references/tools.md)## Read Workflow1. 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.

Frequently asked questions