Lovable
Connect a Scalebrowser daemon to Lovable as a custom MCP connector, and what a cloud-hosted client needs before that works.
Lovable runs in Lovable's cloud, so it can only reach an MCP server that is reachable from the internet. A daemon on 127.0.0.1 is not, and no setting inside Lovable changes that.
What this costs you
A loopback daemon cannot be connected to Lovable. The same applies to ChatGPT, and for the same reason: the client fetches your endpoint from its own servers. Every other client in this section runs on your machine and reaches 127.0.0.1 directly.
Two ways to give the daemon a public address, with different trades:
| Option | What it means |
|---|---|
| Run the daemon on a server | The self-hosted Linux daemon on a host with a real GPU and a public name. A non-loopback bind requires TLS and refuses to start without it, so that is the same gate rather than an extra step. |
| Tunnel your local daemon | A tunnel (Cloudflare, ngrok, Tailscale) gives your machine a public HTTPS name. It is faster to set up, and it puts a full-power token on an address the whole internet can reach. |
Read Ports before either: TLS is mandatory off loopback, and the MCP transport checks the Host header, so the public name has to be listed under [mcp] allowed_hosts in the configuration.
Add the connector
In Lovable, open Connectors, go to the All tab, and pick the Custom MCP card at the bottom.
- Name the server
Anything you will recognise later, for example
Scalebrowser. - Give it the URL
The MCP path on your public daemon:
https://<your-host>/v1/mcp. - Choose bearer-token authentication
Lovable offers OAuth first, which the daemon does not speak. Pick the bearer-token option and paste the API token. Lovable keeps it in the project's secret vault.
- Add the server
The tools appear in the chat once the connector is saved.
What the agent can do now
Ask it to open a page and it will lease a profile, bind a tab and start reading. The tool set, the page map and the failure shapes are on MCP server; what the agent is allowed to do is decided by the daemon, not by the client, so see tool profiles.
A cloud client is a second place your token lives. It sits in Lovable's vault, and every tool call crosses the public internet to your daemon. If you only want an agent to drive a browser on your own machine, one of the local clients is the shorter and tighter path.