Tail MCP por rtf6x

Tail MCP connects an AI assistant running on your own machine to this browser, through a local MCP (Model Context Protocol) server that you run
yourself. No cloud service, no account: the extension talks only to a WebSocket server on 127.0.0.1.

Why not a browser-automation framework? Those drive a separate, automated browser. Sites that fingerprint bot-controlled browsers — the
usual anti-bot and login-walled pages — detect and block it. Tail MCP is a real extension inside your own, already logged-in browser, so to the
website the traffic looks exactly like you clicking around. It is: no automation flag, no headless fingerprint, no second profile to
authenticate again.

• Tabs — list, open, close, reorder and group.
• History — search your recent browsing history.
• Pages, on the domains you approve — read text and links, find and highlight text, scroll an element into view, query the DOM, run
  JavaScript, read console output, take screenshots, and resize the viewport to check responsive and mobile layouts.
• One server, many browsers — every install registers with its own browser ID, so one server can drive several browsers side by side.

• Page access is granted per domain, in the extension's Options page — nothing is readable or scriptable until you approve that domain.
• Every tool has its own on/off switch.
• A local audit log records every command that ran.
• No analytics, no telemetry, no third-party SDKs. The extension declares no data collection; settings and the audit log stay in your browser
  profile.

The fox-tail icon reports the connection to your server: grey when the server is offline, amber while connecting, orange once connected. Hover
it for the exact state; clicking it opens Options. If the button lands in the extensions menu instead of the toolbar, pin it there.

1. Install this extension.
2. Run the MCP server on your own machine — a prebuilt desktop app from the project's releases, a container image, or a source checkout.
3. Open Options (click the toolbar icon) and set a Browser ID plus the server's WebSocket URL, ws://127.0.0.1:18789 by default.
4. Point your MCP client at the server's Streamable HTTP endpoint, http://127.0.0.1:18790/mcp.

Port 18789 is the extension WebSocket, 18790 is MCP.

Open source under the MIT license — source, attribution and full setup instructions: https://github.com/rtf6x/tail-browser-mcp