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

# Connect Reap MCP To OpenClaw

> Add Reap to OpenClaw as a streamable HTTP MCP server with OAuth, so your OpenClaw agent can clip, caption, reframe, dub, and publish video.

> **For AI agents:** a documentation index is at [/llms.txt](/llms.txt). Every page is also available as markdown, just append `.md` to the URL.

## Overview

OpenClaw manages MCP servers through its `openclaw mcp` commands and stores them in `~/.openclaw/openclaw.json`. You add Reap as a streamable HTTP server with OAuth, sign in, and pick the workspace OpenClaw is allowed to use.

## Before You Start

* Your Reap workspace must be on a paid plan with API access enabled.
* Install OpenClaw and have your gateway running.
* You need access to the Reap workspace you want to connect.

## Reap MCP Server URL

```text theme={"system"}
https://mcp.reap.video/mcp
```

## Add Reap To OpenClaw

<Steps>
  <Step title="Add the server">
    ```bash theme={"system"}
    openclaw mcp add reap \
      --url https://mcp.reap.video/mcp \
      --transport streamable-http \
      --auth oauth
    ```
  </Step>

  <Step title="Sign in to Reap">
    ```bash theme={"system"}
    openclaw mcp login reap
    ```

    OpenClaw opens the Reap authorization page. If your setup returns an authorization code instead of completing in the browser, pass it back:

    ```bash theme={"system"}
    openclaw mcp login reap --code <code>
    ```
  </Step>

  <Step title="Choose a workspace and authorize">
    Sign in to Reap, select the workspace OpenClaw is allowed to use, and click **Authorize**.
  </Step>

  <Step title="Reload the server">
    ```bash theme={"system"}
    openclaw mcp reload
    ```

    This clears the cached MCP runtime for the current CLI process. Gateway processes need their own restart or reload before they pick up the new server.
  </Step>
</Steps>

## Edit The Config Directly

If you prefer to edit the file, the entry lives under `mcp.servers` in `~/.openclaw/openclaw.json`:

```json theme={"system"}
{
  "mcp": {
    "servers": {
      "reap": {
        "url": "https://mcp.reap.video/mcp",
        "transport": "streamable-http",
        "auth": "oauth"
      }
    }
  }
}
```

<Note>
  The canonical field is `transport: "streamable-http"`. OpenClaw also accepts the CLI-native `type: "http"` alias when saved through `openclaw mcp set`, and `openclaw doctor --fix` normalizes it.
</Note>

## Confirm The Connection Works

```bash theme={"system"}
openclaw mcp status
```

```bash theme={"system"}
openclaw mcp tools reap
```

The second command lists the Reap tools available to your agent. You can also ask in chat:

```text theme={"system"}
What Reap tools do you have access to?
```

## Troubleshooting

* **Server unhealthy?** Run `openclaw mcp doctor` or `openclaw mcp probe reap` to see the connection error.
* **Tools missing after login?** Run `openclaw mcp reload`, then restart the gateway process.
* **Login loop?** Run `openclaw mcp logout reap` followed by `openclaw mcp login reap` to start a clean OAuth flow.
* **Wrong workspace?** Log out, log in again, and pick the correct workspace on the Reap authorization screen.

<Warning>
  Do not paste secrets inline in `openclaw.json`, because the file ends up in backups and migrations. Reap MCP uses OAuth, so there is no API key to store here.
</Warning>

## Learn More

* [Connect Reap MCP Server](/help-center/connect-reap-mcp-server)
* [Reap MCP Guide](/help-center/reap-mcp-guide)
* [MCP API Reference](/api-reference/mcp)
* [Reap Dashboard](https://app.reap.video)