> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/ai-agent-access/connections-and-integrations/agent-connections/zoom.md).

# Zoom

Connect your company's Zoom account to Cakewalk's MCP Gateway. Every agent tool call against Zoom passes through the gateway and is evaluated against your Policies.

## Requirements

* Zoom account owner, account admin, or the Zoom for developers role.
* **Smart Recording** enabled. Admin > Account Management > Account Settings > AI Companion > **Smart Recording**.
* **Meeting Summary** enabled. Admin > Account Management > Account Settings > AI Companion > **Meeting Summary**.

These two account features power semantic meeting search and recording content retrieval. They are separate from OAuth scopes and must be on for the tools to return useful results.

## Required Scopes

OAuth scopes the app must request:

```
meeting:read:search
meeting:read:assets
ai_companion:read:search
cloud_recording:read:list_user_recordings
cloud_recording:read:content
docs:write:import
docs:read:export
```

## Step 1: Create a Zoom OAuth App

1. Open the Zoom App Marketplace at <https://marketplace.zoom.us>.
2. Click **Develop** > **Build App**.
3. Select **General app** and click **Create**.

You land on the app's Basic Info page.

## Step 2: Configure the Redirect URL

1. On Basic Info, scroll to the **OAuth Information** section.
2. In **OAuth redirect URL**, paste this URL:

```
https://mcp-gateway.getcakewalk.io/api/v1/Auth/Callback
```

3. Add the same URL to **OAuth allow lists**.
4. Save.

## Step 3: Add the Required Scopes

1. Open the **Scopes** page from the left sidebar.
2. Select **Add Scopes**.
3. Pick the Zoom product, check every scope listed in [Required Scopes](#required-scopes) above, then select **Done**.
4. In **Scope Description**, state that the scopes are needed for agent access through Cakewalk.

## Step 4: Paste Credentials Into Cakewalk

1. Back on Basic Info, scroll to the **App Credentials** section.
2. Copy the development **client ID** and **client secret**. Production credentials are only needed if you publish the app on the Zoom Marketplace.
3. Open <https://app.getcakewalk.io>.
4. Go to All Connections.
5. Find Zoom.
6. Click Edit credentials.
7. Paste the Client ID and Client Secret.
8. Save.

## Verifying It Works

The Zoom Connection card flips to Active on All Connections. From an agent platform connected to Cakewalk, ask the agent to list your recent Zoom meetings. If Zoom returns results, the Connection is live.

## Troubleshooting

* Invalid redirect URI on consent: confirm both **OAuth redirect URL** and **OAuth allow lists** contain `https://mcp-gateway.getcakewalk.io/api/v1/Auth/Callback`.
* Empty search results despite valid auth: confirm **Smart Recording** and **Meeting Summary** are on under Account Settings > AI Companion. These account features are separate from OAuth scopes.

## Learn More

* [Create an OAuth app](https://developers.zoom.us/docs/integrations/create/)
* [Zoom MCP server reference](https://github.com/zoom/skills/blob/main/skills/zoom-mcp/SKILL.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://www.cakewalk.security/docs/ai-agent-access/connections-and-integrations/agent-connections/zoom.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.