Skip to main content
Glama
605,578 tools. Updated 2026-09-24 01:32

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

  • Launch a persistent browser session that remains active across automation steps, preserving cookies, tabs, and page state until explicitly closed.
    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
  • Close the currently active browser session and free up resources like tabs, cookies, and history. Safe to call when no session is open.
    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, or load browser cookies to manage session state, preserve logins between runs, or reset website state during testing.
    MIT
  • 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

Matching MCP Servers

  • A
    license
    A
    quality
    B
    maintenance
    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.
    22
    56 npm
    2
    Apache 2.0

Matching MCP Connectors

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

  • Read and triage bug reports captured by Session Replay for your verified domains.

  • Stop an active browser session to halt billing and preserve profile cookies and logins. Use it when tasks are complete or to clean up leaked sessions.
    MIT
    Destructive
  • Close and discard an unneeded in-memory browser session, clearing its document and history while keeping persistent cookies. Specify a session ID to target that session; otherwise, the active session closes.
    MIT
    Destructive
  • Save browser session state to a JSON file to reuse authentication across sessions, or load and clear saved sessions. Useful for skipping re-login and transferring credentials.
    MIT
  • Clear saved session cookies to log out or remove invalid session data. After clearing, run session_refresh to restore a valid session.
    MIT
  • Retrieve browser cookies with domain, path, and secure flag. Use a URL to filter cookies; otherwise, all cookies are returned, including sensitive session tokens.
    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
  • Start a persistent browser session before automating web tasks, maintaining cookies, tabs, and state across subsequent interactions via CDP.
    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
  • 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