Choose the connection path for each bridge.
Direct Streamable HTTP and a compatible stdio proxy connect AXI to the shared service; without a server URL, its existing standalone stdio mode remains available.
CHROME DEVTOOLS AXI + CHROME DEVTOOLS MCP
Shared Chrome access for AXI and MCP.
Multiple clients, one long-lived Chrome connection. Client transport support is released in Chrome DevTools AXI; shared MCP sessions are implemented in a maintained Chrome DevTools MCP fork.
One shared Chrome connection, two cooperating pieces.
Multiple clients can use the same long-lived Chrome instance and page inventory. AXI selects how each client connects; the maintained MCP fork provides the HTTP server and separate MCP context and state for each HTTP client.
Three transport modes.
AXI reads CHROME_DEVTOOLS_AXI_MCP_SERVER_URL and, when present with a nonblank value, CHROME_DEVTOOLS_AXI_MCP_PATH to select its client connection mode.
Direct Streamable HTTP
Set CHROME_DEVTOOLS_AXI_MCP_SERVER_URL and leave CHROME_DEVTOOLS_AXI_MCP_PATH unset or blank. AXI connects directly to the shared endpoint over Streamable HTTP; it does not start a local MCP child in this mode.
SERVER_URL set · PATH unset / blankStdio proxy
Set both CHROME_DEVTOOLS_AXI_MCP_SERVER_URL and a nonblank CHROME_DEVTOOLS_AXI_MCP_PATH. AXI uses the local stdio child as a proxy after the compatibility check succeeds.
SERVER_URL set · PATH setStandalone stdio
With no shared MCP server URL, AXI keeps its existing standalone stdio transport.
SERVER_URL unsetMetadata-only navigation for eval chains.
Navigation-to-eval and chained page-level workflows may not need an automatically printed accessibility tree. AXI’s opt-in --no-snapshot flag on newpage or selectpage prints page metadata without the tree or snapshot-derived suggestions, so you can continue with eval when no UIDs are needed.
Navigate, then evaluate.
Open a page and continue to eval without printing the automatic tree.
newpage --no-snapshot https://example.com
eval 'document.title'Select, then continue.
Choose an existing page and continue without printing the automatic tree.
selectpage --no-snapshot 2Default navigation output is unchanged; --no-snapshot is opt-in, and --full does not override it. An explicit snapshot remains available for UID-based click or fill work. Snapshot capture and reference-freshness checks still run: this AXI CLI option changes printed output only, not browser or MCP behavior.
The MCP server implementation lives in a maintained fork.
It serves loopback Streamable HTTP at /mcp, reuses one BrowserManager, Chrome instance, and page inventory, and creates a separate MCP server and context for each HTTP client.
Chrome DevTools MCP: per-client sessions.
Merged in fork PR #3, the implementation keeps selected-page, roots, trace, recording, and request-mutex state per client. It also provides a stdio-to-HTTP proxy and cleans up sessions when clients disconnect.
Proposal closed; request remains open.
Upstream PR #2733 proposing HTTP transport was closed without merge. The request remains tracked in open issue #2188; its progress note summarizes scope and limits.
Shared Chrome, per-client MCP state.
Separate MCP contexts do not isolate browser access: all clients use the same Chrome instance and page inventory.
One Chrome, shared pages
Clients can act on the same browser and page surface.
Separate MCP state
Selected page, roots, trace, recording, and request-mutex state are per client.
No cross-client mutex
The server does not globally serialize operations across clients.
Not a public service
Remote access uses an SSH tunnel; the endpoint is not a public authenticated service.
Explore the AXI release and MCP fork.
Chrome DevTools AXI maintains the released client transport change; the shared server implementation is maintained in the Chrome DevTools MCP fork.