# zoom-docs [Official] [Health: Active]

**Category:** 🧠 Knowledge & Memory  
**Repository:** https://github.com/zoom/mcp-registry  
**GitHub Stars:** 3  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/zoom-docs

## Description
Zoom Docs server for creating and retrieving Zoom documents and notes in Markdown.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "zoom-docs": {
    "url": "https://mcp.zoom.us/mcp/zoom/streamable"
  }
}
```

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/zoom-docs/readme_