wtf is mobius-mcp?

mobius-mcp gives AI coding assistants like Claude Code, Codex CLI, or Gemini CLI live access to what is happening inside your web app in the browser, without you having to copy and paste console logs or errors into the chat window. It streams console messages, errors, network requests, and page navigation events straight from the browser into the AI agent's tools in real time. It works through a small Chrome browser extension that captures runtime events on a tab you choose, then sends them over a local WebSocket connection to a server running on your own machine. That server, called mobius-mcp, keeps a rolling history of recent events and exposes them to the AI agent using the Model Context Protocol, or MCP, a standard way for AI tools to connect to external data sources. Everything happens on localhost, with no cloud services and no telemetry sent anywhere. Capture is opt in per browser tab, so nothing streams until you click the extension's toolbar icon and enable the tab you want to debug. You can also set up rules so tabs matching a certain address, like a local development server, enable themselves automatically. Once connected, you can ask your AI agent things like checking the browser console for errors, and it can look directly at the live data instead of guessing. Beyond basic logging, the tool offers features such as recording an ordered timeline of events during a debug session, waiting for a specific condition like a console error or a network request instead of repeatedly checking, taking screenshots, and inspecting the page's structure through the Chrome DevTools Protocol when the extension is connected. Recent event history is also saved to a temporary folder on disk, so it survives if the local server restarts. The project is organized as a Node.js server, the browser extension itself, and a paused npm package meant for direct app integration without the extension. It is published on npm, so using it does not require cloning the repository.