Skip to main content
Glama
withLinda

chrome-devtools-mcp-fork

by withLinda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to chrome-devtools-mcp-fork

No user-submitted related servers found.

    Related Servers

    • Claude Chrome MCP

      nonsleepr
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation through the Claude Chrome Extension, allowing agents to navigate websites, fill forms, take screenshots, and debug web apps via standard MCP protocols.
      1
      MIT

    • Browser MCP Bridge

      robhicks
      A
      license
      Not graded
      quality
      D
      maintenance
      Bridges browser content, developer tools data, and web page interactions with Claude through MCP. Enables page inspection, DOM analysis, JavaScript execution, console monitoring, network activity tracking, and screenshot capture across multiple browser tabs.
      MIT

    • preview-bridge

      verbalogicproject-creator
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude Code to inspect live browser-preview state, including forms, routes, selections, and focus, and to access runtime errors and user interaction events from any browser tab via read-only MCP tools.
      5
      Apache 2.0

    • gotham-browser

      gotham-os
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to control a real browser using AI for web scraping, competitive intelligence, and UX auditing through the MCP protocol.
      -
    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

    C2.8/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have distinct purposes, but start_chrome, connect_to_browser, and start_chrome_and_connect overlap in domain, though descriptions clarify their roles.

    Naming Consistency5/5

    All tools use consistent snake_case verb_noun pattern (e.g., clear_console, navigate_to_url), with no mixing of conventions.

    Tool Count5/5

    12 tools is well-scoped for Chrome DevTools operations, covering essential actions without being overly numerous.

    Completeness2/5

    Many tools are placeholder implementations, and the set lacks fundamental interactions like executing JavaScript, modifying cookies, or element manipulation, leaving significant gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources