Ext Ops Panel
Open dashboard
Comparison

Zoom Phone MCP vs Zscaler Zero Trust Exchange

Zoom Phone MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). Zscaler Zero Trust Exchange is an MCP server published by zscaler. Marketplaces we read that list it: 5 (Official MCP Registry, Claude Code: claude-plugins-official, Docker MCP Catalog, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-11-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceZoom Phone MCPZscaler Zero Trust Exchange
Official MCP Registry Listed
Version: 0.1.5
Forks (GitHub): 18
Stars (GitHub): 76
Not marked · First seen
Listed
Version: 0.15.4
Downloads/month (PyPI): 1 348
Downloads/week (PyPI): 2 399
Forks (GitHub): 34
Stars (GitHub): 55
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 0.15.4
Forks (GitHub): 34
Stars (GitHub): 55
Not marked · First seen
Docker MCP Catalog Not listed Not seen in the last pass
Version: sha256:a3951ea456e1
Forks (GitHub): 34
Pulls (Docker Hub): 7 619
Stars (Docker Hub): 0
Stars (GitHub): 55
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.15.0
Forks (GitHub): 34
Stars (GitHub): 55
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Zoom Phone MCP vs Zscaler Zero Trust Exchange
FactZoom Phone MCPZscaler Zero Trust Exchange
Marketplaces that list it (differs)2 (worse)5 (better)
Stars (GitHub) (differs)76 (better)55 (worse)
Pulls (Docker Hub) (differs)No figure on Docker Hub7 619
Forks (GitHub) (differs)18 (worse)34 (better)
Last release (differs)2026-11-12 (better)2026-11-04 (worse)
Where it runs (differs)On your machine (https://github.com/Servosity/msp-skills/releases/download/zoom-phone-v0.1.5/zoom-phone-mcp.mcpb)On your machine (zscaler-mcp)
Transportstdiostdio
Tools it declares (differs)Not published302
Environment variables it asks for (differs)12, secrets among them: 510, secrets among them: 5
Parts of the bundle (differs)Not a bundle28
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/servosity/msp-skillsgithub.com/zscaler/zscaler-mcp-server
Changes in the last 7 days (differs)134
First seen (differs)2026-11-062026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Zoom Phone MCP

In its own words, on Official MCP Registry:

Zoom Phone admin API plus E911, call routing and desk phone audits across client accounts

Zscaler Zero Trust Exchange

In its own words, on Official MCP Registry:

Manage Zscaler Zero Trust Exchange via 400+ tools — ZPA, ZIA, ZDX, ZCC, ZTW, ZMS, EASM, and more.

How to run each

Zoom Phone MCP As a Claude Code plugin

Claude Code
/plugin marketplace add servosity/msp-skills
/plugin install zoom-phone@msp-skills

Requires: PRINTING_PRESS_CLIENT_PROFILE (secret), ZOOM_PHONE_ACCOUNT_ID (secret), ZOOM_PHONE_CLIENT_ID (secret), ZOOM_PHONE_CLIENT_SECRET (secret), ZOOM_PHONE_MCP_HTTP_TOKEN (secret)

Zscaler Zero Trust Exchange As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ZSCALER_CLIENT_ID=<YOUR_ZSCALER_CLIENT_ID>" --env "ZSCALER_CLIENT_SECRET=<YOUR_ZSCALER_CLIENT_SECRET>" --env "ZSCALER_CUSTOMER_ID=<YOUR_ZSCALER_CUSTOMER_ID>" --env "ZSCALER_VANITY_DOMAIN=<YOUR_ZSCALER_VANITY_DOMAIN>" --transport stdio zscaler-mcp-server -- uvx zscaler-mcp

Requires: ZSCALER_CLIENT_ID (secret), ZSCALER_CLIENT_SECRET (secret), ZSCALER_CUSTOMER_ID, ZSCALER_VANITY_DOMAIN

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of Zoom Phone MCP publish no list of tools, so we do not compare tools.

Settings each asks for

Only Zoom Phone MCP asks for

  • PRINTING_PRESS_CLIENT_PROFILE (secret)
  • ZOOM_PHONE_ACCOUNT_ID (secret)
  • ZOOM_PHONE_BASE_URL
  • ZOOM_PHONE_CLIENT_ID (secret)
  • ZOOM_PHONE_CLIENT_SECRET (secret)
  • ZOOM_PHONE_MCP_HTTP_TOKEN (secret)
  • ZOOM_PHONE_MCP_READ_ONLY
  • ZOOM_PHONE_MCP_UPLOAD_ROOT
  • ZOOM_PHONE_NO_LOCAL_DATA
  • ZOOM_PHONE_OAUTH_SCOPE
  • ZOOM_PHONE_TOKEN_URL
  • ZOOM_PHONE_USER_AGENT

Only Zscaler Zero Trust Exchange asks for

  • ZSCALER_CLIENT_ID (secret)
  • ZSCALER_CLIENT_SECRET (secret)
  • ZSCALER_CLOUD (secret)
  • ZSCALER_CUSTOMER_ID (secret)
  • ZSCALER_MCP_DISABLED_SERVICES
  • ZSCALER_MCP_DISABLED_TOOLS
  • ZSCALER_MCP_SKIP_CONFIRMATIONS
  • ZSCALER_MCP_WRITE_ENABLED
  • ZSCALER_MCP_WRITE_TOOLS
  • ZSCALER_VANITY_DOMAIN (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Zoom Phone MCP · What it can do: Zscaler Zero Trust Exchange · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built