AutoGineer
Generated banner for Zoom MCP Whiteboard
Generated logo for Zoom MCP Whiteboard

Zoom MCP Whiteboard

AnthropicOfficialCreated by ZoomDistributed by Anthropic

  • Skill
  • Tool integration
  • Automation and integrations
  • MIT
  • No issues found
Download ZIP

From the author

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 description by Zoom

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides essential documentation for the Zoom Whiteboard MCP server, covering authentication requirements, endpoint configuration, and correct identifier mapping. It details the available tool surface for managing whiteboards programmatically, including listing, retrieving, and creating whiteboards for various use cases like brainstorming or strategy analysis.

What it does

  • Defines authentication requirements using User OAuth and S2S OAuth scopes.
  • Provides endpoint URLs for streamable and SSE transport methods.
  • Explains the correct method for mapping Whiteboard IDs from URL segments.
  • Catalogs available MCP tools for whiteboard creation, retrieval, and metadata updates.
  • Outlines the standard read workflow for discovering and accessing whiteboards.

When to use it

  • When configuring the Zoom Whiteboard MCP connector for an AI agent.
  • When troubleshooting authentication or scope issues with Whiteboard MCP.
  • When needing to identify the correct whiteboard ID from a browser URL.
  • When implementing workflows to list or retrieve whiteboards via MCP tools.

Advantages

  • Provides specific guidance for Whiteboard MCP distinct from general Zoom MCP.
  • Clarifies the distinction between whiteboard IDs and subresource page IDs.
  • Offers clear instructions on required OAuth scopes for read and write operations.

Usage examples

“How do I list my Zoom whiteboards using MCP?”
The agent will guide you to use the list_whiteboards tool with a user OAuth token containing the whiteboard:read:list_whiteboards scope.
“What is the correct whiteboard ID for https://us05whiteboard.zoom.us/wb/db/6iktP8hJT3e5qaCuwFuAGg/p/180968285929472?”
The agent will identify 6iktP8hJT3e5qaCuwFuAGg as the correct whiteboard_id, noting that the /p/ segment should be ignored.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/anthropics/zoom-mcp-whiteboard/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip zoom-mcp-whiteboard.zip -d .agents/skills

Documentation by Zoom

Zoom MCP Whiteboard

Dedicated guidance for Zoom's Whiteboard MCP server.

Endpoints

TransportURL
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

  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

  • OAuth guidance: ../concepts/oauth-setup.md

  • General routing: ../../general/SKILL.md

References

Files

references/authentication-and-identifiers.md

Authentication and Identifiers — Whiteboard MCP

Guidance for https://mcp-us.zoom.us/mcp/whiteboard/streamable and https://mcp-us.zoom.us/mcp/whiteboard/sse.

Authentication Behavior

User OAuth

User OAuth with Whiteboard scopes was the verified working path for:

  • list_whiteboards

  • get_a_whiteboard

The required user OAuth scope set includes:

  • whiteboard:read:list_whiteboards

  • whiteboard:read:whiteboard

Server-to-Server OAuth

S2S OAuth can reach the Whiteboard MCP gateway and complete protocol discovery through tools/list, but Whiteboard read-tool execution must be validated separately for your app.

One possible runtime error shape when S2S lacks the expected scopes is:

Invalid access token, does not contain scopes:[whiteboard:read:admin,whiteboard:read]

Protected-resource metadata for Whiteboard MCP advertised these supported scopes:

  • whiteboard:write:whiteboard

  • whiteboard:read:list_whiteboards

  • whiteboard:read:whiteboard

Practical guidance:

  • Use user OAuth first for Whiteboard MCP.

  • Only rely on S2S after you have confirmed the app can mint and execute with the required Whiteboard scopes.

Whiteboard ID Mapping

The MCP-facing whiteboard_id matches the URL segment after /wb/db/.

Example:

https://us05whiteboard.zoom.us/wb/db/6iktP8hJT3e5qaCuwFuAGg/p/180968285929472

  • Correct MCP whiteboard_id: 6iktP8hJT3e5qaCuwFuAGg

  • The numeric /p/... segment is not the Whiteboard MCP identifier.

Response Shape

get_a_whiteboard returned a list-style payload containing the matched whiteboard rather than an obviously single-object payload. Parse the response shape you actually receive from the live server instead of assuming the tool name implies a unique-object response.

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Claude Code frontmatter, Needs an MCP server

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Zoom
Publisher
Anthropic (Official)
Distributed by
Anthropic
Source
anthropics/knowledge-work-plugins · partner-built/zoom-plugin/skills/zoom-mcp/whiteboard · commit e050c2e
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from partner-built/zoom-plugin/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Zoom or Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download zoom-mcp-whiteboard.zip