Is this an official Zoom MCP server?

No. It is Memtro's MCP server with Memtro's Zoom connector behind it: the connector reads Zoom through its API with the credentials you connect on Dashboard → Connections, and Zoom publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Zoom?

Only when you ask, and only what it has been granted: schedule a meeting for a user on the account; change a scheduled meeting's topic, time, duration, agenda or settings; cancel a scheduled meeting and have Zoom tell its registrants. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Email, calendar and chat

Zoom MCP server

Zoom in any MCP client, through Memtro: Zoom does not publish this server. Memtro's Zoom connector reads Zoom through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Zoom users, upcoming and past meetings with participants, cloud recordings, transcripts and AI Companion summaries across the account; can also schedule a meeting for a user, change one and cancel it when you ask.

Reads

zoom_usersList active Zoom users in the account (name, email, licence type, department, last login), optionally filtered by a name or email fragment.
zoom_meetingsMeetings for one user (email, name or id) or the whole account (first 25 users): upcoming (default), scheduled, live…
zoom_meetingOne meeting by numeric id or instance UUID: topic, scheduled details, and for past meetings the actual start/end, duration and participants (name…
zoom_recordingsCloud recordings for a user or the whole account in a date window (default last 30 days, max one month per call): meeting, host, duration…
zoom_transcriptTranscript of a recorded meeting as 'Speaker: text' lines (truncated), plus the AI Companion summary when one exists.

Acts, when you ask

These change something in Zoom. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

zoom_create_meetingSchedules a Zoom meeting for one user on the account.
zoom_update_meetingChanges a scheduled Zoom meeting — topic, start, duration, timezone, agenda or settings — and leaves everything not passed as it was.
zoom_delete_meetingCancels a scheduled Zoom meeting.

Connect it

First connect Zoom on Dashboard → Connections, then add Memtro to your client once. The Zoom tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Zoom connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› Who was in yesterday's pricing review on Zoom?
› Summarise the last three customer calls Priya recorded
› Which meetings this week have a transcript?
› What did we agree with Acme in Tuesday's call?

Questions

Is this an official Zoom MCP server?: No. It is Memtro's MCP server with Memtro's Zoom connector behind it: the connector reads Zoom through its API with the credentials you connect on Dashboard → Connections, and Zoom publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Zoom?: Only when you ask, and only what it has been granted: schedule a meeting for a user on the account; change a scheduled meeting's topic, time, duration, agenda or settings; cancel a scheduled meeting and have Zoom tell its registrants. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.