Baepsae MCP server
io.github.oozoofrog/baepsae·v6.3.0·26 starsLocal MCP server for iOS Simulator and macOS app automation with a native Swift bridge
26 stars76 downloads/wk
Reviews
Write oneNobody has reviewed Baepsae yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Baepsae tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan27 source files scanned15/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 180 days ago4/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (2)
- mediumnpm install lifecycle script present
install.script - mediumnpm install lifecycle script present
install.scriptpackage.json: … build:ts && npm run build:native", "postinstall": "if [ \"$(uname)\" = \"Darwin\" ]; then…
How Baepsae compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 60/100
- higher than 15% of 48,273 servers
- GitHub stars
- 26
- more than 91% of 28,534 servers
- Downloads a week
- 76
- more than 58% of 11,915 servers with a package
Install Baepsae in Claude Code, Cursor or VS Code
Runs npx -y mcp-baepsae on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add baepsae -- npx -y mcp-baepsae
What the publisher says
From the Baepsae repository's README, as published. We do not edit it. Read it on GitHub
mcp-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
- Platform Support
- Install
- Permissions
- MCP Setup (Recommended)
- Client Matrix
- For LLM
- Manual Setup (Fallback)
- Project Structure
- Commands
- MCP Tool Status
- Usage Examples
Prerequisites
- macOS 14+
- Xcode + iOS Simulator
- Node.js 18+
- Swift 6+
Platform Support
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 analyzeui, tap, rightclick).
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.
Which process usually needs permission?
- Direct native binary invocation
- Example: baepsae-native ...
- Most relevant entry: the baepsae-native binary itself, plus the terminal/shell app that launched it
- Node / npx MCP runtime
- Example: node dist/index.js, npx -y mcp-baepsae@latest
- Most relevant entry: the runtime process (node), plus the terminal or MCP client app that launched it
- Desktop / CLI MCP clients
- Example: Claude Code, Codex CLI/Desktop, Gemini CLI
- Relevant entries can include the MCP client app, the terminal host, and the runtime process depending on launch path
Recommended setup flow
- Open System Settings > Privacy & Security > Accessibility.
- Enable the terminal or MCP client app you actually use.
- Enable the runtime process if listed (node, bun, etc.).
- For direct native invocation, also enable the baepsae-native binary entry if it appears separately.
- If an entry is missing, click + and add it manually.
Important note
After granting permission, the launching process may need to be restarted before macOS applies the change. If the error persists, quit and relaunch the terminal, MCP client, or runtime process that started mcp-baepsae.
For simulator targets, selector-based actions (tap / rightclick with id or label) search in-app content** by default. Set all: true to include Simulator chrome UI.
Install
Option A) npm (easiest)
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Baepsae: common questions
- Is Baepsae MCP server safe?
- With care: it is graded C, so read the findings first (60/100). Read the Baepsae safety report
- How do I install Baepsae?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Baepsae need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Baepsae maintained?
- The last commit was 215 days ago (2026-03-31). The latest release is v6.3.0.
- How does Baepsae compare with other MCP servers?
- safety score 60/100 (higher than 15% of 48,273 servers); github stars 26 (more than 91% of 28,534 servers); downloads a week 76 (more than 58% of 11,915 servers with a package). Full comparison.