How do I install Zoom Revenue Accelerator?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Zoom Revenue Accelerator need an API key?

No required environment variable is listed on this record.

What transport does Zoom Revenue Accelerator use?

Zoom Revenue Accelerator is reached over HTTP.

When was Zoom Revenue Accelerator last checked?

Last checked 2026-11-10. Zoom Revenue Accelerator server for sales insights, conversations, and deal intelligence.

Zoom Revenue Accelerator MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

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

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http io.github.zoom-zoom-revenue-accelerator https://mcp.zoom.us/mcp/revenue_accelerator/streamable

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.zoom-zoom-revenue-accelerator": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://mcp.zoom.us/mcp/revenue_accelerator/streamable"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 1.0.1
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

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`

Registry metadata: zoom-workspace/server.json
Remote URL: https://mcp.zoom.us/mcp/zoom/streamable

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`

Registry metadata: zoom-docs/server.json
Remote URL: https://mcp.zoom.us/mcp/docs/streamable

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`

Registry metadata: zoom-whiteboard/server.json
Remote URL: https://mcp.zoom.us/mcp/whiteboard/streamable

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`

Registry metadata: zoom-revenue-accelerator/server.json
Remote URL: https://mcp.zoom.us/mcp/revenue_accelerator/streamable

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`

Registry metadata: zoom-team-chat/server.json
Remote URL: https://mcp.zoom.us/mcp/chat/streamable

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`

Registry metadata: zoom-meetings/server.json
Remote URL: https://mcp.zoom.us/mcp/meeting/streamable

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`

Registry metadata: zoom-tasks/server.json
Remote URL: https://mcp.zoom.us/mcp/tasks/streamable

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

Update the relevant server.json.
Increment the version field before publishing an update.
Change into the corresponding server directory.
Refresh or establish a login session if needed:
```
mcp-publisher login github
```
Publish the entry:
```
mcp-publisher publish
```
Verify the published record using the registry API URLs listed above.

Example:

cd zoom-workspace
mcp-publisher publish

To publish the two newer entries:

cd ~/temp/mcp-registry-publish/zoom-revenue-accelerator
mcp-publisher publish

cd ~/temp/mcp-registry-publish/zoom-team-chat
mcp-publisher publish

To publish the Meetings and Tasks entries:

cd ~/temp/mcp-registry-publish/zoom-meetings
mcp-publisher publish

cd ~/temp/mcp-registry-publish/zoom-tasks
mcp-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.

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Zoom Revenue Accelerator?

Does Zoom Revenue Accelerator need an API key?

What transport does Zoom Revenue Accelerator use?

When was Zoom Revenue Accelerator last checked?

Documentation

MCP Registry

Registry Servers

io.github.zoom/zoom-workspace

io.github.zoom/zoom-docs

io.github.zoom/zoom-whiteboard

io.github.zoom/zoom-revenue-accelerator

io.github.zoom/zoom-team-chat

io.github.zoom/zoom-meetings

io.github.zoom/zoom-tasks

Registry Notes

Registry API Records

Publishing Workflow

Prerequisites

Publish a New Version

Maintenance

`io.github.zoom/zoom-workspace`

`io.github.zoom/zoom-docs`

`io.github.zoom/zoom-whiteboard`

`io.github.zoom/zoom-revenue-accelerator`

`io.github.zoom/zoom-team-chat`

`io.github.zoom/zoom-meetings`

`io.github.zoom/zoom-tasks`