Skip to main content
Glama
zueai

webdev-mcp

by zueai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
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
      36 npm
      61
      MIT

    • Screeny MCP Server

      rohanrav
      A
      license
      Not graded
      quality
      D
      maintenance
      A privacy-first macOS MCP server that enables AI agents to capture screenshots of pre-approved application windows for development and debugging tasks.
      15
      MIT

    • ScreenMonitorMCP

      inkbytefo
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that provides AI with real-time screen monitoring capabilities and UI element intelligence, allowing AI to observe, analyze, and interact with screen content through features like smart clicking and text extraction.
      71
      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

    B3.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: listScreens identifies available screens for capture, while takeScreenshot performs the actual screenshot operation on a specified 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 Consistency2/5

    The naming is inconsistent: listScreens uses camelCase, while takeScreenshot uses camelCase but with a different verb style (list vs. take). Although both are camelCase, the lack of a uniform verb_noun pattern (e.g., list_screens, take_screenshot) and mixed verb conventions reduce predictability and readability.

    Tool Count2/5

    With only 2 tools, the server feels too thin for the web development domain implied by the name 'webdev-mcp'. This limited set lacks essential operations such as screen recording, window management, or other common web development tasks, making it insufficient for comprehensive coverage.

    Completeness2/5

    The tool surface is significantly incomplete for a web development server. While listScreens and takeScreenshot cover basic screenshot functionality, there are obvious gaps like capturing specific windows, recording screen activity, or integrating with web development workflows (e.g., browser automation, code editing). This will likely cause agent failures in broader tasks.

    Resources