My Machines / Remote Control: route localhost streamableHttp MCP via the worker, not Cursor cloud backend

Ideas Feature Requests
, ,
1

Feature request for product/service

Cloud Agent (GitHub, Slack, Linear,…)

Describe the request

Summary

When a Cloud Agent / Remote Control session runs on My Machines, local privacy MCP servers that listen on 127.0.0.1 (streamableHttp) are unreachable, because HTTP MCP is dialed from Cursor’s cloud backend. The worker can already edit files and run shell on the host, but cannot use the host’s loopback MCP.

Repro

  1. On a Mac, run a local MCP on http://127.0.0.1:14242/mcp/ (example: Nowledge Mem).
  2. Configure it in ~/.cursor/mcp.json as type: streamableHttp → http://127.0.0.1:14242/....
  3. Desktop Agent on that Mac: MCP tools appear and work.
  4. Start a Cloud Agent / phone Remote Control session targeting the same machine as a private worker.
  5. The agent can read/write the workspace and run shell on the Mac, but the localhost MCP tools are absent from the tool catalog.

Expected

For My Machines / self-hosted workers, streamableHttp URLs that target 127.0.0.1 / localhost should be connected from the worker process on that machine (same trust boundary as stdio MCP on the worker), not from Cursor’s cloud backend.

Alternatively (weaker): clearly document that local HTTP privacy MCPs are unsupported on My Machines, and that only:

  • dashboard-registered stdio MCPs (run on worker), or
  • publicly reachable HTTPS MCPs (dialed from Cursor backend)

are supported — so users don’t try to “just Remote Control” a localhost Mem/KG.

Why this matters

Many personal tools intentionally bind to loopback only (memory graphs, local DBs, credential brokers). Asking users to publish those on a public HTTPS endpoint just to use phone Remote Control is the harmful workaround. Stdio is a partial escape hatch, but hosts that already ship streamableHttp-on-localhost (common MCP pattern) still break.

Staff have already clarified elsewhere that:

  • My Machines does not read host ~/.cursor/mcp.json by itself (dashboard / session MCP config).
  • stdio MCPs run on the worker; HTTP MCPs are handled by Cursor’s backend.

This request is specifically about the localhost HTTP case under that model: please either proxy loopback HTTP MCP through the worker, or document the limitation prominently for Remote Control / My Machines.

Related

Non-goal

I am not asking Cursor to scrape arbitrary host mcp.json into every cloud session. The ask is narrower: when a My Machines session is already executing on machine X, loopback MCP on X should be reachable without exposing it to the public internet.

Operating System (if it applies)

MacOS

1 Like