Skip to main content
Glama
Yan-Vi

easy-spec-mcp

by Yan-Vi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to easy-spec-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-browser

      souhailmerroun-recyclebin
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes Playwright browser automation as MCP tools, enabling AI assistants to control a real browser tab-by-tab for form filling, navigation, and more, while preserving the user's active session.
      -

    • Tabryn

      idugeni
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects AI agents to your Chrome browser via MCP, enabling real-time control of existing tabs, sessions, and application state for development workflows.
      MIT

    • jev-browser

      tontoko
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables browser automation through MCP with native Playwright operations, deterministic assertions, and natural-language grounded actions, structured extraction, and bounded agent workflows over live page elements.
      7
      Apache 2.0

    • BrowserPilot

      soulxyz
      F
      license
      B
      quality
      D
      maintenance
      Enables AI to control browsers via natural language for web automation, testing, and data scraping. Supports Chrome-based browsers and integrates with any MCP-compatible AI tool.
      17
      2
      -
    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.2/5.0

    Scored across 77 tools

    Disambiguation4/5

    Most tools are clearly separated by entity type (flow, scenario, page object, util, suite) and action (list, get, create, delete, set, live_*). A few closely related live-execution tools could require careful reading, but descriptions generally make each one's purpose distinct.

    Naming Consistency4/5

    The naming largely follows a consistent snake_case verb_noun pattern such as list_flows, create_page_object, set_util_body, and live_get_run. Minor deviations like add_to_suite and connect_panel are still readable and do not seriously break the overall convention.

    Tool Count1/5

    With 77 tools, the surface is extremely large and far outside the typical well-scoped range. Even for a complex automation domain, this many distinct endpoints creates a heavy cognitive and discovery burden for an agent.

    Completeness4/5

    The toolkit covers a broad lifecycle: create/list/get/update/delete for flows, scenarios, page objects, and utils, plus live execution, run inspection, and suite management. Some possible lifecycle gaps exist, such as no explicit suite-entry removal tool, but the domain is otherwise richly covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources