plonk-mcp
Related Servers
Alternatives to plonk-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenancemacOS automation for AI assistants: 17 typed tools for window management, application menus, keyboard input, clipboard, browser tabs, screenshots, displays and Apple Shortcuts, driven through AppleScript and JXA. Menu clicks are self-correcting — a wrong item returns the actual menu contents so the model can retry with the right one.1728 npm12MIT
- AlicenseNot gradedqualityDmaintenanceProvides native macOS desktop automation for AI agents, enabling screen capture, mouse/keyboard control, window management, and iOS/Android simulator control in both foreground and background modes without focus stealing.3MIT
- AlicenseNot gradedqualityAmaintenanceLets AI agents see and control desktop applications through the accessibility layer, enabling clicking, typing, scrolling, dragging, and window/app management across macOS, Windows, and Linux entirely on the local machine.14MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with macOS windows through yabai, providing window listing organized by Spaces and screenshot capture capabilities.2MIT
- AlicenseNot gradedqualityAmaintenanceA local autonomous AI agent that watches your screen, understands the visual layout, and executes native OS commands (clicking, typing) without cloud APIs.16MIT

ToolPiperofficial
AlicenseNot gradedqualityCmaintenance426+ MCP tools for macOS, all on-device — local AI inference (llama.cpp on Metal), voice, vision OCR, local RAG, browser automation, and ~140 system actions across 26 macOS domains. Nothing leaves your Mac.2MIT
TDQS
Scored across 22 tools
Most tools map cleanly to distinct actions (window layout vs zones vs screenshots vs awake vs updates), and descriptions carefully steer between look-alikes like extract_text, take_screenshot, and measure_screen. However, the three legacy aliases (save_layout/apply_saved_layout/delete_layout) are genuine duplicates of workspace tools, so an agent could pick the wrong one despite the 'legacy' warnings.
Every tool follows the same snake_case verb_noun convention (save_workspace, delete_zone_set, check_for_update), with the object as a noun and a clear action verb. Even legacy aliases comply with the pattern. No camelCase or inconsistent styles are present.
22 tools is on the heavy side, and three are pure legacy duplicates that add surface area without new capability. The breadth is defensible for a desktop-management utility covering windows, zones, screenshots, OCR, measure, keep-awake, updates, and agents, but it exceeds the ideal 3-15 range.
The tool surface covers the main lifecycles well: workspaces can be saved/launched/deleted, zone sets created/assigned/deleted, app rules set/cleared, and screenshots can be captured, annotated, OCR'd, and measured. Minor gaps remain—there is no explicit programmatic way to stop a keep-awake session, and update/agent tools are thin—but nothing likely to strand an agent.