MCP server · Zoom Phone

Zoom MCP Server (Workspace)

Zoom operates a fleet of first-party hosted MCP servers at mcp.zoom.us, advertised through an MCP server card at /.well-known/mcp/server-card.json on the developer host and published to the official MCP registry (registry.modelcontextprotocol.io) from github.com/zoom/mcp-registry as io.github.zoom/*. All servers use streamable HTTP transport with server-to-server OAuth. There is NO Zoom Phone-specific MCP server: the Phone REST surface (391 operations) is not exposed as MCP tools today. mcp.zoom.us/mcp/phone/streamable returns -32602 "instance not found". Anonymous tools/list against the general Workspace server returns HTTP 401 with -32001 "Access token is required", so live tool schemas require an authenticated introspection — no tool names are published anywhere for this provider, and none are invented here.

Open endpoint → Zoom Phone provider profile

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: Zoom Phone Type: Hosted endpoint Transport: http Host: mcp.zoom.us

Endpoint

https://mcp.zoom.us/mcp/zoom/streamable

Hosted endpoint · transport http

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

# mcp client config (e.g. .mcp.json / mcp settings) { "mcpServers": { "zoom-phone": { "url": "https://mcp.zoom.us/mcp/zoom/streamable" } } }

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

# Add to claude_desktop_config.json { "mcpServers": { "zoom-phone": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.zoom.us/mcp/zoom/streamable"] } } }

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

curl -i -X POST https://mcp.zoom.us/mcp/zoom/streamable \ -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.

Work with this as data

Every MCP server here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for mcp servers

4 MCP tools reach this
  • find_mcpBrowse and filter every MCP server in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This MCP server 
curl "https://apis.io/api/v1/mcp/zoom-mcp-server-workspace"
All mcp servers 
curl "https://apis.io/api/v1/mcp?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.