A
Agiliton
Feature comparison

Five field leaders. Seventeen features.

Every cell traces to a public-facing source or a file path in the SiteBridge repo. No hand-waving. ships it   partial   doesn’t.

CapabilitySiteBridgeClaudeforChromePlaywrightMCPBrowserMCPDevToolsMCP
Bundled with model + agent runtime (no third-party sub)
Runs inside your real logged-in Chrome1
Works with any LLM provider (no model lock-in)2
Local-only data path possible3
Pre-click safety guards (expectedTarget, viewport check)
Undo log + DOM snapshot ring buffer
Compound wait-aware tools (click+wait+read)4
Cross-session selector learning
Semantic search across open tabs
Markdown negotiation (~10× token reduction)
Userscript / JS injection / CSS overlay5
Network capture + custom HTTP requests
Performance tracing (Core Web Vitals)
GIF recording with click indicators
Element-selection human handoff
Domain integrations (Smartling/n8n/Confluence/GDocs/Jira)
Per-MCP-client session isolation (Tab Groups)N/A6
Clipboard-routed secrets (no transcript leak)
Documented tool count30+~540+~829
  1. Chrome DevTools MCP can attach to your real Chrome but only after relaunching with --remote-debugging-port=9222 every session — characterized as “torture” in published comparisons.
  2. Claude for Chrome runs only against Anthropic’s own models, gated to paid plans (Pro = Haiku 4.5; Max/Team/Enterprise = Sonnet 4.5 / Opus 4.5).
  3. Claude for Chrome inference happens on Anthropic’s servers — fine for many uses, blocking for regulated workloads.
  4. Implicit browser-native waits, but no documented compound primitive that combines click + navigate + settle + read in one call.
  5. Anthropic’s blog explicitly lists capabilities as “clicking, form-filling, navigation” only.
  6. Playwright MCP spawns its own browser — per-client isolation is automatic but at the cost of throwing away cookies, MFA tokens, browser extensions, and your real fingerprint.