shinyprobe
Related Servers
Alternatives to shinyprobe
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI coding agents to visually interact with frontend apps by taking screenshots, clicking elements, reading console logs, and performing visual diffs.7 npm3MIT

agentlaneofficial
FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to drive and inspect isolated app instances across web, iOS, and Android, with tools for reading screens, running interactions, and capturing screenshots or evidence.-- AlicenseNot gradedqualityBmaintenanceEnables MCP agents to drive a running web application by registering schema-validated actions and using a WebSocket relay, with ten ui_* MCP tools for invoking actions, reading state, screenshots, and tab management.MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to open and exercise web applications in an isolated Chromium browser, capture screenshots and runtime/network diagnostics, and run deterministic page checks with linked evidence.121MIT
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to read and modify the state of web apps (Vue, React, Svelte, Pinia, router) through MCP, acting as headless devtools.300 npm123MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to respond to users with live, persistent, interactive web apps served at a single URL that evolve in place as the conversation continues. It exposes UI generation and evolution tools over MCP so agent responses can include clickable buttons and streaming interfaces alongside chat replies.3Apache 2.0
TDQS
Scored across 12 tools
Every tool targets a distinct action: lifecycle (attach, launch_app, stop_app), UI inspection (list_controls), interaction (set_inputs, click, show, upload_file), output reading (read_outputs), and diagnostics (get_errors, screenshot, get_console). No two tools overlap in purpose, making misselection highly unlikely.
All names follow a consistent verb_noun pattern in snake_case (e.g., launch_app, set_inputs, read_outputs). Single verbs like attach and click are still clear and fit the pattern, with no mixed conventions or vague terms.
12 tools is well-scoped for a Shiny app interaction server. Each tool covers a necessary capability for starting, controlling, inspecting, and debugging apps, without redundancy or bloat.
The surface covers the full lifecycle from launch to stop, all common input interactions, output reading, and error/console diagnostics. No obvious gaps exist for typical Shiny testing workflows, making the set self-sufficient.