
Zoom Revenue Accelerator
io.github.zoomPublished by GitHub account zoomv1.0.1Updated Oct 25, 2026
Zoom Revenue Accelerator server for sales insights, conversations, and deal intelligence.
Overview
Zoom's remote MCP server for sales insights, customer conversations and deal intelligence from Zoom Revenue Accelerator.
- What you can do
- Review customer interactions and revenue-related conversations and activity, per the registry description and README, which describe a focused surface for sales insights, conversations and deal intelligence. The manifest lists no individual tools, so specific operations are not documented here. Intended for preparing follow-up notes and finding context from revenue-related conversations.
- When to use it
- Useful for sales teams that want an assistant to help review customer interactions, prepare follow-up notes, or find context from revenue-related conversations and activity stored in Zoom Revenue Accelerator.
- Requirements
- A remote streamable HTTP endpoint at mcp.zoom.us; no local package or runtime. OAuth authentication is required, so a Zoom account with access to Revenue Accelerator data is needed, plus network access.
Installation
In SourceWeft
- Open Zoom Revenue Accelerator in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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-revenue-accelerator/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"zoom-revenue-accelerator": {
"type": "http",
"url": "https://mcp.zoom.us/mcp/revenue_accelerator/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
- 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.2for Workspace, Docs, and Whiteboard;1.0.1for Revenue Accelerator and Team Chat;1.0.0for 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
versionfield before publishing an update. -
Change into the corresponding server directory.
-
Refresh or establish a login session if needed:
-
Publish the entry:
-
Verify the published record using the registry API URLs listed above.
Example:
To publish the two newer entries:
To publish the Meetings and Tasks entries:
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
0Version history
1- v1.0.1LatestSep 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