Cross Device Session Persistence With Browser Storage

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-storage-management”

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

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 “cookie and storage management”

Chrome DevTools for coding agents

Unique: Provides unified access to cookies, localStorage, and sessionStorage via Chrome DevTools Protocol, enabling agents to manage all storage types without separate APIs or custom JavaScript execution.

vs others: Offers transparent storage management (vs Puppeteer's JavaScript-based localStorage access), enabling agents to set cookies and manage session state without custom code, improving reliability for authentication-dependent workflows.

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 “cookie and local storage management”

** - An MCP server using Playwright for browser automation and webscrapping

Unique: Exposes Playwright's cookie and storage APIs as MCP tools, supporting both HTTP cookies and JavaScript-accessible storage (localStorage/sessionStorage). Enables state management across page navigations and sessions.

vs others: More complete than simple cookie jar implementations; supports both HTTP cookies and JavaScript storage, with fine-grained control over cookie attributes and domain restrictions.

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 “state persistence and local storage management in views”

Official repo for spec & SDK of MCP Apps protocol - standard for UIs embedded AI chatbots, served by MCP servers

Unique: Provides patterns for both local (browser storage) and server-side state persistence, allowing Views to choose the appropriate strategy based on their needs. State can be scoped to individual Views or shared across multiple Views, enabling flexible state management patterns.

vs others: More flexible than browser-only storage because it supports server-side persistence for sensitive or large state. More explicit than automatic state management because developers control what is persisted and when.

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 “browser state persistence for captcha mitigation”

A Playwright-based Node.js tool that bypasses search engine anti-scraping mechanisms to execute Google searches. Local alternative to SERP APIs with MCP server integration.

Unique: Implements stateful browser persistence at the Playwright level (saving/restoring browser context) rather than HTTP-level cookie management. Preserves full browser state including localStorage and sessionStorage, maintaining Google's session context more effectively than header-based cookie jars.

vs others: More effective CAPTCHA mitigation than stateless SERP APIs or simple cookie rotation; trades state file management complexity for sustained search access without manual intervention.

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 “settings persistence with environment-specific configuration”

Open Source and Free Alternative to ChatGPT Atlas.

Unique: Implements environment-specific persistence (chrome.storage.local vs electron-store) with a unified settings interface, allowing the same configuration logic to work across both deployment targets.

vs others: More flexible than hardcoded configuration, but requires manual credential management compared to OAuth-based approaches.

via “cookie and storage management across sessions”

** (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: Provides unified storage management API covering cookies, localStorage, and sessionStorage with serialization support for session export/import, enabling checkpoint-based workflow resumption and multi-session state persistence beyond simple cookie handling

vs others: More comprehensive than basic cookie management; supports multiple storage types; enables session export/import for resilience vs stateless automation approaches

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

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-storage-management”

** - Playwright MCP server

Unique: Provides context-level storage management through Playwright's native APIs, allowing agents to persist and restore full browser state (cookies, localStorage, sessionStorage) as JSON — enables stateful multi-session workflows without custom serialization.

vs others: More comprehensive than simple cookie handling because it includes localStorage and sessionStorage; more reliable than manual cookie parsing because it uses browser APIs directly.

via “cookie-and-storage-management”

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

Unique: Exposes Puppeteer's cookie and storage APIs as MCP tools, allowing agents to manage session state across multiple page navigations. Enables stateful automation without manual session handling.

vs others: More flexible than hardcoding credentials because it allows dynamic session management; more reliable than HTTP-only session management because it works with JavaScript-based authentication.

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

MCP server: playwright-mcp

Unique: Leverages Playwright's context isolation to provide multi-session support within a single browser instance, reducing memory overhead vs multiple browser processes. Exposes context creation and cookie/storage management as MCP tools, enabling agents to manage sessions programmatically.

vs others: More efficient than spawning multiple browser instances because contexts share a single browser process. More flexible than cookie-jar-based approaches because it also manages localStorage and sessionStorage, which many modern web apps rely on.

via “session-management-for-browser-instances”

MCP server: skyvern

Unique: Implements stateful browser session management within MCP server, allowing agents to maintain context across multiple tool calls without re-initializing browsers. Uses session IDs to reference persistent browser instances and their associated state (cookies, local storage, navigation history).

vs others: Enables stateful multi-step workflows vs. stateless tool calls, reducing latency and supporting authentication-dependent tasks