Zoom Whiteboard

io.github.zoomPublished by GitHub account zoomv1.0.2Updated Oct 24, 2026

Zoom Whiteboard server for creating boards and diagrams and locating existing boards.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowMedia & Design

Overview

AI-generated overview

Zoom Whiteboard is a remote MCP server that lets an assistant create editable whiteboards and diagrams from prompts and find existing boards in a Zoom account.

What you can do
Create new editable whiteboards and diagrams from natural-language prompts, including simple flowcharts and more technical diagram types. Locate existing boards in the authenticated user's Zoom account. Access is limited to boards the signed-in user can already see.
When to use it
Useful for workshop planning, visual collaboration, and diagram generation where you want an assistant to turn a description into a Zoom whiteboard or to find a board you already have.
Requirements
A remote MCP endpoint hosted by Zoom, reached over streamable HTTP. Sign-in with Zoom OAuth is required; no API keys or environment variables are declared.
Before you install
The server creates new boards in your Zoom account, so review generated content before sharing. It only exposes boards the authenticated user can access, but anything it creates inherits that account's sharing settings. OAuth grants the server access to your Zoom account.

Installation

In SourceWeft

  1. Open Zoom Whiteboard in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.zoom%2Fzoom-whiteboard/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "zoom-whiteboard": {
      "type": "http",
      "url": "https://mcp.zoom.us/mcp/whiteboard/streamable"
    }
  }
}

README

MCP Registry

This project provides Zoom's registry of MCP servers at registry.modelcontextprotocol.io. It contains the published registry metadata for remote MCP servers. It does not contain the server implementations themselves.

Registry Servers

io.github.zoom/zoom-workspace

Zoom Workspace exposes Zoom meetings, Team Chat, and Zoom Docs to MCP clients. It supports natural-language retrieval of AI-generated summaries, transcripts, recordings, shared documents, and meeting assets, along with recording-specific resources such as playback links and next steps. It can retrieve Zoom Docs content, list cloud recordings, and create follow-up Zoom Docs from Markdown. This server is intended for workflows such as locating where a topic was discussed, generating agendas, capturing notes, identifying action items, and creating follow-up documents from existing Zoom collaboration data.

io.github.zoom/zoom-docs

Zoom Docs provides a focused MCP surface for working with Zoom documents and notes. It currently supports creating new Zoom Docs from Markdown content and retrieving existing Zoom Docs or notes in Markdown form. The server is designed for structured document generation and readback flows used by AI agents and developer tooling, without exposing broader document lifecycle operations such as update or delete.

io.github.zoom/zoom-whiteboard

Zoom Whiteboard provides MCP tools for creating new editable whiteboards and diagrams from prompts and for locating existing boards in a user's account. It is intended for workshop planning, visual collaboration, and diagram-generation use cases, including simple flowcharts and more technical diagram types. The server only exposes boards the authenticated user can access.

io.github.zoom/zoom-revenue-accelerator

Zoom Revenue Accelerator provides a focused MCP surface for sales insights, conversations, and deal intelligence. It is intended for workflows such as reviewing customer interactions, preparing follow-up notes, and finding context from revenue-related conversations and activity.

io.github.zoom/zoom-team-chat

Zoom Chat provides a focused MCP surface for chat channels, messages, contacts, files, and collaboration context. It is intended for workflows such as locating chat history, preparing summaries, and generating follow-ups from chat activity. The registry name remains io.github.zoom/zoom-team-chat for continuity with the existing published entry.

io.github.zoom/zoom-meetings

Zoom Meetings provides a focused MCP surface for meeting search, recordings, transcripts, summaries, and meeting assets. It is intended for workflows such as locating meeting context, reviewing recordings, and preparing follow-ups from meeting content.

io.github.zoom/zoom-tasks

Zoom Tasks provides a focused MCP surface for creating, updating, assigning, and synchronizing tasks. It is intended for workflows such as managing task details, reviewing comments and steps, and coordinating work across collaborators.

Registry Notes

  • Namespace: io.github.zoom/*
  • Transport: streamable-http
  • Current metadata versions in this repository: 1.0.2 for Workspace, Docs, and Whiteboard; 1.0.1 for Revenue Accelerator and Team Chat; 1.0.0 for Meetings and Tasks

Registry API Records

  • Search listing: https://registry.modelcontextprotocol.io/v0.1/servers?search=zoom&limit=100
  • Workspace latest version: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-workspace/versions/latest
  • Docs latest version: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-docs/versions/latest
  • Whiteboard latest version: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-whiteboard/versions/latest
  • Revenue Accelerator latest version: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-revenue-accelerator/versions/latest
  • Team Chat latest version: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-team-chat/versions/latest
  • Meetings latest version: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-meetings/versions/latest
  • Tasks latest version: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-tasks/versions/latest

Publishing Workflow

The MCP Registry entries in this repository are published with mcp-publisher.

For the Zoom-specific step-by-step publishing history and lessons learned, see RUNBOOK.md.

Prerequisites

  • Install mcp-publisher
  • Authenticate with GitHub using an account that has access to the target GitHub organization
  • Ensure the GitHub organization membership associated with the namespace is public

Publish a New Version

  1. Update the relevant server.json.

  2. Increment the version field before publishing an update.

  3. Change into the corresponding server directory.

  4. Refresh or establish a login session if needed:

    bash
    mcp-publisher login github

  5. Publish the entry:

    bash
    mcp-publisher publish

  6. Verify the published record using the registry API URLs listed above.

Example:

bash
cd zoom-workspacemcp-publisher publish

To publish the two newer entries:

bash
cd ~/temp/mcp-registry-publish/zoom-revenue-acceleratormcp-publisher publish
cd ~/temp/mcp-registry-publish/zoom-team-chatmcp-publisher publish

To publish the Meetings and Tasks entries:

bash
cd ~/temp/mcp-registry-publish/zoom-meetingsmcp-publisher publish
cd ~/temp/mcp-registry-publish/zoom-tasksmcp-publisher publish

Maintenance

Published entries can be updated by modifying the corresponding server.json, incrementing the version, and republishing from that server's directory with mcp-publisher publish.

Source: README.md at commit 25347a5

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts