"Using personal browser with existing cookies and session data" matching MCP servers:

Drives the browser you are already signed into, so work behind a login, SSO or MFA needs no scripted auth. A local stdio MCP server talking to the free T3rnel Browser extension over a native-messaging relay. 20 tools standalone; 99 with the extension — CSS-as-component export, full-page capture, React inspector, network and console capture, form filling, record and replay. Nothing hosted.

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

Enables selecting a saved Codex or Claude Code session from the same PC and importing its recent context into the other tool, so work can continue across clients with source and omission information.

Provides MCP tools to migrate or compress conversation sessions between models based on context window capacity, including querying model context windows and listing known models.

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

Browser automation for OpenCode using Chrome DevTools and a shared Chromium profile, with per-session tab isolation so concurrent agents don't interfere. Enables browser agents to use existing signed-in sessions with shared cookies and extensions.

MCP server for local browser control via Chrome/Edge extension, enabling agents to open isolated tabs, observe pages, take screenshots, and interact with accessible controls using an existing browser profile. It is agent-agnostic, local-only, and supports safe session scoping with origin grants and sensitive-data blocking.

MCP server for programmatic lifecycle management of Claude Code sessions, supporting list, create, read, send, fork, wait, and interrupt operations.

Browser use using Typesafe's Jev model

Enables Grok CLI to control your already-running Brave browser via Chrome DevTools Protocol, allowing tab management, clicking, typing, navigation, and screenshots using your existing session and logins.

Provides web search, dice rolling, text processing, and dad jokes tools, integrated with LangGraph for intelligent workflow orchestration.

Enables MCP-capable clients to launch and control one visible, isolated Chromium session, creating and managing Tether-owned tabs, navigating to HTTP(S) URLs, reading bounded page text on request, and ending the session without touching the user's personal browser profile.

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.

Enables governed browser automation for AI agents with human-in-the-loop approval, audit logging, and read-only replay, supporting both ASK and AUTO autonomy modes.

Enables cross-tool session reading and bidirectional incremental context synchronization for AI coding tools such as Codex, Claude Code, and VS Code Copilot, with exact caller identification and incremental transcript access.

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.

Enables local control of existing Chrome/Chromium browser tabs through MCP, including tab management, navigation, content reading, screenshots, and page interaction.