E2LLM MCP server

E2LLM — structured browser perception for AI

E2LLM turns a live web page into SiFR: a compact, structured, LLM-readable model of what's on the page, what it means, and what can be done with it. Perception is the product. Action is available when you need it — always explicit, always gated.

Works as a hosted remote MCP server with the AI you already use. There's no local server to run — a browser extension pairs your live browser to the server, so perception and action happen in the real browser you're already signed into.

E2LLM is not an agent

This matters, so it comes first.

An agent decides and acts on its own — it plans, loops, and takes steps toward a goal without you in the path. That autonomy is also its attack surface: an agent runtime that can do anything can be steered into doing anything.

E2LLM is a perception layer, not an agent. It gives your model senses for the browser — structured sight through sifr_capture, and a set of narrow, individually-gated actuators. It does not plan, does not loop, and does not decide. Whatever model you already use does the reasoning; E2LLM only reports what a page is and carries out one explicit instruction at a time. No hidden autonomy, no self-directed steps, nothing that runs while you look away.

That line — perception substrate versus autonomous runtime — is the whole design.

What it does

<!-- MAINTAINER NOTE — do NOT align batchact's step list to act's. They genuinely differ: act click, type, select, navigate, drag, open, paste (7) batchact click, type, select, drag, paste (5 — no navigate, no open) MEASURED: both enums read directly from e2llm-mcp-server/tools.go. Adding navigate or open here would put this doc at odds with the server's own advertised schema. WHY they differ is NOT recorded here on purpose — tools.go gives no reason, and a plausible-sounding explanation would get reasoned FROM rather than around. If you find the reason in the source, add it and say where. Verify before changing either: grep the two "enum" lists under the act and batch_act tool definitions in e2llm-mcp-server/tools.go — not by line number, they drift. Tidying these two for symmetry looks like cleanup and introduces a real defect. -->

Nine tools: five 🔎 that only perceive, and four 🖐 for interaction — of which act, batchact, and closetab change page state, while explore only reads. The tool inventory is in server.json; full parameter schemas come from the live server on connect. The perception tools never change page state; the state-changing tools can each be held for your confirmation (see Safety).

What is SiFR — and why it isn't the obvious thing

SiFR (Single-File RAG, pronounced "see-far") is a self-contained retrieval artifact for live interface state: model-readable, node-addressable, progressively queryable, and independent of the reasoning system above it. E2LLM is its reference implementation for the real browser.

Shortened. The full README is on GitHub.