Productivity · Remote MCP server
Zoom Revenue Accelerator
Zoom Revenue Accelerator server for sales insights, conversations, and deal intelligence.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.zoom/zoom-revenue-accelerator- Version
- 1.0.1
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-07-08
- Updated
- 2026-07-08
- Publisher
- zoom (GitHub) · 7 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/zoom) · how
- Listed under
- Zoom MCP servers
- Repository
- github.com/zoom/mcp-registry
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.zoom.us/mcp/revenue_accelerator/streamable | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Zoom Revenue Accelerator
Zoom Revenue Accelerator is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.zoom.us/mcp/revenue_accelerator/streamable, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from zoom (GitHub)
| Server | Runs |
|---|---|
| Zoom DocsZoom Docs server for creating and retrieving Zoom documents and notes in Markdown. | Remote · HTTPLive check: sign-in required |
| Zoom MeetingsZoom Meetings server for meeting search, recordings, transcripts, summaries, and meeting assets. | Remote · HTTPLive check: sign-in required |
| Zoom TasksZoom Tasks server for creating, updating, assigning, and synchronizing task workflows. | Remote · HTTPLive check: sign-in required |
| Zoom Team ChatZoom Chat server for channels, messages, contacts, files, and chat collaboration. | Remote · HTTPLive check: sign-in required |
| Zoom WhiteboardZoom Whiteboard server for creating boards and diagrams and locating existing boards. | Remote · HTTPLive check: sign-in required |
| Zoom WorkspaceZoom workspace server for meetings, chat, docs, recordings, and AI-generated collaboration content. | Remote · HTTPLive check: sign-in required |
More productivity servers
| Server | Runs |
|---|---|
| ZevariControlled LinkedIn and GTM MCP server with review-gated prospecting and outreach workflows. | Remote · HTTPLive check: sign-in required |
| ZoogentAI agent orchestrator with Architect AI. Multi-team, web dashboard, 35+ MCP tools. | Local · stdio |
| ZoteusZotero MCP server for Claude and ChatGPT: search, citations, safe writes, PDF passages and pages. | Remote & Local · HTTP, stdioLive check: sign-in required |