Skip to main content
Glama
Yuyang-Hou

WebMCP Script

by Yuyang-Hou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to WebMCP Script

No user-submitted related servers found.

    Related Servers

    • WebMCP

      lossefanya
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables browser-based AI chat interfaces to use local MCP tools by injecting a tool-call protocol into the page and executing approved filesystem, shell, and downstream MCP tool calls from a local daemon.
      145
      MIT

    • ps3d

      sagar25-Code-it
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI hosts to interact with a browser CAD workbench through model-neutral local stdio or authenticated remote MCP tools, supporting command discovery, design-health analysis, and scoped previews while never reading local files or taking over open sessions.
      MIT

    • veriloop

      arvindcr4
      A
      license
      A
      quality
      C
      maintenance
      Exposes a verified tool registry (calculator, sandboxed file read, web fetch) over MCP stdio, enabling any MCP-capable client to reuse the same tools from the inspectable ReAct loop.
      3
      MIT

    • llm-wiki-chrome

      nvk
      F
      license
      B
      quality
      A
      maintenance
      MCP server for the LLM Wiki Chrome extension that exposes bounded browser automation tools (shared tabs, accessibility snapshots, screenshots, clicks, typing, etc.) with explicit user consent and strict typing, enabling local agents to interact with specific web pages via a native messaging relay.
      34
      2
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 13 tools

    Disambiguation4/5

    The set splits into two clear clusters: browser/page tools (inspect_page, describe_tool, call_tool, visit_page) and script/native lifecycle tools, each with a distinct verb. The only real overlap is between 'pages' and 'inspect_page', which both surface tool summaries, though the descriptions distinguish list-vs-inspect.

    Naming Consistency3/5

    All names use snake_case, but the convention is mixed: verb_noun (inspect_page, call_tool, describe_tool), a bare noun (pages), noun_noun (connection_info), and two prefix-grouped families (script_*, native_*). Consistent casing makes it readable, but there is no single predictable pattern.

    Tool Count4/5

    13 tools sits comfortably in the well-scoped 3-15 range, and the granular split of the native workflow (native_build, native_select_build, native_launch) reflects real, distinct steps. Slightly heavy but each tool earns its place.

    Completeness4/5

    Coverage of the script lifecycle is strong: connection setup, page discovery, schema inspection, invocation, plus script status/preview/import/change and native build/select/launch. Minor gaps like no direct script authoring or connection teardown, but core workflows are fully covered.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources