Persistent Browser Session And Profile Management

via “browser session lifecycle management”

Automate browser interactions and take screenshots via Puppeteer MCP.

Unique: Exposes Puppeteer's browser lifecycle (launch, createIncognitoBrowserContext, close) as MCP tools, enabling clients to manage browser sessions without direct SDK access. Implements context isolation pattern for multi-workflow scenarios.

vs others: Cleaner abstraction than requiring clients to manage Puppeteer SDK directly; context isolation enables safe concurrent automation workflows within a single server instance.

via “persistent browser context and session state management”

Run cloud browser sessions and web automation via Browserbase MCP.

Unique: Leverages Browserbase's cloud infrastructure to persist browser context (cookies, DOM state, history) across multiple MCP tool invocations, enabling multi-step workflows without re-authentication; context IDs are managed through CLI flags and passed between tool calls

vs others: More reliable than client-side session management (localStorage, cookies) because state is stored server-side in cloud infrastructure; eliminates need for manual state serialization/deserialization compared to local browser automation

via “cookie-and-session-management”

Experimental MCP server for browser automation using Puppeteer (inspired by @modelcontextprotocol/server-puppeteer)

Unique: Wraps Puppeteer's cookie management API as MCP tools, enabling LLM agents to handle authentication and session state without direct browser object access or manual cookie serialization

vs others: More flexible than HTTP-only cookie handling (supports domain-specific cookies and attributes) but requires manual cookie management logic in the LLM agent (no automatic refresh or expiration handling)

via “browser-session-authentication-and-state-management”

Perplexity AI answers alongside any browser search.

Unique: Stores and manages Perplexity session state directly in the browser extension, allowing transparent authentication without requiring users to log in to a separate website or manage API keys manually

vs others: More user-friendly than API key management because it uses the same credentials as the Perplexity website, though less secure than OAuth because credentials are stored in browser storage rather than delegated tokens

via “browser session lifecycle management with profile persistence”

🌐 Make websites accessible for AI agents. Automate tasks online with ease.

Unique: Implements a SessionManager with CDP connection pooling for multi-tab scenarios and storage state persistence via JSON serialization. Handles graceful shutdown with signal handling and timeout-based process termination. Supports browser profile configuration with custom launch arguments and proxy settings.

vs others: More robust than raw Playwright because it manages process lifecycle and handles graceful shutdown; more flexible than cloud-based RPA because it supports local profile persistence and custom browser configurations.

via “session-based connection and browser pooling with state management”

🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl!

Unique: Browser sessions implement tab pooling within a single browser context, reducing memory overhead compared to per-request browser spawning. Sessions maintain cookies, headers, and authentication state across requests with optional proxy rotation per-request, enabling complex multi-step workflows without manual state management.

vs others: Selenium and raw Playwright require manual browser lifecycle management; Scrapling's Session abstraction handles connection pooling, tab reuse, and state persistence automatically. Tab pooling reduces memory usage by ~60-70% vs spawning separate browser instances in concurrent scenarios.

via “session configuration and storage with persistent context across requests”

🔥 Open Source Browser API for AI Agents & Apps. Steel Browser is a batteries-included browser sandbox that lets you automate the web without worrying about infrastructure.

Unique: Implements session persistence through ChromeContextService that maps session IDs to CDP contexts, enabling context reuse across multiple requests. Sessions can be cloned, restored, and queried through a unified API.

vs others: More sophisticated than Puppeteer's basic context support; provides session cloning, restoration, and metadata tracking, whereas Puppeteer requires manual context management.

via “browser context and session management”

Playwright MCP server

Unique: Maintains a registry of isolated browser contexts with independent storage/cookies, enabling multi-context automation through a single MCP server. The context management layer abstracts Playwright's context API and provides tool-level access to context creation/switching.

vs others: Provides context isolation and management through MCP tools, whereas direct Playwright usage requires client-side context management code.

via “persistent browser profile management with cookie-based authentication”

Open-source MCP server for LinkedIn. Give Claude and any MCP-compatible AI assistant access to profiles, companies, jobs, and messages.

Unique: Implements persistent local browser profiles that maintain LinkedIn authentication state across server restarts, eliminating repeated login flows. Uses Patchright's profile management to store cookies and session tokens locally, enabling stateful authentication without requiring credential re-entry or external session stores.

vs others: More convenient than stateless authentication approaches (e.g., OAuth, API tokens) because it reuses browser-based authentication without requiring LinkedIn API access. More reliable than in-memory session storage because profiles survive server restarts.

via “multi-browser session routing”

AI-powered 3D globe control via MCP — 59 tools for camera, layers, entities, animation, scene, interaction, heatmap, trajectory, and geocoding with CesiumJS. Supports stdio (Claude Desktop, VS Code Copilot, Cursor) and Streamable HTTP (Dify, n8n, custom backends) transports. Multi-browser session r

Unique: Utilizes a centralized session management system that tracks user states and interactions across different browsers, unlike traditional single-browser solutions.

vs others: More robust than traditional session management systems as it supports real-time updates across multiple browsers without manual refresh.

via “browser-session-and-context-management”

Model Context Protocol servers for Playwright

