noracu
Related Servers
Alternatives to noracu
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityCmaintenanceStandalone MCP server for desktop GUI automation on macOS and Windows, exposing a unified tool for accessibility-tree snapshots, input, app control, and browser CDP fast path, driven by any MCP host.-
- AlicenseNot gradedqualityDmaintenanceMCP server that drives the iOS Simulator via accessibility-tree snapshots with stable element refs, enabling LLMs to interactively find, tap, type, and inspect UI elements at sub-200ms latency.25 npmMIT
- AlicenseBqualityDmaintenanceProvides a local MCP bridge for AI assistants to control a Mac by observing screen state and performing actions like mouse movement, clicking, typing, and opening URLs.12MIT
- 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.141MIT
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to control macOS via accessibility and screen recording, providing tools to list apps, observe UI, click, type, press keys, and scroll.MIT
- AlicenseNot gradedqualityBmaintenanceProvides a JSON-RPC computer use runtime for macOS, exposing 7 MCP tools (observe/act/inspect/session/cancel/trace) as image content blocks so external agents like Claude Code, Pi, OpenCode, or Codex CLI can capture screenshots and drive the desktop with clicks, keys, and typing while enforcing session locking, stale-frame protection, and trace redaction server-side.14 npm1MIT
TDQS
Scored across 35 tools
Tools are cleanly separated by platform prefixes (mac_, browser_, phone_) and each targets a distinct action. Minor potential confusion exists among text-entry tools (mac_type vs mac_paste vs mac_key) and gesture tools (phone_scroll vs phone_swipe), but descriptions clearly explain when to use each.
All tool names consistently use snake_case with a platform prefix followed by an action or resource, e.g. browser_navigate, mac_click, phone_screenshot. There are no mixed camelCase or inconsistent verb styles.
The server exposes 35 tools, which is a very large surface for an MCP server. Although they are split across three coherent domains (Mac, browser, iPhone), the total volume increases selection burden and exceeds a comfortably scoped toolset.
Coverage is broad across Mac accessibility/input, browser automation, and iPhone mirroring, with lifecycle tools such as launch, screenshot, inspect, interact, and close. Minor gaps remain, such as explicit browser tab/history management and a dedicated Mac app-launch tool, but core workflows are covered.