Hermes connects directly to Scrollport over remote HTTP MCP and handles OAuth discovery, PKCE and token refresh. Only the server URL and OAuth mode belong in configuration; never paste a Scrollport API key into Hermes.

Connect

Add the server

Open ~/.hermes/config.yaml and add Scrollport under mcp_servers:
code
```
mcp_servers:
  scrollport:
    url: "https://mcp.scrollport.com/"
    auth: oauth
```
Merge this entry with any existing mcp_servers configuration rather than replacing the block.
Start OAuth

From a fresh terminal, run:
code
```
hermes mcp login scrollport
```
Starting login outside an active Hermes session avoids its shorter configuration auto-reload timeout and gives you time to complete authorization.
Sign in and authorize

Hermes opens the authorization URL when possible. Sign in with Google, review the connection name, scopes and return host, then separately select Authorise connection.

On a remote or headless host, use Hermes' printed paste-back instructions: open the URL locally, approve it, then paste the final redirect URL into the waiting terminal.
Reload and verify

Start Hermes, or run /reload-mcp in an existing session, then confirm that the Scrollport tools are available. Ask Hermes to call the free wallet tool before running metered work.

See Hermes' MCP guide for current OAuth, remote-host and reload behavior.

Disconnect and revoke

Remove the scrollport entry from ~/.hermes/config.yaml, then reload MCP or restart Hermes so the server is no longer available.

Then open Agent access in Scrollport and revoke the matching MCP connection. This invalidates both access and refresh tokens while leaving other Hermes profiles and Scrollport connections working.

Return to the Remote MCP overview for the canonical endpoint and all supported clients.