Zoom Revenue Accelerator
Vendor domain: zoom.com · Public company brief (ZM) · vendor page id zoom-com
A live handshake means the URL answered an MCP initialize as a server on the probe date. It is liveness and nothing more: nobody has run its tools. A tool being catalogued means a server names it, by answering tools/list, in its own source, or in the vendor's documentation. None of them has been called. A tool count of 0 means not measured, never zero tools.
Zoom Revenue Accelerator
Zoom's built-in conversation/revenue-intelligence layer that analyzes Zoom Meetings and Phone calls for deal insights, scorecards, and account activity.
1 of 1 gate unknown, not established from public sources and published as unknown.
The gate is the api_gate field on each product entry, established by hand on the last_checked date shown above. It records whether a solo operator can get API access without a contract. Money is not tracked.
3 distinct job labels, the union across 1 product, tagged 2026-08-25. A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.
- https://news.zoom.com/zoom-revenue-accelerator-mcp-connector/ (Zoom Revenue Accelerator, docs page, probed 2026-09-04)
An endpoint is where an agent connects. A docs page is where a person reads about connecting. Both are published because both are what the probe found; an agent needs the first.
No CLI found for any product of this vendor by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.
github.com/zoom tied to the vendor by rule 1, the directory already classed this repo first-party and its owner is an Organization, confidence strong
The five most recently pushed, on 2026-09-08:
| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| rtms-samples | docs or examples | RTMS sample apps | 27 | 2026-09-05 | |
| zoomapps-advancedsample-react | docs or examples | This repository contains an Advanced Zoom Apps Sample. It should serve as a starting point for you to build and test... | 64 | 2026-09-04 | |
| zoom-plugin-claude | plugin or integration | Claude plugin for planning, building, and debugging Zoom integrations across REST APIs, SDKs, webhooks, bots, and MCP... | 7 | 2026-09-03 | |
| skills | other | Skills for building with Zoom SDKs, APIs, MCP servers, and integrations across web, mobile, desktop, and server... | 74 | 2026-09-03 | feb-2026 |
| videosdk-reactnative-quickstart | docs or examples | This is a sample application that demonstrates how to use the Zoom Video SDK in a React Native application. | 10 | 2026-09-02 |
Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.
A job tag is a vendor claim: it means the vendor says the product does this, and it is not a test result. A listed tool has not been run: the catalogue says what an agent could try, not what works. 1 of 1,252 directory entries are bench tested, meaning somebody personally ran the tool on a stated date, and 0 of this vendor's 1 product are among them. There is no verdict here on whether this vendor is better than another.
Vendor pages group the directory's canonical product entries by vendor_domain. The vendor name is the product display name that matches the domain when several products share it; nothing on this page is typed by hand. Data baked 2026-09-27 by build_directory.py (phase 1).