Baepsae
概览
作者提供的说明(英文原文)
Local MCP server for iOS Simulator and macOS app automation with a native Swift bridge
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在你的电脑上运行
- 传输方式: stdio
- 分类: 开发者工具
安装
选择你使用的 AI 应用,然后复制设置。
通过 1/2 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
打开电脑版 Claude 应用的设置文件
SettingsDeveloperEdit Config
粘贴这些设置并保存文件
{ "mcpServers": { "baepsae": { "command": "npx", "args": [ "-y", "mcp-baepsae" ] } } }退出 Claude 再重新打开
试一试
用 Baepsae 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Baepsae,或回答中出现 Baepsae 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Baepsae
Baepsae 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
你可以改用这些方式
A · 使用能连接 Baepsae 的应用
- 需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
- 需要先在电脑上安装 Node.js(只需一次)
- 需要先在电脑上安装 Node.js(只需一次)
- 需要先在电脑上安装 Node.js(只需一次)
B · 开发者工具 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
- Sentry✓ ChatGPT
- Front-End Checklist✓ ChatGPT
- Compiler Explorer✓ ChatGPT
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add baepsae -- npx -y mcp-baepsae在 Claude Code 中输入 /mcp
应能看到 Baepsae 在列表中并显示已连接
试一试
用 Baepsae 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Baepsae,或回答中出现 Baepsae 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 Baepsae 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Baepsae,或回答中出现 Baepsae 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 Baepsae 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Baepsae,或回答中出现 Baepsae 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
开发者专用:终端命令和 JSON 设置
安装在电脑上
Claude Code
claude mcp add baepsae -- npx -y mcp-baepsaeClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"baepsae": {
"command": "npx",
"args": [
"-y",
"mcp-baepsae"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"baepsae": {
"command": "npx",
"args": [
"-y",
"mcp-baepsae"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"baepsae": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-baepsae"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月11日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 oozoofrog 验证,该账户拥有此仓库
- ! 注意
仍在维护
代码最后更新于7个月前,已超过 6 个月
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 5763 个服务器的 94%
- 发布到注册中心的时间比此分类中其他 5763 个服务器的 8% 更新
- 基础检查结果等于或优于此分类中其他 5763 个服务器的 11%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Baepsae 安全吗?
它在 2 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于7个月前,最新版本(6.3.0)于7个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
有什么可以替代它?
同一分类中有:REA, Netdata, Front-End Checklist
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Netdata
Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Front-End Checklist
Review frontend code and live pages against 386 quality-gated web development rules.
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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
- Troubleshooting
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 simctlcommands. - 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.
Which process usually needs permission?
- Direct native binary invocation
- Example:
baepsae-native ... - Most relevant entry: the
baepsae-nativebinary 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-nativebinary 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 / right_click with id or label) search in-app content by default. Set all: true to include Simulator chrome UI.
Install
Option A) npm (easiest)
# Run directly without installing
npx mcp-baepsae@latest
Or install globally
npm install -g mcp-baepsae
On macOS, the Swift native binary is built automatically during install. If Swift is not available, the server still works with simctl-based features.
If you plan to use UI inspection or input automation right away, grant Accessibility permission to the terminal / MCP client / runtime process you will actually launch the server with.
Option B) From source
git clone https://github.com/oozoofrog/mcp-baepsae.git
cd mcp-baepsae npm install npm run build
MCP Setup (Recommended)
Use the installer script that calls each client's MCP install flow directly.
bash scripts/install.sh --tool all
Client Matrix
| Client | Install Path | Script Target | Notes |
|---|---|---|---|
| Claude Code | claude mcp add | --tool claude-code | Supports multi-scope via --claude-scope |
| Claude Desktop | claude mcp add --scope user | --tool claude-desktop | User-level registration |
| Codex CLI | codex mcp add | --tool codex-cli | Also works for Codex Desktop settings |
| Codex Desktop | Codex CLI MCP config | --tool codex-desktop | Uses same MCP registry as CLI |
| OpenCode | Global config (~/.config/opencode/opencode.json) | --tool opencode | Auto-updated by installer |
| Gemini | gemini mcp add | --tool gemini | User scope setup |
| Google Antigravity | Gemini-compatible MCP flow | --tool antigravity | Uses Gemini MCP command path |
| GitHub Copilot | copilot or gh copilot session | --tool copilot | Interactive/session-based setup |
For LLM
If you are an LLM agent setting up this MCP server, here is everything you need:
Before trying UI automation tools, remember that Accessibility permission usually belongs to the host/runtime process (
node, terminal, MCP client), not the target app under automation.
Quick start (one command)
# Register baepsae as an MCP server for all supported clients
bash scripts/install.sh --tool all
If you installed via npm instead of cloning the repo, use npx:
# Claude Code
claude mcp add baepsae -- npx -y mcp-baepsae@latest
Codex CLI
codex mcp add baepsae -- npx -y mcp-baepsae@latest
Automation flags
# Preview commands without executing
bash scripts/install.sh --tool all --dry-run
Verify environment and dependencies
bash scripts/install.sh --tool all --doctor
Unregister from all clients
bash scripts/install.sh --tool all --uninstall
Runtime options
The installer supports multiple runtimes via --runtime:
| Flag | Command | When to use |
|---|---|---|
--runtime node (default) | node dist/index.js | Local source build |
--runtime npx | npx -y mcp-baepsae@latest | npm registry, no global install |
--runtime bunx | bunx mcp-baepsae@latest | Bun users |
--runtime global | mcp-baepsae | After npm install -g mcp-baepsae |
Manual Setup (Fallback)
Use this when you do not want to run scripts/install.sh.
Using npx (recommended for npm users)
# Claude Code
claude mcp add baepsae -- npx -y mcp-baepsae@latest
Codex CLI
codex mcp add baepsae -- npx -y mcp-baepsae@latest
Gemini CLI
gemini mcp add --scope user --transport stdio baepsae npx -y mcp-baepsae@latest
When using npx, the relevant Accessibility entry is commonly the spawned node runtime plus the terminal / MCP client that launched it.
Using local build
# Claude Code (project)
claude mcp add --scope project --env="BAEPSAE_NATIVE_PATH=/ABS/PATH/native/.build/release/baepsae-native" baepsae -- node /ABS/PATH/dist/index.js
Codex CLI
codex mcp add baepsae --env BAEPSAE_NATIVE_PATH=/ABS/PATH/native/.build/release/baepsae-native -- node /ABS/PATH/dist/index.js
Gemini CLI
gemini mcp add --scope user --transport stdio -e BAEPSAE_NATIVE_PATH=/ABS/PATH/native/.build/release/baepsae-native baepsae node /ABS/PATH/dist/index.js
When using a local build, check permission on both the runtime (node) and the app that launched it. If you invoke baepsae-native directly for debugging, check permission on the native binary entry itself as well.
Project Structure
- MCP server entry point:
src/index.ts - Tool modules:
src/tools/(info, simulator, ui, input, media, system) - Shared utilities:
src/utils.ts,src/types.ts - Native binary entry point:
native/Sources/main.swift - Native command handlers:
native/Sources/Commands/ - Native binary output:
native/.build/release/baepsae-native - TS tests:
tests/mcp.contract.test.mjs,tests/unit.test.mjs,tests/mcp.real.test.mjs - Swift tests:
native/Tests/BaepsaeNativeTests/
Commands
npm run build # Build TypeScript + native Swift binary
npm test # Contract/integration tests npm run test:real # Real simulator smoke test (requires booted simulator) npm run test:real:preflight # Environment diagnostics only npm run test:real:sim # iOS simulator phases only (skips Phase 4) npm run test:real:mac # macOS Safari phase only npm run verify # test + test:real npm run setup:mcp # Alias for scripts/install.sh
MCP Tool Status
43 tools implemented end-to-end.
Official public MCP surface: unified generic tools
The public API surface is intentionally single-scheme: use unified generic tools with a target argument, rather than sim_* / mac_* names.
| Category | Tools |
|---|---|
| UI | analyze_ui, query_ui, tap, tap_tab, type_text, swipe, scroll, drag_drop, wait_for_ui, detect_dialog, read_ui_value, set_ui_value, read_ui_param, hit_test, enumerate_ui |
| Input | key, key_sequence, key_combo, touch, input_source, list_input_sources |
| Workflow | run_steps |
| System | list_windows, activate_app, screenshot_app, right_click, focus_window, context_menu_action, watch_notification |
| Simulator-only | list_simulators, screenshot, record_video, stream_video, open_url, install_app, launch_app, terminate_app, uninstall_app, button, gesture |
| macOS/system | list_apps, menu_action, get_focused_app, clipboard |
| Utility | baepsae_help, baepsae_version, doctor |
Target routing is explicit in the arguments: udid for simulator, bundleId / appName for macOS.
type_text policy
type_text accepts exactly one input source: text, stdinText, or file.
method: "auto"resolves to:pastefor simulator targetskeyboardfor macOS targetsmethod: "paste"uses the simulator pasteboard for simulator targets and a temporary host clipboard replace/restore flow for macOS targets.method: "keyboard"always types character-by-character.
When paste is used, simulator targets update the simulator pasteboard without touching the host clipboard, while macOS targets temporarily overwrite the host clipboard and restore it after submission. Successful responses report the input source, target kind, requested method, used method, paste transport, and any auto fallback that was applied.
tap_tab policy
tap_tab is semantic-first, geometry-last.
- First it tries actionable descendants exposed under the tab bar.
- If SwiftUI/Simulator does not expose real tab button descendants, it can use a semantic proxy row (for example, app-provided top navigation buttons that map cleanly to the same tabs).
- Only if neither semantic path exists does it fall back to tab-bar geometry.
This matters because SwiftUI TabView in Simulator may expose the tab bar as a generic AXGroup text="Tab Bar" without actionable child buttons.
Usage Examples
Switch tabs by index with semantic-first fallback:
// Prefer this when your app exposes a real tab bar but individual tab buttons
// are not consistently addressable via query_ui/tap selectors. tap_tab({ udid: "...", index: 1, tabCount: 3 })
**Unified simulator app accessibility quickstart (i