Skip to main content
Glama
fefergrgrgrg

webdev-mcp

by fefergrgrgrg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to webdev-mcp

No user-submitted related servers found.

    Related Servers

    • Screenshot MCP

      upnorthmedia
      A
      license
      B
      quality
      B
      maintenance
      An MCP server that enables capturing website screenshots with full-page, element-specific, and device-responsive capabilities through natural language commands.
      3
      20 npm
      61
      MIT

    • uisight

      sololabstr
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that provides AI coding agents with real-time visual access to web apps, enabling them to see screens, run accessibility and layout inspections, and interact with pages through a shared live panel.
      1,134 npm
      127
      MIT

    • browser-mcp

      lizhongxuan
      F
      license
      B
      quality
      D
      maintenance
      An MCP server that enables AI coding tools to control a browser for automated actions, UI extraction, network interception, and screenshots.
      23
      1
      -
    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

    B3.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: listScreens enumerates available displays, while takeScreenshot captures a specific screen. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool based on the task.

    Naming Consistency3/5

    The naming is mixed: listScreens uses camelCase, while takeScreenshot uses camelCase but with a different verb style (list vs. take). Both are readable, but they lack a consistent pattern like verb_noun or uniform casing, which could cause minor confusion in a larger set.

    Tool Count2/5

    With only 2 tools, the server feels thin for a web development domain, which typically involves more operations like browser control, DOM manipulation, or network monitoring. This limited scope may restrict agent capabilities and suggests an incomplete tool surface.

    Completeness2/5

    For a webdev-mcp server, the tools only cover screen listing and screenshot capture, leaving significant gaps in web development workflows such as page navigation, element interaction, or performance testing. The surface is severely incomplete for the implied domain, likely causing agent failures in broader tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources