Flecha MCP
A developer browser on Chromium with a local MCP server: an agent lists tabs, reads the console, takes screenshots and clicks
- 132 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The agent clicks, types and runs JavaScript in open tabs, including signed-in accounts.
- Pages and console logs enter the model context.
Install
- Works in
Manual install
Download `Flecha-<version>.dmg` from releases, drag the app to Applications and enable Settings, Coding agents. Then add the `127.0.0.1` address and the token from settings to the client's MCP configuration.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent clicks, types and runs JavaScript in open tabs, including signed-in accounts.
- Pages and console logs enter the model context.
This is third-party code. Review the repository files before installing.
What it does
Flecha is an Arc-style macOS browser on a Chromium 158 fork: a vertical sidebar, Spaces with separate cookies and logins, Peek link previews, split view and a command bar with queries such as `gh owner/repo` or `mdn grid`. Developer features include a responsive view, a console error badge, a list of local servers and switching between local, staging and production environments. In Settings, the Coding agents section turns on a local MCP server on `127.0.0.1` protected by a token. Through it Claude Code, Cursor and other clients list tabs, read pages and console logs, take screenshots, click, type and run JavaScript. The server needs the native host that ships with the app.
Who it is for. Web developers on macOS who want to give an agent access to live tabs of their own browser for debugging and layout checks.
Good fit when
- An agent has to read console errors of an open local page.
- After a layout edit a screenshot taken in the working browser is needed.
- A check runs under your account: a Space with separate cookies is available to the agent.
- A development page is compared with staging by switching the environment in one step.
Not a fit when
- You need a cross-platform tool: Flecha is built for macOS.
- The browser holds banking or work accounts the agent must not touch.
- A headless browser for automated tests with no UI is enough.
Example request
Open the `localhost:3000` page, read the console errors and take a screenshot after I fix the layout.MCP
- Transport
- http
- Authentication
- API key
Limitations
Builds target macOS on Apple silicon and Intel; Linux and Windows are not announced. The author calls the project early software used daily. The agent MCP server runs locally on `127.0.0.1` with a token, but the agent can click, type and run JavaScript in your tabs, including signed-in ones. The native host is also required for importing data from other browsers. Choosing the downloads folder is not yet available in the Chromium build.
How to disable. Turn off the Coding agents section in Flecha settings and remove the server entry from the client MCP configuration. Delete the app by dragging it from Applications to the Trash.
FAQ
How do I connect Claude Code to Flecha?
Enable Settings, Coding agents: Flecha starts an MCP server on `127.0.0.1` with a token. Add the address and token to the client's MCP configuration.
What can an agent do in tabs?
List tabs, read pages and console logs, take screenshots, click, type and run JavaScript.
Why is Flecha a Chromium fork rather than Electron?
Google blocks sign-in in Electron. A Chromium fork keeps Google sign-in and Chrome Web Store extensions working.
How do I install Flecha?
Download `Flecha-<version>.dmg` from GitHub releases; the `-x64` build is for Intel. Then drag the app to Applications.
What are Spaces in Flecha?
Groups of tabs with their own colour. Separate Cookies and Logins gives them a separate storage so you can sign in as different users side by side.
Discussion
No questions or reviews yet.
Related
MCP serversmacOS browser on WebKit and Rust: keyboard-first, with a built-in assistant and an MCP server an agent uses to drive the browser
A real browser inside the terminal with a CLI for the agent: a coding agent opens sites and interacts with them in the same tab
A desktop browser with local models and a built-in MCP server: Claude Code and Codex open tabs and read pages.
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
CamoFox Browser: anti-detection browser for AI agents
camofox-browser
A REST server and CLI on Camoufox: an agent opens pages with a spoofed browser fingerprint and reads them as an element tree
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Flecha (this card) | no | API key | 132 | |
| agent-browser | yes | not required | 50,530 | that card runs a separate managed browser; Flecha hands the agent your working signed-in browser |
| Chrome DevTools MCP | yes | not required | 55,199 | DevTools MCP attaches to Chrome; here a dedicated browser ships with built-in MCP and developer tabs |
README in short
The build is signed with a Developer ID and notarized by Apple, and updates itself. Sources include Chromium patches, an MV3 shell extension and a Node native host.