Why This Search Exists

Without access to the live browser session, assistants can only reason from partial evidence such as notes, screenshots, or logs. That weakens browser-heavy investigations immediately.

What teams need is a browser-aware MCP setup that lands inside the real session, not a detached sandbox.

Recommended Approach

A local runtime exposed through MCP lets assistants inspect pages, capture snapshots, and navigate the same browser context the operator trusts.

iatlas-browser supports this with one shared local runtime across CLI, MCP, and the localhost daemon.

Key Takeaways

  • Investigations benefit from shared browser context.
  • MCP is strongest when it reaches the real session.
  • A shared runtime lowers debugging and setup friction.
  • Hosted APIs remain for public retrieval only.

Fast Start

  1. Connect the assistant to the local runtime via MCP.
  2. Use browser-aware tools in a real ops investigation.
  3. Capture the useful steps for reuse.
  4. Keep public research tasks 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