Skip to main content
Glama
Myestery

Browser CDP MCP Server

by Myestery
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Browser CDP MCP Server

No user-submitted related servers found.

    Related Servers

    • superpowers-chrome

      obra
      A
      license
      A
      quality
      A
      maintenance
      Enables direct browser control via Chrome DevTools Protocol, supporting navigation, interaction, content extraction, and screenshots through a single MCP tool.
      1
      355
      MIT

    • BrowserUse

      YisRime
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to control Chrome/Edge browsers via CDP, including page navigation, element interaction, snapshots, network debugging, script execution, and performance tracing.
      AGPL 3.0

    • browser-devtools-mcp

      kikcmime
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables reading browser DevTools data (tabs, console errors, network requests, screenshots, DOM, CSS, JS execution) via Chrome DevTools Protocol.
      3,667 npm
      MIT

    • Fast Browser MCP

      kqlio67
      A
      license
      C
      quality
      A
      maintenance
      Enables AI agents and developers to automate real Chrome/Chromium browsers through the Chrome DevTools Protocol, with token-efficient snapshots, multi-action batching, shadow DOM traversal, system-page control, extension management, and network/WebSocket inspection.
      64
      MIT
    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

    D1.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: cdp_send appears to send commands to the Chrome DevTools Protocol, close_browser terminates the browser session, get_url retrieves the current URL, and screenshot captures a visual snapshot. There is no overlap in functionality between these tools.

    Naming Consistency3/5

    The naming is mixed: cdp_send uses a prefix-based convention, while close_browser, get_url, and screenshot follow a verb_noun pattern. This inconsistency reduces predictability, but all names are still readable and descriptive of their functions.

    Tool Count3/5

    With only 4 tools, the set feels thin for a browser automation server, lacking common operations like navigation, clicking, or input handling. However, the tools cover basic session management and inspection, making it borderline appropriate for minimal use cases.

    Completeness2/5

    The toolset is severely incomplete for browser automation: it lacks essential actions like navigate, click, type, or evaluate JavaScript, and there is no coverage for interacting with page elements or handling events. This will cause significant agent failures in typical browsing tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources