Why This Search Exists

Assistants become much less useful when they cannot inspect the same browser state the human is already using to understand the issue. That missing context creates blind spots quickly.

The value of browser-aware MCP comes from working in the same session, not from abstract browser access.

Recommended Approach

A local MCP setup backed by the real browser session allows assistants to inspect, snapshot, and navigate in the same context as the operator.

iatlas-browser enables that by sharing one runtime across CLI, MCP, and the localhost daemon.

Key Takeaways

  • Investigations benefit from shared browser context.
  • MCP should point to the same live session as the operator.
  • A shared runtime makes browser tooling more coherent.
  • Hosted APIs remain for public retrieval and remote-safe tasks.

Fast Start

  1. Connect the assistant to the local runtime via MCP.
  2. Use browser-aware tools on a real investigation workflow.
  3. Capture the stable investigative steps for reuse.
  4. Keep public-source 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