# Zoom (Remote)

{% hint style="warning" %}
**Early Access** — Reach out to your Natoma representative for access.
{% endhint %}

**Type:** Official

**Source Type:** Remote URL

**Source:** <https://mcp.zoom.us/mcp/zoom/streamable>

**Description:** Zoom (Remote) MCP server provides AI assistants with access to Zoom's video conferencing platform via Zoom's native remote MCP integration. It enables meeting management, recording lookups, search, and Zoom Docs operations through an admin-supplied OAuth client.

{% hint style="info" %}
Zoom does not support Dynamic Client Registration — you must provide pre-registered client credentials. PKCE is required by the MCP spec; Natoma supplies the `code_verifier` automatically, so no extra admin configuration is needed.
{% endhint %}

***

## Setup

### Admin Setup (one-time)

See Zoom's [Connect to Zoom MCP servers](https://developers.zoom.us/docs/mcp/servers/connect-to-zoom-mcp-servers/) guide for the canonical instructions. In summary:

1. Go to [marketplace.zoom.us](https://marketplace.zoom.us).
2. Click **Develop** in the top nav, then **Build App**.
3. Select **General App**.
4. Fill in basic app info (e.g. name: `Natoma MCP Integration`).
5. Under **Basic Information > OAuth Information**, add the Natoma redirect URL:

{% hint style="warning" %}
The URL must match exactly (protocol, domain, path, no trailing slash). Zoom returns error `4709` on mismatch.
{% endhint %}

```
https://api.natoma.app/mcp/server/callback
```

6. Under **Scopes**, click **Add scopes** and add the scopes from the table below. You may need to search for each one individually in Zoom's scope picker.

| Scope                                       | Required by tool(s)             |
| ------------------------------------------- | ------------------------------- |
| `meeting:read:search`                       | `search_meetings`               |
| `ai_companion:read:search`                  | `search_zoom`                   |
| `meeting:read:assets`                       | `get_meeting_assets`            |
| `cloud_recording:read:list_user_recordings` | `recordings_list`               |
| `cloud_recording:read:list_recording_files` | `recordings_list`               |
| `cloud_recording:read:content`              | `get_recording_resource`        |
| `docs:read:export`                          | `get_file_content`              |
| `docs:write:import`                         | `create_new_file_with_markdown` |

7. From the same app's **App Credentials** section, copy the **OAuth Client ID** and **Client Secret**.

In Natoma, an admin adds **Zoom (Remote)** under **Apps** and enters the **Client ID**, **Client Secret**, and the same scopes added in Zoom.

{% hint style="warning" %}
Scopes must match exactly between Zoom and Natoma. A mismatch causes tool calls to return `401` or `403` — if you see either, first verify that every scope you added in the Zoom Marketplace is also entered in Natoma's connector configuration.
{% endhint %}

### Authorize Your Connection

When prompted while creating the connection in Natoma, click **Authorize**, review the permissions in Zoom, and click **Accept and Continue**. Then click **Test Connection** to verify everything is working.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.natoma.ai/apps/zoom-remote.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.