The MCP Connector turns LumaBrowser into a Model Context Protocol client. Point it at a filesystem server, an internal HTTP service, or anything else that speaks MCP, and its tools are discovered live and handed straight to your local chat agent. No restart, no config file editing, and nothing leaves your machine unless the server you connected is remote.
Most tools pick a side: either they expose an MCP server, or they consume one. LumaBrowser does both, and the two meet in the same registry. Tools you import from an external server are re-exported on LumaBrowser's own MCP surface, so a single connection from Claude Desktop or Cursor reaches your browser tools and every server you have connected behind it.
External agents connect to LumaBrowser and drive real tabs: navigate, click, read the page, intercept traffic.
The MCP Connector dials out to third-party servers and pulls their tools in for your local chat agent to use.
The inbound half is covered in depth on the AI agent browser page. This page is about the outbound half.
Servers are added from a form, not a JSON file you have to find on disk. Open the AI tab, switch to Setup, and pick the MCP Servers tab.
Click Add a server, name it, and choose a transport: a local command, Streamable HTTP, or legacy SSE.
For a local server, give the command, arguments, an optional working directory, and any environment variables. For a remote one, give the URL and any headers.
Saving connects right away and lists the tools the server exposes, each shown as a chip on the server card.
The imported tools appear in the chat gear panel grouped by source, with per-tool checkboxes, alongside the built-in tools.
The chat agent re-reads its tool catalog every turn, so a server you connect mid-conversation is usable in your next message.
Each card carries Enable, Disable, Reconnect, Edit, and Remove, plus a live status badge and the raw error text when something fails.
Pick the one your server speaks. Local servers almost always use stdio; hosted ones use Streamable HTTP, with SSE kept around for older deployments.
| Transport | Use it for | What you provide |
|---|---|---|
stdio |
Local servers launched as a child process, the most common kind. | Command, arguments, optional working directory, environment variables for secrets. |
Streamable HTTP |
Hosted or networked servers on the current MCP HTTP transport. | Endpoint URL and any headers, including bearer tokens. |
SSE |
Older HTTP deployments that predate Streamable HTTP. | Endpoint URL and any headers. |
On Windows, command-line launchers such as npx, uvx, bunx, pnpm, and deno are wrapped automatically, so a command that works on macOS or Linux works as typed without you adding cmd /c yourself.
Imported tools are treated exactly like the ones LumaBrowser ships with, which means they inherit the same controls you already use.
Every imported tool is namespaced as mcp__server__tool, so two servers can both expose a tool called search without ambiguity.
Imported tools land in the chat gear panel grouped by source, so you can hand one conversation your filesystem tools and another none at all.
Anything you connect also appears on LumaBrowser's own MCP surface, so external clients reach it through the same single connection.
Connecting, disabling, or removing a server takes effect on the next chat turn. The browser keeps running throughout.
Local servers take environment variables and remote ones take custom headers, so API keys never have to sit in a visible command line.
The same server list is available over LumaBrowser's REST API, so you can provision connections from your own tooling.
Tools, specifically. The connector consumes the tools an MCP server exposes. Resources, prompts, and sampling are not consumed today. If a server adds new tools while it is running, hit Reconnect to pick them up.
Authentication is headers and environment variables. Remote servers take any headers you supply, which covers bearer tokens and API keys. There is no OAuth flow, so servers that require an interactive OAuth handshake are not supported yet.
Reconnection is manual. If a local server crashes or a remote endpoint goes away, the card shows the error and the tools disappear from chat until you press Reconnect. There is no background retry loop.
Credentials are stored locally. Environment values and headers are saved in LumaBrowser's local settings database on your machine so servers can reconnect on launch. Treat that database as sensitive, the same way you would treat any local MCP client's configuration file.
The MCP Connector ships with LumaBrowser, free to download and run locally. Connect the servers you already use, decide per conversation which tools the model can reach, and give your external agents one endpoint that covers all of it.