OpenClaw connects directly to Scrollport over Streamable HTTP and manages the OAuth session itself. Configure the remote server explicitly; never add a bearer token or Scrollport API key to its configuration.

## Connect

1. **Add the server**

   Run:

   ```bash
   openclaw mcp add scrollport \
     --url https://mcp.scrollport.com/ \
     --transport streamable-http \
     --auth oauth
   ```

2. **Start OAuth**

   Run:

   ```bash
   openclaw mcp login scrollport
   ```

   OpenClaw opens the authorization URL and listens for the browser callback. On a remote or headless host where the callback cannot reach OpenClaw, follow the printed `--code` fallback instead.

3. **Sign in and authorize**

   Sign in with Google, review the connection name, scopes and return host, then separately select **Authorise connection**. Return to the terminal after the callback completes.

4. **Probe and verify**

   Prove that the server connects and exposes its tools:

   ```bash
   openclaw mcp doctor scrollport --probe
   ```

   Restart or reload the OpenClaw agent or gateway process that will use the connection, then ask it to call the free `wallet` tool. A configuration-only status does not prove a live MCP connection; use `--probe` for that check.

See OpenClaw's [MCP command guide](https://docs.openclaw.ai/cli/mcp) for current OAuth, probe and reload behavior.

## Disconnect and revoke

Clear the OAuth session and remove the saved server:

```bash
openclaw mcp logout scrollport
openclaw mcp unset scrollport
```

Then open **Agent access** in Scrollport and revoke the matching **MCP connection**. This invalidates the connection's access and refresh tokens without affecting other clients.

Return to the [Remote MCP overview](https://scrollport.com/docs/mcp) for the canonical endpoint and all supported clients.