Zoom Docs logo

Zoom Docs

Creates Zoom Docs from Markdown and retrieves existing documents or notes as Markdown over streamable HTTP.

Install Zoom Docs

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://mcp.zoom.us/mcp/zoom/streamable

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

The zoom-docs MCP server connects AI agents and developer tooling to Zoom Docs through a streamable HTTP endpoint. It supports creating new documents from Markdown and retrieving existing Zoom Docs or notes in Markdown form. Reach for it when an agent needs focused document generation or readback, rather than broader Zoom collaboration features or document lifecycle management.

Use cases

  • Create Zoom Docs from generated Markdown
  • Retrieve Zoom notes for agent analysis
  • Read existing documents into a Markdown workflow
  • Generate structured documents with developer tooling

Key features

  • Create Zoom Docs from Markdown
  • Retrieve Zoom Docs as Markdown
  • Retrieve Zoom notes as Markdown
  • Use a streamable HTTP transport
  • Focused document-generation and readback workflows

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

12/12 checks healthy over the last 66d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
Last commit4mo agoMost recent push to the default branch.

How Zoom Docs works

What zoom-docs MCP server does

The zoom-docs MCP server provides a focused interface for working with Zoom documents and notes. It exposes two core workflows: creating a new Zoom Doc from Markdown content and reading an existing Zoom Doc or note back as Markdown.

This makes the server suitable for agents that turn generated text into Zoom documentation, or that need to inspect document content as part of a larger reasoning workflow. Markdown is the interchange format described by the registry material, so callers can provide structured text when creating documents and receive a text representation when retrieving them.

The server is narrower than Zoom Workspace. It targets document operations only and does not expose the broader meeting, chat, recording, or collaboration features listed for other Zoom MCP servers.

How it works

The published entry identifies a remote streamable HTTP endpoint:

https://mcp.zoom.us/mcp/docs/streamable

An MCP client connects to that endpoint and invokes the document capabilities exposed by the service. For creation, the client supplies Markdown content for a new Zoom Doc. For retrieval, the client requests an existing Zoom Doc or note and receives its content in Markdown form.

The zoom-docs MCP server is therefore a fit for structured generation and readback flows. For example, an agent can compose meeting notes, plans, or other Markdown-based material and send it to Zoom Docs, or retrieve an existing note for summarization and further processing.

Setup and configuration

Configure an MCP client to use the registered streamable HTTP service at the Zoom Docs endpoint. The repository identifies the transport as streamable-http and lists the registry entry as io.github.zoom/zoom-docs.

Authentication and access behavior should therefore be confirmed against the client and Zoom service configuration used in the deployment.

Tools and capabilities

The documented capabilities are:

  • Create a new Zoom Doc from Markdown content.
  • Retrieve an existing Zoom Doc in Markdown form.
  • Retrieve an existing Zoom note in Markdown form.

These operations support document generation and content retrieval for AI agents and developer tools. The material does not identify additional tools by name or describe parameters beyond the Markdown input and output behavior.

Limitations and notes

The zoom-docs MCP server does not provide the broader Zoom data surfaces available through Zoom Workspace, such as meetings, Team Chat, or recordings. It also does not expose document update or delete operations. Existing content can be retrieved, but the documented interface is limited to creating new documents and reading existing documents or notes.

The repository is an MCP registry project containing metadata and remote URLs; it does not contain the server implementation.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Zoom Docs

zoom-docs is an MCP server that connects AI agents and developer tooling to Zoom Docs. Its main tools create new Zoom Docs from Markdown and retrieve existing Zoom Docs or notes as Markdown. It provides a focused document surface without broader lifecycle actions such as updating or deleting documents.

Connect your MCP client to https://mcp.zoom.us/mcp/docs/streamable using streamable HTTP. The registry identifies the service as io.github.zoom/zoom-docs.

It can create new Zoom Docs from Markdown content. The documented interface does not describe creation of other Zoom assets or provide additional input formats.

No. The documented capabilities cover creating new Zoom Docs and retrieving existing Zoom Docs or notes; update and delete operations are not exposed.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewZoom Docs AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/zoom-docs?style=directory)](https://allmcps.com/mcp/zoom-docs)
HTML Embed
<a href="https://allmcps.com/mcp/zoom-docs"><img src="https://allmcps.com/api/badge/zoom-docs?style=directory" alt="Zoom Docs on AllMCPs" /></a>