Why This Search Exists

Without live browser access, assistants must infer from code, logs, or screenshots and miss the rendered context where many browser bugs live.

Teams need browser-aware debugging tied to the real session, not a disconnected demo environment.

Recommended Approach

A local MCP debugging workflow lets the assistant inspect pages, capture snapshots, and navigate the same live session the engineer is already using.

iatlas-browser enables this through one shared runtime across CLI, MCP, and the localhost daemon.

Key Takeaways

  • Debugging benefits from shared browser context.
  • MCP is strongest when it points to the real local session.
  • A shared runtime reduces context loss during investigation.
  • Hosted APIs remain separate from live debugging.

Fast Start

  1. Start the local runtime before the debugging session.
  2. Connect the assistant through MCP.
  3. Use browser-aware tools against the live issue.
  4. Keep public-source retrieval 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