zoom-revenue-accelerator-mcp

zoom-revenue-accelerator-mcp is an MCP server for Claude Code from zoom/zoom-plugin. Its token cost is not measured, scanned A, original, MIT.

A remote MCP server configuration for Zoom Revenue Accelerator, using Zoom's service URL and an access token. MCP is a way for an agent to connect to external tools and services.

In plain words
What is it for?
Use it when an agent needs to connect to Zoom Revenue Accelerator through the configured remote MCP endpoint.
Why use it?
It gives the agent the connection details needed to use the configured Zoom service instead of setting them up manually.

MCP server for Claude Code ✓ vendor

Written for Claude Code: shipped in a Claude Code plugin. Also seen: listed in a Claude config.

Part of the zoom-plugin plugin — 47 skills, 7 MCP servers shipped together

One of 7 entries in .mcp.json upstream. Installing this one merges just its entry into your config; the other 6 are separate, each on its own page.

Good fit Use it when an agent needs to connect to Zoom Revenue Accelerator through the configured remote MCP endpoint.

Compare 6 mcp servers from other repositories ↓
Install with agentmods
npx agentmods add mcp/zoom/zoom-plugin/zoom-revenue-accelerator-mcp
About the project

Zoom Plugin is a Claude plugin that helps plan, build, and debug Zoom integrations across APIs, SDKs, webhooks, bots, and MCP connections. It is for developers creating Zoom applications, with catalogue entries providing guidance, workflows, and MCP connectors for selecting and implementing the relevant Zoom products.

zoom/zoom-plugin · 7 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/zoom/zoom-plugin

Made for: Claude Code.

Or install zoom-plugin, the plugin that ships this one along with the rest of its 47 skills, 7 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for zoom-revenue-accelerator-mcp

README.md
[![agentmods](https://agentmods.dev/badge/mcp/zoom/zoom-plugin/zoom-revenue-accelerator-mcp/github.svg)](https://agentmods.dev/mcp/zoom/zoom-plugin/zoom-revenue-accelerator-mcp)
Your own site
<a href="https://agentmods.dev/mcp/zoom/zoom-plugin/zoom-revenue-accelerator-mcp"><img src="https://agentmods.dev/badge/mcp/zoom/zoom-plugin/zoom-revenue-accelerator-mcp/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for zoom-revenue-accelerator-mcp

Your own site · 80×15
<a href="https://agentmods.dev/mcp/zoom/zoom-plugin/zoom-revenue-accelerator-mcp"><img src="https://agentmods.dev/badge/mcp/zoom/zoom-plugin/zoom-revenue-accelerator-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

zoom-revenue-accelerator-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.mcp.json · 9 lines

What it actually says

{
  "zoom-revenue-accelerator-mcp": {
    "type": "http",
    "url": "https://mcp.zoom.us/mcp/revenue_accelerator/streamable",
    "headers": {
      "Authorization": "Bearer ${ZOOM_REVENUE_ACCELERATOR_MCP_ACCESS_TOKEN}"
    }
  }
}
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 9 lines scan A cbee5a395ed7

Subscribe to this mod's changes

zoom-revenue-accelerator-mcp is an MCP server published in the GitHub repository zoom/zoom-plugin (7 stars, last pushed 7d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.