Remote MCP is one way to connect an agent to Scrollport. It is not a separate catalog. Every supported client receives the same nine control tools for checking connected-app readiness and discovering, inspecting and running ready-to-use tools from the Scrollport wallet.

When an agent has a persistent writable shell, /start routes it through the Scrollport CLI first because that is normally the lower-friction setup. Use Remote MCP when the client supports Streamable HTTP with OAuth. MCP is optional: if the agent cannot register a connector, check the direct API and device-authorisation route. Authenticated HTTPS requests and a persistent vault or secret store are sufficient; a shell is not required.

Use this canonical Streamable HTTP endpoint:

code

https://mcp.scrollport.com/

Choose your client

Priority clients

CodexAdd the remote MCP server to Codex.Claude CodeConnect over remote MCP from the terminal.Claude, Cowork and DesktopAdd Scrollport as a remote connector.

Other supported clients

CursorAdd Scrollport to Cursor's MCP configuration.ChatGPTAdd Scrollport as a developer mode app.OpenClawConnect with Streamable HTTP and OAuth.HermesAdd Scrollport to the Hermes MCP configuration.GrokAdd a custom connector or set up Grok Bot.

Connect

Open the guide for your client.

Use the exact setup path for the chat client or coding agent you already use.
Add the Scrollport endpoint.
code
```
https://mcp.scrollport.com/
```
Sign in and authorise the connection.

Your client opens Google sign-in and then a separate Scrollport authorisation screen. Review the client name and requested access before selecting Authorise connection.
Reload the client.

Start a new agent session or restart the client unless it explicitly reloads MCP connections in place.
Verify access with the wallet.

Ask the agent to call the free get_wallet tool. A successful response confirms the connection without running a metered catalog tool.

What your client receives

Scrollport exposes the fixed control tools search_tools, inspect_tool, run_tool, get_run, list_apps, get_wallet, get_files, upload_file and delete_file. The client uses them to check app readiness and select from the live catalog on demand, which avoids loading every provider tool into the agent context.

The connection receives short-lived access tokens and a stable refresh credential directly. Scrollport never displays an API key, access token or refresh token in the browser, and you should never paste one into a connector form or committed project configuration.

Scope and revocation

Each credential belongs to one client connection, not to a model, prompt or conversation. Every connection receives the standard agent permissions discover, inspect, run, wallet, apps and files; sys-admin cannot be requested. This fixed grant allows paid runs subject to workspace spending controls and reading, uploading and permanently deleting workspace files. Read-only grants are not currently supported.

Disconnect the connector in the client to stop that client using it. Then open Agents in the Scrollport dashboard and revoke the matching MCP connection to invalidate its access and refresh tokens immediately. Other machines and client connections are unaffected.

The compatibility endpoint https://api.scrollport.com/mcp reaches the same server without redirecting, but new configurations should use the canonical endpoint above.