Lilo MCP

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.

  • 55 ★ on the repository
  • Last commit
  • MIT
MCP server

Broad access

Why this level

  • An agent drives a real browser: clicks, input, page reading, cookies and network responses.
  • A borrowed profile exposes your site sign-ins to the agent, and actions such as payment need your confirmation.
All reasons and checks

alexays/lilo

Install

Manual install

brew install --cask alexays/tap/lilo

The command from the README header, macOS 26 or newer is needed. Then in Lilo settings enable Let agents use Lilo and connect a client with the Connect button.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • An agent drives a real browser: clicks, input, page reading, cookies and network responses.
  • A borrowed profile exposes your site sign-ins to the agent, and actions such as payment need your confirmation.

This is third-party code. Review the repository files before installing.

What it does

Lilo is an Arc-style Mac browser on WebKit with no Chromium that runs Chrome extensions and has terminal tabs. For agents it has a built-in MCP server: Claude Code, Claude Desktop, Codex, Cursor or any MCP client drive a real browser beside you. Lilo ships no AI of its own. Agents open tabs in a folder of a dedicated Space with a throwaway profile wiped after the session, and never see your private Spaces. Lilo asks permission before sending, paying, deleting and publishing. The tools cover navigation, input, accessibility tree reading, screenshots, console and network, request mocks, emulation and performance metrics.

Who it is for. Web developers and testers on a Mac who want to give an agent a real browser for checking pages and debugging without handing over their own tabs.

Good fit when

  • An agent must open a checkout page on localhost and find why the order fails.
  • Console, network and request responses must be read and a HAR exported.
  • Requests must be mocked or delayed to check page behavior.
  • A page needs checking in the Safari WebKit engine rather than Chromium.

Not a fit when

  • There is no Mac running macOS 26 or newer.
  • A headless CI test run is needed.
  • An agent must not get access to a browser with real payments.

Example request

Open localhost:3000/checkout in Lilo, pay with the test card and find out from console and network why the order fails.

MCP

Transport
stdio
Authentication
not required

Limitations

Lilo runs only on macOS 26 and newer and is in public beta: the interface changes and rough edges are possible. The built-in server is switched on in settings under AI agents. An agent can borrow one of your profiles only after explicit permission, and then it gets your site sign-ins. Some Chrome extension APIs differ in WebKit. The project is open, MIT licensed and needs no account.

How to disable. Turn off Let agents use Lilo in the AI agents settings and delete the Lilo entry from the MCP client settings. The browser is removed like an app, for example `brew uninstall --cask lilo`.

FAQ

How do I connect Claude Code?

In Lilo settings turn on Let agents use Lilo and press Connect next to Claude Code. Lilo adds itself to the client's MCP servers.

What does the agent see?

Only tabs in its own folder of the Agents Space and a throwaway profile. Private Spaces stay hidden and your keyboard and mouse remain yours.

When does Lilo ask permission?

Before sending data, paying, deleting, publishing and handing a page one of your files: allow once, always for the site, or deny.

Which tools are available?

Tabs and navigation, input and file uploads, accessibility tree, screenshots, console and network with HAR, request mocks, emulation and profiling.

What are the system requirements?

macOS 26 or newer. Install with `brew install --cask alexays/tap/lilo`.

Discussion

No questions or reviews yet.

A desktop browser with local models and a built-in MCP server: Claude Code and Codex open tabs and read pages.

MCP serverBroad access140Repository stars

A developer browser on Chromium with a local MCP server: an agent lists tabs, reads the console, takes screenshots and clicks

MCP serverBroad access133Repository stars

MCP server for Safari on macOS: an agent drives your real browser with your logins through 98 tools

MCP serverBroad access242Repository stars

A plugin and MCP server letting an agent drive your open, already logged-in Chrome through an extension with no debugging port.

MCP serverBroad access145Repository stars
Official

Browserless.io MCP server: a cloud browser for the agent with page reads, site crawls, Lighthouse audits and click-driven sessions

MCP serverBroad access19Repository stars

macOS browser on WebKit and Rust: keyboard-first, with a built-in assistant and an MCP server an agent uses to drive the browser

MCP serverBroad access144Repository stars

README in short

Each client is approved once and tied to the program rather than the name it gives. The project aims to replace Arc, which shuts down on December 22, 2026.

README badge

Report a problem