Happy slice of mcp pizzaMCP.pizza

mcp-baepsae

MCP.Pizza Chef: oozoofrog

mcp-baepsae lets you automate and control the iOS Simulator and macOS apps directly from your AI assistant in apps like Claude Desktop. It runs locally on macOS 14 or later and requires Xcode, iOS Simulator, Node.js, and Swift. After a simple setup involving permission grants and command installs, you can have your assistant interact with simulator apps, inspect UI, and perform input actions without manual effort.

Other

Use This MCP server To

Automate taps and clicks in iOS Simulator apps Inspect UI elements inside iOS Simulator Control macOS apps from my AI assistant Run iOS Simulator commands from Claude Desktop Test app workflows using AI-driven automation Trigger right-click or other input events in Simulator

README

mcp-baepsae

baepsae

Baepsae (Vinous-throated Parrotbill) — A tiny Korean bird. Round, chubby, and constantly hopping around chirping. Known for its grit — even when a little bird tries to keep up with a stork, it never gives up. This project is small too, but it pecks away at your simulators tirelessly.

Local MCP server for iOS Simulator and macOS app automation with a TypeScript MCP layer and a Swift native bridge.

한국어 문서는 README-KR.md를 참고하세요.

Table of Contents

Prerequisites

  • macOS 14+
  • Xcode + iOS Simulator
  • Node.js 18+
  • Swift 6+

Platform Support

Platform Supported Notes
macOS Yes Primary platform. Required for iOS Simulator and Accessibility APIs.
Linux No Native binary depends on AppKit, CoreGraphics, and Accessibility frameworks.
Windows No Native binary depends on AppKit, CoreGraphics, and Accessibility frameworks.

Why macOS only?

The Swift native bridge (baepsae-native) uses macOS-specific frameworks (AppKit, CoreGraphics, Accessibility) to interact with iOS Simulator and macOS applications. These frameworks are not available on Linux or Windows. The TypeScript MCP layer also relies on xcrun simctl, which is part of Xcode Command Line Tools and only available on macOS.

Requirements summary:

  • macOS 14 or later -- required for iOS Simulator automation and Accessibility API access.
  • Xcode or Xcode Command Line Tools -- required for Swift 6+ compilation of the native binary and xcrun simctl commands.
  • Node.js >= 18.0.0 -- required to run the TypeScript MCP server.

Permissions

Accessibility permission is required for UI inspection and input automation features (use unified generic tools such as analyze_ui, tap, right_click).

The important detail is that permission usually needs to be granted to the automation host / runtime process, not to the target app you are automating.

mcp-baepsae FAQ

Can I use this to automate iOS Simulator tasks on my Mac?
Yes — mcp-baepsae lets you control and automate iOS Simulator and macOS apps on macOS 14+ using MCP-compatible clients like Claude Desktop.
Does mcp-baepsae work with Claude Desktop?
Yes — it supports Claude Desktop and other MCP clients that can register this server.
Do I need special permissions to use mcp-baepsae?
Yes — you must grant Accessibility permission to your terminal or MCP client and the runtime process (like node) to enable UI automation features.
Is an API key or account required to use mcp-baepsae?
No — it runs locally on your Mac and does not require external accounts or keys.
How hard is it to set up mcp-baepsae?
Setup is copy-paste-config level — you run simple commands and grant permissions on macOS.
Can I use mcp-baepsae on Windows or Linux?
No — it requires macOS 14+ with Xcode and iOS Simulator due to system dependencies.
What do I need installed before using mcp-baepsae?
macOS 14+, Xcode with iOS Simulator, Node.js 18+, and Swift 6+ are required.