ryubing-mcp
Related Servers
Alternatives to ryubing-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLocal MCP server for automating the Eden Nintendo Switch emulator, enabling control of Switch buttons, touch input, screenshots, and parallel sessions via the control-enabled custom build.27MIT
- AlicenseAqualityBmaintenanceMCP server for the mGBA Game Boy Advance emulator. Read and write GBA memory, inject button presses, take screenshots, save/load state, and step the emulator through a Lua bridge.1822 npm2MIT
- AlicenseCqualityDmaintenanceAn MCP server for real-device Android reversing workflows, wrapping AlgorithmAide config writes, AppSwitch/logList sync, LSPosed scope sync, Frida script injection, and runtime log queries into a stable MCP toolset.2313MIT
- AlicenseNot gradedqualityBmaintenanceLocal MCP server for Android emulator control, exposing tools to get emulator status, inspect UI tree, capture screenshots, and open App settings via Appium and ADB.ISC
- AlicenseNot gradedqualityCmaintenanceLocal MCP server for Android and iOS mobile automation and performance telemetry, enabling device control (screenshot, tap, swipe, input, app launch) and metric collection (CPU, memory, launch time) via ADB, simctl, and WebDriverAgent with SQLite session history.6 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for controlling Hyprland Wayland compositor: screen capture, mouse/keyboard injection, and automation via native Hyprland IPC and wlr protocols.MIT
TDQS
Scored across 10 tools
Each tool targets a distinct resource or action: session management, status, game launch, input methods, screenshot, and logs. There is no overlap, and descriptions clearly distinguish between session status and active game status.
All tools use the 'ryubing_' prefix and mostly follow a verb_noun pattern (e.g., press_buttons, set_sticks, launch_game, list_sessions). The only deviation is ryubing_touch, which is a single verb, but it remains clear and does not cause confusion.
Ten tools is a well-scoped size for an emulator control server, covering session lifecycle, input, diagnostics, and game launching without redundancy. Each tool earns its place.
The tool set covers the core workflow: create session, launch game, control input, take screenshots, read logs, and stop session. Missing advanced features like save states or configuration settings are minor gaps for the apparent purpose.