Skip to main content
Glama
680,744 tools. Updated 2026-10-20 11:21

"How to use personal browser with cookies enabled" matching MCP tools:

  • Close the currently active browser session and free up resources like tabs, cookies, and history. Safe to call when no session is open.
    MIT
  • Close the active browser session after automation finishes to release resources and clear tabs, cookies, and history. Safe to call even when no session exists.
    MIT
  • Open a new browser tab with a separate session, cookies, and login state for isolated browsing contexts. Provide a unique tab name and URL, and optionally inject pre-authenticated cookies before navigation.
    AGPL 3.0
  • Inspect, clear, save, and load browser cookies to manage session state, preserve logins between runs, restore saved sessions, or reset website state during testing.
    MIT
  • Inspect, clear, save, or load browser cookies to manage session state, preserve logins between runs, or reset website state during testing.
    MIT
  • Automates browser warmup to collect cookies for later scrapes. Use when manual seeding isn't possible, but strict WAFs may cause failure.
    -

Matching MCP Servers

Matching MCP Connectors

  • Programmatic headless browser sessions: create, interact, browse, and extract - rendered in a real

  • Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.

  • Manage Chromium cookies for automated browser testing: read, set, delete, or clear cookies, including HttpOnly ones, to seed authenticated sessions or verify cookie state.
    Apache 2.0
  • Permanently remove saved Cloud Browser settings and browser state, including cookies and storage. Stop any active session using them first, or the deletion fails.
    MIT
  • Set one or more cookies in an active browser session to preserve login, preferences, or tracking state before scraping. Provide session_id and cookie name/value pairs.
    MIT
  • Clear captured HTTP(S) request history and cached response bodies for a clean network capture window. Use before reproducing an action to get fresh evidence, while leaving cookies and browser state untouched.
    Apache 2.0
    Destructive
  • Delete the persistent browser profile to wipe cookies, localStorage, and history. This restores a clean slate for new automation sessions after the browser is closed.
    MIT
  • Close the active browser session and quit its browser when automation is done, preventing browsers from being left open. Cookies, login state, and open pages are discarded.
    MIT
  • End the active browser session and free its resources, including tabs, cookies, and page state. Use when automation is complete or to reset the browser before starting a new session.
    MIT
  • End the active browser session and free its resources, including tabs, cookies, and page state. Use when automation is complete; start a new session to continue.
    MIT
  • Prepare Chrome or Edge for automated agent use by creating a dedicated profile and copying cookies, so the agent opens the browser with your sites logged in.
    GPL 3.0
  • Inspect, clear, save, or restore browser cookies to manage login sessions and reset site state. Use get_all, clear, save, or load actions to preserve or restore session cookies between runs.
    MIT
  • Inspect, clear, save, or load browser cookies to manage session state, preserve logins between runs, or reset website state during testing.
    MIT