Cursor connects directly to Scrollport over Streamable HTTP and stores its own OAuth credentials. Use Cursor's native remote-server support; you do not need a local proxy or a copied API key.

Connect

Open MCP settings

In Cursor, open Settings → Cursor Settings → Tools & MCP, then select Add Custom MCP. If that control is not shown, use Developer → Edit Config to open mcp.json.
Add Scrollport

Add this entry inside the existing mcpServers object. Do not replace other servers already in the file.
code
```
{
  "mcpServers": {
    "scrollport": {
      "url": "https://mcp.scrollport.com/"
    }
  }
}
```
Save the file, return to Tools & MCP, and enable Scrollport. Use ~/.cursor/mcp.json when the connection should be available across projects, or .cursor/mcp.json when only the current project should declare the server URL. Never commit OAuth credentials or an API key.
Sign in and authorize

Cursor opens Scrollport in the browser. Sign in with Google, review the connection name, scopes and return host, then separately select Authorise connection. If Cursor shows Needs authentication instead of opening the browser, select it to start OAuth.
Start a chat and verify

Confirm that Scrollport is enabled and its five tools appear in Cursor. Start a new Agent chat, then ask Cursor to call the free wallet tool before running metered work.

See Cursor's Model Context Protocol guide for current configuration locations and MCP controls.

Disconnect and revoke

Disable or remove Scrollport from Tools & MCP, and remove its entry from mcp.json when it should no longer be configured.

Then open Agent access in Scrollport and revoke the matching MCP connection. Removing the configuration alone does not invalidate an OAuth refresh token already held by the client, 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.