> ## Documentation Index
> Fetch the complete documentation index at: https://docs.peacock.support/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Claude Desktop to connect to Zoom MCP Server

> Configure Claude Desktop to launch the Zoom MCP Server by editing the Claude config file, setting the correct absolute path, and restarting the app.

Claude Desktop discovers MCP servers through a JSON configuration file. You add an entry pointing to the Zoom MCP Server's launcher, restart Claude, and the integration is live. The whole process requires editing one file and performing one restart.

<Steps>
  <Step title="Locate the Claude Desktop config file">
    On macOS, the config file lives at:

    ```
    ~/Library/Application Support/Claude/claude_desktop_config.json
    ```

    If the file does not exist yet, create it. If it already exists, open it in any text editor.
  </Step>

  <Step title="Add the Zoom MCP server entry">
    Add the following to the `mcpServers` object. If the `mcpServers` key does not exist, add it at the top level:

    ```json theme={null}
    {
      "mcpServers": {
        "zoom": {
          "command": "node",
          "args": ["/absolute/path/to/zoommcp/launch-mcp.js"]
        }
      }
    }
    ```

    <Tip>
      To find the absolute path to your `zoommcp` directory, open a terminal, navigate to the `zoommcp` folder, and run:

      ```bash theme={null}
      pwd
      ```

      Copy the output and append `/launch-mcp.js` to form the full path. For example: `/Users/yourname/projects/zoommcp/launch-mcp.js`.
    </Tip>

    <Warning>
      You must use an absolute path in the `args` array. A relative path will not work because Claude Desktop does not resolve paths relative to your home directory or the config file location.
    </Warning>
  </Step>

  <Step title="Why launch-mcp.js instead of index.js">
    The config points to `launch-mcp.js` rather than `index.js` directly. `launch-mcp.js` is a Claude MCP-safe launcher that loads your `.env` file and the access token into the environment before starting `index.js`. This avoids shell execution issues that can occur in Claude's macOS and iCloud Drive environments, where direct shell script execution is restricted.
  </Step>

  <Step title="Restart Claude Desktop">
    Save the config file and fully quit Claude Desktop, then reopen it. Claude reads the MCP server configuration only on startup.
  </Step>

  <Step title="Verify the connection">
    After Claude Desktop restarts, it should connect to the Zoom MCP Server without showing any MCP connection errors. To confirm everything is working, ask Claude:

    > "Show me my upcoming Zoom meetings"

    Claude should respond with your meeting list pulled from Zoom.

    If something does not work, check the Claude Desktop logs for error details:

    ```
    ~/Library/Logs/Claude/mcp*.log
    ```
  </Step>
</Steps>