Unique: Implements browser/context/page lifecycle management as discrete MCP tools, allowing LLMs to explicitly manage multiple isolated sessions and switch between them, enabling complex multi-scenario automation without requiring application-level session tracking

vs others: Provides explicit context isolation (separate cookies, storage, cache) as a first-class concept in MCP tools, enabling LLMs to reason about session boundaries and manage multi-user scenarios more naturally than frameworks requiring manual state management

via “browser session persistence and state management”

为 AI Agent 设计的 JS 逆向 MCP Server，内置反检测，基于 chrome-devtools-mcp 重构 | JS reverse engineering MCP server with agent-first tool design and built-in anti-detection. Rebuilt from chrome-devtools-mcp.

Unique: Provides agent-native session management with automatic state persistence and pooling support, enabling long-running agent workflows without manual state tracking; vs raw CDP which creates new browser instance per connection

vs others: More efficient than creating new browser instances per task because it reuses sessions with persistent state; enables multi-agent collaboration through session pooling vs isolated browser instances

via “interactive-browser-state-persistence-with-authentication-setup”

An MCP server that autonomously evaluates web applications.

Unique: Decouples authentication setup from automated testing by persisting full browser state (cookies, localStorage, sessionStorage) to disk, allowing subsequent agent evaluations to inherit authenticated sessions without re-implementing login logic. Uses Playwright's browser context serialization to capture and restore complete session state, not just cookies.

vs others: Unlike environment-variable-based token injection or hardcoded credentials, this approach captures the full browser state including cookies, local storage, and session artifacts, making it compatible with complex authentication flows (OAuth, SAML, 2FA) that cannot be scripted. More flexible than pre-recorded HAR files because it captures live session state.

via “browser context and session management for stateful test workflows”

Currents MCP server

Unique: Implements an in-memory context registry that maintains Playwright browser instances across MCP tool invocations, enabling stateful workflows without re-initializing the browser. Uses context identifiers to allow LLMs to reference and reuse browser sessions across multiple tool calls.

vs others: Unlike stateless browser automation tools, this capability enables persistent browser sessions across LLM tool invocations, reducing overhead and enabling complex, multi-step user journey automation.

via “playwright-browser-session-management-with-context-isolation”

🌐Web Agent Protocol (WAP) - Record and replay user interactions in the browser with MCP support

Unique: Provides context-aware session management that isolates recording sessions and preserves browser state, treating each recording as an independent experiment with its own browser context

vs others: More robust than manual Playwright usage because it handles cleanup and error cases automatically, and more flexible than headless browser services because it runs locally with full control

via “session state management and cleanup”

BrowserStack's Official MCP Server

Unique: Implements MCP-aware session lifecycle management that integrates with the protocol's tool invocation model; tracks sessions at the MCP server level to ensure cleanup even if client disconnects unexpectedly

vs others: Better resource safety than raw BrowserStack API because the MCP server enforces cleanup hooks; more reliable than client-side cleanup because it's centralized in the server process

via “cookie-and-session-management”

Fork and update (v0.6.5) of the original @modelcontextprotocol/server-puppeteer MCP server for browser automation using Puppeteer.

Unique: Exposes Puppeteer's cookie management as discrete MCP tools with JSON serialization, enabling agents to export and import session state without managing Puppeteer's cookie API directly or handling domain/path validation.

vs others: More agent-friendly than raw Puppeteer cookie APIs because it provides simple get/set/delete operations as MCP tools, vs. requiring agents to manage Puppeteer's cookie objects and domain validation.

via “cross-platform browser session management via puppeteer”

** (by UI-TARS) - A fast, lightweight MCP server that empowers LLMs with browser automation via Puppeteer’s structured accessibility data, featuring optional vision mode for complex visual understanding and flexible, cross-platform configuration.

Unique: Leverages Puppeteer's context API for true session isolation rather than simple page management, enabling concurrent multi-session automation with independent cookies/storage while maintaining a single browser process for resource efficiency

vs others: More efficient than spawning separate browser processes per session; provides better isolation than shared-page approaches; cross-platform without custom OS-specific code unlike Selenium or raw browser APIs

via “stateful web navigation with context preservation”

** - Automate browser interactions in the cloud (e.g. web navigation, data extraction, form filling, and more)

Unique: Implements session affinity at the MCP protocol level, routing all commands within a session to the same cloud browser instance without requiring the client to manage connection pooling or session tokens. Automatically handles cookie/storage synchronization and provides session metadata (expiry, resource usage) as part of the MCP response schema.

vs others: More reliable than stateless REST API wrappers around Selenium because it guarantees session continuity without manual cookie management, and simpler than building custom session orchestration on top of Playwright because session routing is handled transparently by the MCP server.

via “cookie and session persistence management”

** - A MCP server that provides comprehensive website snapshot capabilities using Playwright. This server enables LLMs to capture and analyze web pages through structured accessibility snapshots, network monitoring, and console message collection.

Unique: Provides cookie-based session management without requiring credential storage, using Playwright's context.addCookies() API to enable authenticated access while maintaining security boundaries

vs others: More secure than embedding credentials because it uses session cookies; more flexible than hardcoded login flows because it supports any authentication method that uses cookies