Skip to main content
Glama
k-l-lambda

chrome-cookies-mcp

by k-l-lambda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to chrome-cookies-mcp

No user-submitted related servers found.

    Related Servers

    • Chrome Tools MCP Server

      nicholmikey
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools for interacting with Chrome through its DevTools Protocol, enabling remote control of Chrome tabs to execute JavaScript, capture screenshots, monitor network traffic, and more.
      29 npm
      53
      MIT

    • chrome-bridge-mcp

      ShalomObongo
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets coding tools drive an already-running, logged-in Chrome using its real profile and cookies, providing tools for tabs, navigation, clicks, typing, and more via CDP.
      79 npm
      MIT

    • paparazzi

      nicksenap
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects to your browser to capture screenshots, inspect console logs, network requests, and more via Chrome DevTools Protocol.
      4 npm
      2
      MIT

    • mcp-chromium-cdp

      duquesnay
      A
      license
      A
      quality
      D
      maintenance
      MCP server for controlling Chromium/Chrome via Chrome DevTools Protocol. Supports cross-platform automation, auto-launch, and automatic reconnection.
      25
      1
      MIT

    • MCP Browser Logger

      tao-Lionel
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that captures browser console logs and network requests via the Chrome DevTools Protocol. It allows users to monitor real-time logs, inspect network traffic, and execute JavaScript code directly in the browser context.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: get_cookies retrieves cookies for a given domain, while list_domains enumerates available domains. There is no ambiguity or overlap.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern in snake_case (get_cookies, list_domains), making the naming predictable and clear.

    Tool Count5/5

    With only two tools, the set is perfectly scoped for the narrow domain of reading Chrome cookies. Each tool serves a distinct, necessary function without excess or deficiency.

    Completeness5/5

    For a read-only cookie retrieval tool, the combination of listing domains and fetching cookies covers the essential workflow completely. No gaps are apparent for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources