Skip to main content
Glama

Related Servers

Alternatives to WebMCP Script

No user-submitted related servers found.

    Related Servers

    • 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.
      225 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables compatible agents to call registered local tools and read resources through one stdio server, including harness preparation, knowledge search and document management, memory retention/recall, correction proposals, advisory decisions, tool/skill discovery, and log/source inspection.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a governed, OAuth-gated set of tools that let web-based AI chat clients read and write local files, run whitelisted shell commands, search code, inspect Git and SQLite data, automate browsers and DevTools, and manage background jobs, localhost services, clipboard, notifications, and Postman on the user's own machine.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI clients discover available API operation schemas and write sandboxed JavaScript that chains those operations together, returning only the results they need. Supports stdio and Streamable HTTP transports.
      280 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes a governed, OAuth-gated suite of 38 tools that let web AI clients work directly on your machine: reading, writing, and editing files, running whitelisted shell commands, searching, Git, SQLite, browser automation, DevTools debugging, background tasks, localhost/LAN fetches, clipboard, notifications, port management, and Postman control.
      MIT

    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

    ActivitySlowing
    ResponsivenessUnresponsive