Most browser automation tools spin up a fresh headless browser and start from scratch. But all the useful context is already in my real browser. My sessions, my cookies, my tabs, my logged in state.
So I built LiveMCP. It is an MCP server and browser extension that gives AI tools direct access to the browser you are already running. No separate process, no fresh profile. Claude Code, Cursor, or any MCP client connects to a local hub daemon, the daemon talks to the extension over WebSocket, and the extension runs browser APIs inside your live profile.
Version 1.2 added compound tools and tab targeting by URL or title, so you can say "scroll down on the GitHub tab" and it just works. The hub multiplexes across multiple AI sessions over Unix sockets, so there are no port conflicts if you have Cursor and Claude open at the same time.
It supports 30 plus tools across screenshots, tab control, navigation, form interaction, network capture, console logs, and storage access.