playdate-mcp
Related Servers
Alternatives to playdate-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceFirst-party MCP server and CLI for Xcode and iOS Simulator automation. Enables control of Xcode and iOS Simulator via MCP tools for tasks like building, testing, and automation.35 npm1MIT
- AlicenseNot gradedqualityCmaintenanceLocal MCP server for iOS Simulator and macOS app automation with a TypeScript MCP layer and Swift native bridge. Enables UI inspection, input automation, and simulator control through unified generic tools.44 npm26MIT
- AlicenseNot gradedqualityFmaintenanceAn MCP server to control iOS Simulators.12 npm53MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI to control iOS simulators through the MCP protocol. Supports device management, UI automation, and network interception including screenshot capture, text input, and HTTP request mocking.-
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with Xcode build tools, iOS Simulator, and Apple notarization services.7 npm5MIT
- AlicenseBqualityCmaintenanceEnables local MCP clients to run Sailfish OS device, SDK, OBS, and Android/AppSupport development workflows via typed tools for SSH access, screenshots, touch injection, builds, logs, services, and repository checks.35BSD Zero Clause
TDQS
Scored across 15 tools
Most control tools target distinct inputs or actions, but playdate_status and playdate_inject heavily overlap in finding the Simulator and ensuring the agent is available. playdate_run and playdate_load are also closely related, though descriptions clarify their build/no-build distinction.
All tools share the playdate_ prefix and mostly use clear verb-first names like playdate_set_crank and playdate_capture_screenshot. Minor deviations like playdate_status and playdate_toolbar are noun-style rather than verb-style, but the overall pattern remains readable and predictable.
Fifteen tools is at the upper edge of well-scoped for a simulator-control server, and each tool covers a meaningful action or input surface. The redundant playdate_inject and broad playdate_toolbar add slight bulk but do not make the set feel bloated.
The tool surface covers the core Simulator lifecycle—build/run/load, restart, pause, status—plus key input methods, volume, lock state, screenshots, and recording. Minor gaps exist around advanced Simulator state or explicit simulator selection, but common workflows are fully supported.