Skip to main content
Glama
pedrocoutinhosilva

shinyprobe

by pedrocoutinhosilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to shinyprobe

No user-submitted related servers found.

    Related Servers

    • agent-ui-bridge

      maparham
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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

    • medula

      posva
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to read and modify the state of web apps (Vue, React, Svelte, Pinia, router) through MCP, acting as headless devtools.
      201 npm
      34
      MIT

    • mcp-cdp

      dockndevai
      A
      license
      A
      quality
      B
      maintenance
      Enables agents to inspect and drive Electron or Chrome/Chromium apps via the Chrome DevTools Protocol, exposing DOM snapshots, console logs, network requests, and gated interactions like clicking, typing, and navigating.
      6
      MIT

    • @agent-mcp/react

      A-Launch
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to drive a running React application through typed MCP tools, using the same actions as the UI instead of browser automation.
      10 npm
      1
      Apache 2.0
    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

    A4.1/5.0

    Scored across 12 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources