Zoom MCP

Skill 159 of 200

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.

1 minute · 195 words · 8 sections

Install

$ npx skills add anthropics/knowledge-work-plugins --skill zoom-mcp/whiteboard

$ npx skills add anthropics/knowledge-work-plugins

» /plugin marketplace add anthropics/knowledge-work-plugins

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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 (opens in a new tab)

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 (opens in a new tab)

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 (opens in a new tab)
General routing: ../../general/SKILL.md

References

references/authentication-and-identifiers.md (opens in a new tab) - Auth behavior and Whiteboard ID mapping.
references/tools.md (opens in a new tab) - Whiteboard MCP tool catalog.

About this skill

Trigger

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.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/anthropics/knowledge-work-plugins, branch main, last pushed 23 September 2026.

Licence

Apache-2.0 — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

200 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 27 distinct layouts observed: bio-research/skills/*/SKILL.md, cowork-plugin-management/skills/*/SKILL.md, customer-support/skills/*/SKILL.md, data/skills/*/SKILL.md, design/skills/*/SKILL.md, engineering/skills/*/SKILL.md, enterprise-search/skills/*/SKILL.md, finance/skills/*/SKILL.md, human-resources/skills/*/SKILL.md, legal/skills/*/SKILL.md, marketing/skills/*/SKILL.md, operations/skills/*/SKILL.md, partner-built/apollo/skills/*/SKILL.md, partner-built/brand-voice/skills/*/SKILL.md, partner-built/common-room/skills/*/SKILL.md, partner-built/slack/skills/*/SKILL.md, partner-built/zoom-plugin/skills/*/SKILL.md, partner-built/zoom-plugin/skills/contact-center/*/SKILL.md, partner-built/zoom-plugin/skills/meeting-sdk/*/SKILL.md, partner-built/zoom-plugin/skills/meeting-sdk/web/*/SKILL.md, partner-built/zoom-plugin/skills/video-sdk/*/SKILL.md, partner-built/zoom-plugin/skills/virtual-agent/*/SKILL.md, partner-built/zoom-plugin/skills/zoom-mcp/*/SKILL.md, pdf-viewer/skills/*/SKILL.md, product-management/skills/*/SKILL.md, productivity/skills/*/SKILL.md, sales/skills/*/SKILL.md.

Issue colours

Resolved from the awesome-design-md registry — hue 39°, chroma 0.113. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Typefaces

Display: Copernicus is not available to us; set in Newsreader.

We never load a typeface at request time from a third-party origin, so a brand face we do not already self-host is substituted rather than fetched.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Removed “Zoom MCP Whiteboard”, a leading h1 that duplicated the skill title.

Spec compliance

53 editorial notes across 41 of 200 skills. They are printed in the margin of each skill rather than as errors here.

and 31 more.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Anthropic, declaring 120 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /anthropics/knowledge-work-plugins.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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 (opens in a new tab)

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 (opens in a new tab)

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 (opens in a new tab)
General routing: ../../general/SKILL.md

References

references/authentication-and-identifiers.md (opens in a new tab) - Auth behavior and Whiteboard ID mapping.
references/tools.md (opens in a new tab) - Whiteboard MCP tool catalog.

Zoom Mcp/whiteboard

Endpoints

Authentication

Required Scopes

Whiteboard ID Mapping

Available Tools

Read Workflow

Chaining

References

About this skill

Trigger

Colophon

Zoom Mcp/whiteboard

Endpoints

Authentication

Required Scopes

Whiteboard ID Mapping

Available Tools

Read Workflow

Chaining

References

Appendix 159.1–159.2

ReferencesMarkdown · 2 files

About this skill

Trigger

Colophon

Appendix 159.1–159.2

ReferencesMarkdown · 2 files