Why This Search Exists

Without access to the live dashboard session, assistants can only infer from code or logs and miss the rendered state where many issues become obvious.

The value of browser-aware MCP comes from being attached to the real session, not just any browser.

Recommended Approach

A local MCP browser workflow lets the assistant inspect, snapshot, and navigate the same live dashboard state the engineer already has.

iatlas-browser provides this through a shared local runtime used by CLI, MCP, and the daemon.

Key Takeaways

  • Dashboard debugging benefits from shared browser context.
  • MCP is strongest when it points to the real local session.
  • A shared runtime reduces friction across tools.
  • Hosted APIs remain separate from live debugging.

Fast Start

  1. Start the local runtime during the debugging session.
  2. Connect the assistant through MCP.
  3. Use browser-aware tools against the live dashboard tab.
  4. Keep public lookups 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