WebMCP Script
Related Servers
Alternatives to WebMCP Script
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables an AI agent to run local tools on the user's own machine via stdio, including command execution, workspace file read/write, and system status checks.52MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to observe foreground browser viewports, read filtered page evidence, and run guarded reusable site-pack procedures through the same local runtime as the CLI.MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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.560 npmAGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables 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.2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceExposes 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
- AlicenseAqualityBmaintenanceLets 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.213 npmMIT
TDQS
Scored across 13 tools
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.
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.
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.
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.