Localhost & tunnels
How to test a store that runs on your own machine: with a tunnel, or with the Local runtime (private beta).
What counts as local
We treat a host as local when it is localhost, a private or loopback address, a bare hostname, or ends in .local, .localhost, .internal or .test. Local hosts keep their http:// scheme; public hosts are always upgraded to HTTPS.
To keep a local build at hand, add it under Settings → Stores & endpoints with the kind Local and its MCP or REST endpoint (see Saved targets). It then shows in the store menu, and runs use it as the store's pre-production environment, without discovery.
Keeping the scheme doesn't make the host reachable. Runs and Inspect sessions run in our cloud, and your localhost is not on our network. You can save a local address, but a run in our cloud cannot reach it.
Use a tunnel
- Put your dev store on a public HTTPS hostname with the tunnel tool you already use (ngrok,
cloudflaredor similar), for examplehttps://mystore.ngrok.app. - Serve your UCP profile at
/.well-known/ucpon that hostname so endpoint discovery works, or add the tunnel's endpoints in Settings → Stores & endpoints to skip discovery. - Pick the tunnel domain in Inspect, or start a run on it from Runs, like any other store.
While the tunnel is up, anyone can reach your dev store. Put it behind auth if the catalog matters, and remember we see exactly what any visitor would.
The Local runtime (private beta)
The Local runtime removes the tunnel: a small runner on your side makes the store requests, so the store never has to be public. It is in private beta. For access, get in touch.
Something wrong on this page?