LumaBrowser MCP
A desktop browser with local models and a built-in MCP server: Claude Code and Codex open tabs and read pages.
- 140 ★ on the repository
- Last commit
Broad access
Why this level
- The agent drives a real browser with your tabs, cookies and signed-in accounts.
- The Windows desktop control mode lets the agent see and operate other applications.
- The REST API on port 3000 has no key and is open to anyone who reaches the port.
Install
- Works in
Manual install
npx lumabrowser startNeeds Node 18 or newer; fetches and launches the latest build.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent drives a real browser with your tabs, cookies and signed-in accounts.
- The Windows desktop control mode lets the agent see and operate other applications.
- The REST API on port 3000 has no key and is open to anyone who reaches the port.
This is third-party code. Review the repository files before installing.
What it does
LumaBrowser is a Chromium browser with local language models on llama.cpp, image generation, voice and its own agents. It ships an MCP server for outside agents: Claude Code, Codex, Cline and OpenCode open tabs, read and extract page data, call LumaBrowser agents, run timed tasks and watch pages for changes. The app writes the agent config entry from its settings. Beyond MCP there are WebDriver and CDP for Selenium, Puppeteer and Playwright (off by default), a `luma` command line tool and plugins for VS Code and JetBrains. A Docker image exists for servers.
Who it is for. People who want to give Claude Code or Codex a real browser while keeping models and data on their own machine.
Good fit when
- An agent must open a page and read it in a real browser.
- Selenium or Playwright tests run over CDP on a local browser.
- A page or element is watched and a change triggers a notification.
- A local model answers without sending data out.
Not a fit when
- A headless library without a desktop app is enough.
- Port 3000 would be exposed to an untrusted network without a key.
- An agent must not see the content of your tabs.
Example request
Open the pricing page in LumaBrowser, extract the table and report when a value in it changes.MCP
- Transport
- stdio
- Authentication
- not required
Environment variables
LUMA_API_PORT- LumaBrowser REST API port, 3000 by default.
Limitations
A whole desktop application must be installed: Windows, Linux (AppImage) and macOS on Apple Silicon. The agent sees everything the browser sees, and so does the model behind it. The REST API on port 3000 has no key by default, so set one in settings before leaving localhost. In Docker the API accepts any address, also without a key. GitHub did not detect a repository licence, so check the terms yourself. Desktop control is available on Windows only.
How to disable. Remove the `luma-browser` entry from the agent configuration and close the app. Keep the API, WebDriver and CDP ports off in settings.
FAQ
How do I connect Claude Code?
The app writes its MCP entry into Claude Code, Cline, Codex and OpenCode from settings. By hand, add `node` with the path to `mcp-server.js` from the install directory.
Must the app be running?
No. The MCP server starts LumaBrowser if it is not running.
Is the API exposed to the network?
Not by default: ports stay on localhost. The REST API on port 3000 has no key, so set one before any external access.
Can it be used with Selenium or Playwright?
Yes, through WebDriver or CDP. Both are off by default and enabled in settings.
Is there a server version?
Yes. The Docker image runs the app headless and serves the desktop through noVNC on port 6080.
Discussion
No questions or reviews yet.
Related
MCP serversBrowserless.io MCP server: a cloud browser for the agent with page reads, site crawls, Lighthouse audits and click-driven sessions
The built-in MCP server of Lilo, a macOS WebKit browser: Claude Code and Codex drive a real tab in a Space of their own.
A Claude Code plugin with an MCP server and seven skills: the agent drives a real browser by writing Python code
A developer browser on Chromium with a local MCP server: an agent lists tabs, reads the console, takes screenshots and clicks
A local browser automation platform: MCP server, CLI and skills so an agent can drive Chrome, fill forms and pull data from pages
A Chromium with engine-level device fingerprint spoofing and an MCP server that lets an agent drive it through Playwright
README in short
Browser, local models, agents and an MCP server are combined in one application. Automation goes through MCP, WebDriver, CDP, a REST API and the `luma` command line tool.