MCP server bridging Claude Code to a browser extension over WS+HMAC
If you already use Sallyport, the sallyport mcp server is the piece that lets your assistant work with it directly. MCP server bridging Claude Code to a browser extension over WS+HMAC.
A secure browser-automation bridge between Claude Code (or any MCP client) and your Chrome. An alternative to Kimi WebBridge with explicit security boundaries instead of implicit ones.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
list_tabs — No allowlist check — listing is freenavigate — Checks the destination URL against allowlist. waitFor={selector?,text?,absent?,timeoutMs?} polls after the load until the page is actually usablereload — Hard reload via bypassCache=true. Allowlist-gated; refs invalidatehistory_go — Back/forward through the tab's session history — return to the previous page without knowing its URL. direction='back'\close_tab — tabId required — no implicit fallback (closing the wrong tab loses work)snapshot — Accessibility tree with stable @eN refs (per-tab), pruned of layout noise. Cross-checks against a DOM walk (same refs) when the a11y tree looksread_text — Whole-page or by ref. No raw JS. Capped at 20 000 chars by default (maxChars overrides; cut results carry truncated/totalChars)get_state — Cheap one-element probe (CSS or @eN) — {exists, visible, tag, text, box?, inViewport?} without a full snapshot. Verify an action's effect or re-checkconsole_tail — Recent page console errors/warnings + uncaught exceptions for a tab ({enabled, entries:[{ts,level,text,origin}]}) — tell "the handler threw and thenetwork_tail — Recent XHR/fetch responses for a tab ({enabled, entries:[{ts,method,url,status,type,contentType,size,body?}]}) — **the data behind canvashandle_dialog — See and steer native JS dialogs (alert/confirm/prompt/beforeunload) — an open dialog freezes the page's JS and is browser UI no other tool canclick — DOM .click(). CSS selector or @eN ref. Optional waitFor polls for the click's effect in the same callnpm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Sallyport's toolset — list_tabs, navigate, reload and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ginkida; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| list_tabs | No allowlist check — listing is free. |
| navigate | Checks the *destination* URL against allowlist. waitFor={selector?,text?,absent?,timeoutMs?} polls after the load until the page is actually usable (SPAs render long after "loaded"). |
| reload | Hard reload via bypassCache=true. Allowlist-gated; refs invalidate. |
| history_go | Back/forward through the tab's session history — return to the previous page without knowing its URL. direction='back'\ |
| close_tab | tabId required — no implicit fallback (closing the wrong tab loses work). |
| snapshot | Accessibility tree with stable @eN refs (per-tab), pruned of layout noise. Cross-checks against a DOM walk (same refs) when the a11y tree looks suspiciously sparse — Telegram Web K and similar SPAs. mode=auto\ |
| read_text | Whole-page or by ref. No raw JS. Capped at 20 000 chars by default (maxChars overrides; cut results carry truncated/totalChars). |
| get_state | Cheap one-element probe (CSS or @eN) — {exists, visible, tag, text, box?, inViewport?} without a full snapshot. Verify an action's effect or re-check a ref in one round-trip. Never errors on a missing node: returns {exis |
| console_tail | Recent page console errors/warnings + uncaught exceptions for a tab ({enabled, entries:[{ts,level,text,origin}]}) — tell "the handler threw and the page is wedged" from "merely slow". **Opt-in** (popup setting, off by de |
| network_tail | Recent XHR/fetch responses for a tab ({enabled, entries:[{ts,method,url,status,type,contentType,size,body?}]}) — **the data behind canvas dashboards** (Metrika, Chart.js, WebGL) that have no readable DOM. Pull exact JSON |
| handle_dialog | See and steer native JS dialogs (alert/confirm/prompt/beforeunload) — an open dialog **freezes the page's JS** and is browser UI no other tool can click. With handling on, every dialog is answered the moment it opens (al |
| click | DOM .click(). CSS selector or @eN ref. Optional waitFor polls for the click's effect in the same call. |
| mouse_click | Real Input.dispatchMouseEvent as a full hover→press→release sequence. Auto-aims around partial overlays; a fully covered target reports covered/hitTarget/hitTargetRef. Explicit x/y (viewport CSS px) as manual aim. button |
| hover | Hover the pointer over an element/point without clicking (the mouseMoved preamble only). For CSS :hover-only menus, tooltips, row-action UIs. selector/@eN (auto-aimed, reports covered/hitTargetRef) or viewport x/y; optio |
{
"mcpServers": {
"sallyport": {
"command": "npx",
"args": ["-y", "npm"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.