Baepsae

Name: Baepsae
Author: oozoofrog

by oozoofrogversion 6.3.0i★ –iRuns on your computer

Registry nameio.github.oozoofrog/baepsae

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "baepsae": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-baepsae"
      ]
    }
  }
}

Run this in your terminal

claude mcp add baepsae -- npx -y mcp-baepsae

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "baepsae": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-baepsae"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "baepsae": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-baepsae"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account oozoofrog, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32537 servers in this category
Published to the registry more recently than 5% of the other 32537 servers in this category
Basic checks equal to or better than 100% of the other 32537 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Baepsae safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (6.3.0) reached the registry 7 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, TF Rooms

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

TF Rooms

by tfrooms.com

Live room availability, rates and stay quotes for 12 New Leaf motels in Twin Falls, Idaho.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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를 참고하세요.

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 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.

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 / 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:
paste for simulator targets
keyboard for macOS targets
method: "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

Only the beginning is shown; read the rest in the repo

Baepsae

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

TF Rooms

README from the maker

mcp-baepsae

Table of Contents

Prerequisites

Platform Support

Permissions

Which process usually needs permission?

Recommended setup flow

Important note

Install

Option A) npm (easiest)

Or install globally

Option B) From source

MCP Setup (Recommended)

Client Matrix

For LLM

Quick start (one command)

Codex CLI

Automation flags

Verify environment and dependencies

Unregister from all clients

Runtime options

Manual Setup (Fallback)

Using npx (recommended for npm users)

Codex CLI

Gemini CLI

Using local build

Codex CLI

Gemini CLI

Project Structure

Commands

MCP Tool Status

Official public MCP surface: unified generic tools

type_text policy

tap_tab policy

Usage Examples

`type_text` policy

`tap_tab` policy