Browser runtime mappings#
SnagBadger depends on runtime capabilities, not a particular MCP product. The host coordinator maps bridge operations to its installed tools. Verify their current schemas; do not assume documentation for another version applies.
Chrome DevTools MCP#
The official tool reference exposes new_page with isolatedContext. Use a unique context name for each requested identity; repeating a name deliberately reuses that context. The context implementation creates contexts for new names.
Save the returned page handle, select/target it before actions, and route browser.perform requests to it. Use installed screenshot and screencast capabilities only when actually exposed. Closing a page and destroying its browser context are different capabilities: inspect the installed lifecycle API, release all owned targets, and report context-disposal limitations rather than claiming full disposal. A context name must never be reused even if closed pages leave the context allocated.
Other browser MCPs#
An adapter needs:
- creation of a new isolated browser context with a distinct identity per attempt;
- explicit targeting of actions/capture in that context;
- artifact paths/bytes for requested screenshots/video;
- documented cleanup for owned pages/context;
- a fresh agent-delegation mechanism supplied by the host.
A new page inside an existing profile is insufficient. A disposable same-origin cookie/local-storage probe can detect shared state; clean up its markers. API/CLI scenarios need fresh agents and durable diagnostic output, but no browser context.
T3 collaborative preview#
Current-session testing found new preview tabs sharing cookies/local storage. In that mode set newBrowserContexts false. Screenshot/video support alone does not qualify it for isolated browser tests. Do not switch the user's selected browser runtime silently; supported environments may differ across installed versions.
The workspace and preview may also have different loopback networking. A locally reachable URL is not proof that the remote browser can reach it. Select the project's declared accessible environment and preserve explicit blocked outcomes when it cannot.
Portability boundary#
The supplied filesystem bridge translates deterministic orchestration into host tool requests. It is not an embedded MCP client, a Chrome installer, or a hidden Playwright runtime. The coordinating skill supplies discovered tool mappings and fresh-agent delegation. Module users can implement the Runtime callbacks directly instead of using the bridge.
Native MCP end-to-end verification requires that MCP's installed tools. Core conformance tests verify sequencing, context identities, hooks, evidence, and rendering with deterministic adapters; they do not assert compatibility with an unavailable MCP version.