Why This Search Exists

Without access to the real browser session, debugging turns into guesswork based on screenshots or tickets instead of the rendered state where the issue appears.

Teams using browser-aware assistants need a real-session architecture, not a disconnected browser sandbox.

Recommended Approach

MCP becomes operationally useful here when it points to the local runtime tied to the live browser session.

iatlas-browser supports this with a shared runtime across CLI, MCP, and the daemon API.

Key Takeaways

  • Debugging benefits from shared browser context.
  • MCP is strongest when it reaches the real session.
  • A shared runtime reduces setup and handoff friction.
  • Hosted APIs remain for public retrieval and remote-safe tasks.

Fast Start

  1. Start the local runtime before the debugging session.
  2. Connect the assistant through MCP.
  3. Use snapshots and browser-aware tools against the live account state.
  4. Keep public research on the hosted layer.

Next Action

Get MCP config

Move from research to implementation by choosing the correct boundary: local runtime for real-session work, hosted API for public-safe retrieval.

Get MCP config Local runtime homepage Hosted API docs