Claude Code connects to Scrollport over Streamable HTTP and stores its own OAuth credentials. Only the server URL belongs in configuration; never paste or commit an API key.

If Claude Code has a persistent writable shell, the default setup at /start uses the Scrollport CLI. Follow this page when you deliberately want a Claude Code-scoped Remote MCP connection instead.

Connect

Check the Claude Code version

Run claude --version. The command-line claude mcp login flow below requires Claude Code 2.1.186 or later. If the installed version is older, ask before running claude update. If an update is not approved, add the server and use the interactive /mcp authentication flow available in compatible older clients.
Add the server

Run:
code
```
claude mcp add --transport http --scope user scrollport https://mcp.scrollport.com/
```
User scope makes the connection available across projects for this OS user. Use --scope local for only the current checkout, or --scope project when your team intentionally shares the server URL through the repository.
Start OAuth

Run:
code
```
claude mcp login scrollport
```
Sign in and authorize

Sign in with Google, then review the connection and separately select Authorise connection on the Scrollport screen.
Check and verify

Open /mcp to confirm that Scrollport is connected. Start a new Claude Code session or restart the current one, then call the free wallet tool.

See Anthropic's Connect Claude Code to tools via MCP for current scope flags and client commands.

Disconnect and revoke

Clear the saved OAuth login with claude mcp logout scrollport, then remove the scrollport server with Claude Code's MCP remove command at the same configuration scope used to add it.

Then open Agent access in Scrollport and revoke the matching MCP connection. Removing project configuration alone does not prove a still-valid refresh token was revoked, so complete both steps on a machine you no longer trust.

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