Skip to main content
Glama
betson-g

browser-inspector-mcp

by betson-g
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to browser-inspector-mcp

No user-submitted related servers found.

    Related Servers

    • Visionaire Engine

      mi60dev
      A
      license
      A
      quality
      A
      maintenance
      Eyes for AI coding agents: deterministic MCP server that tells the LLM which CSS rule wins, in which file, on which line — and why. Cascade verdicts, blast radius, interaction timelines, pixel-perfect audits.
      22
      45 npm
      4
      Apache 2.0

    • StyleSpeak

      Patrizzos
      A
      license
      A
      quality
      B
      maintenance
      A companion MCP server that makes CSS legible to AI agents by resolving cascade, tracing properties, and explaining what applies and why before an agent modifies styles.
      2
      47 npm
      MIT

    • bettercss

      ikraamg
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables CSS layout verification and debugging by extracting deterministic, diffable rendered layout from a browser, allowing agents to inspect, explain, and diff CSS changes.
      8 npm
      2
      MIT

    • chrome-devtools-mcp

      zhang77-X
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding assistants to control and inspect a live Chrome browser through Chrome DevTools for automation, debugging, and performance analysis.
      1,026,016 npm
      Apache 2.0

    • Chrome DevTools MCP

      dinesh-nalla-se
      A
      license
      Not graded
      quality
      D
      maintenance
      Lets AI coding assistants control and inspect a live Chrome browser using full Chrome DevTools capabilities for browser automation, debugging, and performance analysis.
      1,026,016 npm
      Apache 2.0
    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.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap between tools, making disambiguation perfect. The tool's description clearly outlines its distinct purpose of inspecting browser pages, with no competing tools to cause misselection.

    Naming Consistency5/5

    Since there is only one tool, naming consistency is inherently perfect. The tool name 'browser_inspect' follows a clear verb_noun pattern, and with no other tools to compare, there are no deviations or inconsistencies in naming conventions.

    Tool Count2/5

    A single tool is too few for a server named 'browser-inspector-mcp', which suggests a broader scope for browser inspection tasks. While the tool covers multiple actions (dom, styles, screenshot, diff), the server feels thin and under-scoped, as typical inspection domains might benefit from more specialized or separate tools.

    Completeness3/5

    The tool provides core inspection actions (dom, styles, screenshot, diff), but there are notable gaps for a browser inspector, such as missing tools for network monitoring, JavaScript debugging, performance analysis, or element interaction. This limits the server's ability to fully cover browser inspection workflows, though the included actions are useful for basic CSS and DOM tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources