sudo-meow-mcp
Related Servers
Alternatives to sudo-meow-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceAn MCP server that enables AI assistants to build, test, and debug Tauri v2 applications through UI automation (screenshots, clicks, typing, element finding), IPC monitoring, log streaming, and mobile device management.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for safety-first automation and app QA, exposing deterministic tools to control graphical apps, browsers, terminals, Android devices, VMs, and SSH hosts.2 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server that allows AI agents to interact with and debug Tauri applications through screenshots, DOM access, input simulation, and more.1,412 npm109MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to automate and test Tauri desktop applications through the Model Context Protocol. It provides tools for app management, UI interaction, and state inspection across multiple platforms without requiring CDP dependencies.141,412 npm1MIT
- AlicenseAqualityAmaintenanceMCP server exposing Windows desktop UI Automation as tools for AI agents, enabling automated interaction with Windows applications via Appium.8719 npm1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceGives AI agents and MCP clients direct control over native desktop apps, Chrome/Electron browsers, and Android devices with screenshots, OCR, accessibility-based element lookup, input simulation, window management, CDP, and ADB in one local server.134MIT
TDQS
Scored across 5 tools
Each tool has a distinct purpose: state snapshot, transitions, event triggering, history, and console logs. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (get_current_state, get_available_transitions, trigger_event, get_state_history, read_console_logs).
Five tools is ideal for debugging a state machine and Pomodoro timer, covering reading state, available transitions, event triggering, history, and console logs without unnecessary duplication.
The tool surface covers the main debugging needs (state, transitions, events, history, logs). Minor gaps exist (e.g., no reset or clear functionality), but these are acceptable for a debug server.