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

Add the server

Run:

code

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

Start OAuth

Run:
code
```
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.
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.
Probe and verify

Prove that the server connects and exposes its tools:
code
```
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 for current OAuth, probe and reload behavior.

Disconnect and revoke

Clear the OAuth session and remove the saved server:

code

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 for the canonical endpoint and all supported clients.