"Claude for Safari browser extension or integration" matching MCP servers:

Enables MCP-compatible agents and HTTP clients to discover, claim, and control Chrome tabs through an authenticated local bridge, including snapshots, actions, approvals, task ownership, screenshots, frames, diagnostics, and cleanup.

Enables remote browser automation via MCP, allowing models to open pages, read snapshots, click, fill, and select elements using Playwright, with built-in security restrictions against sensitive actions.

Reliable, scalable browser infrastructure for AI agents. Route, pool, and failover across any browser provider. 8 built-in browser tools using raw Chrome CDP - navigate, screenshot, snapshot, interact, evaluate. Zero-config with auto Chrome detection & concurrent sessions support

MCP server that lets Claude control multiple persistent browser tabs inside VS Code, with tools for navigation, clicking, typing, snapshotting pages, and reading console output.

Enables AI to control a real browser through MCP tools for clicking, typing, navigation, screenshots, and more. It supports a follow mode that tracks the active tab, plus fixed mode for controlling specific tabs.

Enables seamless real-time collaboration between Claude Code and the Gemini CLI for discussing ideas and refining solutions. It provides tools to initiate collaborative sessions, consult Gemini with context preservation, and access conversation history.

Browser use using Typesafe's Jev model

Enables MCP clients to drive a self-hosted Chrome session for browsing tasks through browser tools, while providing a live view URL so a human can take over at prompts like logins or 2FA.

Lets any number of concurrent Claude Code sessions drive a Firefox browser through the Browser Control extension by funneling every session's commands over a single shared port via a background daemon and private unix socket. Sessions no longer have to compete for a limited pool of extension ports, and requests stay isolated through per-request correlation ids.

Enables MCP agents to drive an already signed-in Chrome or Edge browser through a local extension bridge, controlling existing tabs and opening task-related HTTP(S) tabs without remote debugging or profile copying.

Enables AI agents to inspect and modify Chrome state directly through extension APIs, listing tabs and windows and moving or reordering tabs within and across windows. Operations are validated and never simulate mouse/keyboard input, steal focus, or activate tabs implicitly.

MCP server that gives AI full control of a live Chrome browser via CDP, with 145 tools for framework-aware intelligence, evidence analysis, and SEO auditing. Connects to your existing Chrome via an extension, enabling interaction with dynamic and authenticated web pages.

MCP server that lets agents drive your real Chrome browser with existing logins and sessions via an outbound-only WebSocket extension. It exposes Playwright-compatible browser tools for navigation, clicking, typing, and snapshots.

A hardened local browser MCP server that drives your existing Chrome over the DevTools Protocol, providing token-efficient Markdown extraction and stealth features to avoid trivial automation detection.

MCP server for managing and controlling multiple isolated Chrome/Edge browser instances, exposing tools for navigation, screenshots, clicking, form filling, and JavaScript execution to AI clients.

Enables AI agents to control a real, persistent Chrome browser over MCP, perceiving pages as accessibility trees and interacting with elements by their accessible names without automation fingerprints or site-specific glue.

Gives MCP-compatible AI agents direct control of your real browser with existing sessions, logins, and cookies. Supports multiple agents concurrently with tab targeting.

Enables AI agents to control a Playwright-driven browser through natural-language instructions, including page interaction and live browser task execution.

Enables an agent to drive a real browser while enforcing provenance-based gating so URLs and form values must trace to the user or an allowlist, never to untrusted page content.

MCP server that bridges Model Context Protocol with browser automation, offering 37 tools across three modes (Playwright, CDP, Chrome Extension) and an autonomous agent for web tasks.