Remote MCP is one way to connect an agent to Scrollport. It is not a separate catalog. Every supported client receives the same five 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](https://scrollport.com/start) routes it through the Scrollport CLI first because that is normally the lower-friction setup. Use Remote MCP for Claude, Cowork and Desktop, for another client without a persistent shell, or when you deliberately want a client-scoped OAuth connection.

Use this canonical Streamable HTTP endpoint:

```text
https://mcp.scrollport.com/
```

## Choose your client

<DocsMcpClients />

## Connect

1. **Open the guide for your client.**

   Use the exact setup path for the chat client or coding agent you already use.

2. **Add the Scrollport endpoint.**

   ```text
   https://mcp.scrollport.com/
   ```

3. **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**.

4. **Reload the client.**

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

5. **Verify access with the wallet.**

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

## What your client receives

Scrollport exposes the fixed control tools `apps`, `discover`, `inspect`, `run` and `wallet`. 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 rotating refresh tokens 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 fixed least-privilege scopes `discover`, `inspect`, `run`, `wallet` and `apps`; `sys-admin` cannot be requested.

Disconnect the connector in the client to stop that client using it. Then open **Agent access** 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.