Skip to main content
Glama
MarlonJD

web-debug-mcp

by MarlonJD
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to web-debug-mcp

No user-submitted related servers found.

    Related Servers

    • Chrome Course MCP

      CrispyW0nton
      F
      license
      B
      quality
      D
      maintenance
      A local MCP server that enables Codex to inspect and interact with Chrome tabs through the Chrome DevTools Protocol, primarily for collecting authorized Brightspace course materials into local folders.
      16
      -

    • Glassbox

      adihebbalae
      A
      license
      Not graded
      quality
      B
      maintenance
      An instrumented local browser daemon MCP server that lets coding agents verify UIs in one call, with console, network, layout, accessibility, and coverage checks, plus debugging tools. It provides named isolated sessions and a CLI+MCP duality for the same verbs.
      MIT

    • js-reverse-mcp

      1600822305
      A
      license
      Not graded
      quality
      D
      maintenance
      A Chrome DevTools Protocol-based MCP server that enables AI coding assistants to control browsers for JavaScript debugging, reverse engineering, web scraping, and API debugging.
      822 npm
      1
      Apache 2.0
    • orchords-web-pilot by ORCHORDS

      orchords-web-pilotofficial

      ORCHORDS
      F
      license
      A
      quality
      B
      maintenance
      Enables coding agents to drive a real Playwright-backed browser session, navigating, observing, interacting, and capturing proof on web pages via MCP tools across stdio and Streamable HTTP transports.
      15
      2
      -

    • browser-for-ai

      icueth
      A
      license
      B
      quality
      C
      maintenance
      A CDP-native MCP server that lets AI agents drive a real Chrome browser with deep network/console inspection, robust page interaction, and the ability to reverse-engineer a site's API flow into runnable code with dependency chaining and replay verification.
      52
      218 npm
      4
      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

    A3.7/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct step in the web debugging workflow: sessions, browser actions, breakpoints, evaluate, replay, reproduction, and verification. Even related tools like repro_record and fix_verify are clearly separated by their record/verify roles, and debug_control vs browser_action are unambiguous.

    Naming Consistency5/5

    All names follow a uniform 'web_<domain>_<action>' snake_case pattern, with the action being a verb (start, close, record, verify). The only mild exception is web_session_status and web_browser_action, but both still fit the scheme as noun-as-verb conventions, so the set feels highly predictable.

    Tool Count5/5

    At 13 tools, the set is appropriately scoped for a comprehensive web debugging suite. Each tool fills a distinct role and there is no redundant overlap or fluff that would justify trimming or expanding.

    Completeness4/5

    The tool surface covers the core debugging lifecycle: record, capture, start/stop sessions, interact, set breakpoints, jump, edit live state, and verify. Minor omissions like remove breakpoint, pause on exceptions, or network inspection leave small gaps, but the main workstreams (reproduce, debug, fix, verify) are all represented.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources