Log inSubmit server
Baepsae logo

Baepsae

Automates iOS Simulator and macOS apps locally through MCP using a TypeScript layer and Swift native bridge.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Baepsae

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "baepsae": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-baepsae@latest"
      ],
      "env": {
        "BAEPSAE_NATIVE_PATH": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 47 tools correctly (12d ago).

Overview

The baepsae MCP server connects MCP clients to local iOS Simulator and macOS app automation on macOS. It combines a TypeScript MCP layer with a Swift native bridge and exposes paste and keyboard tools. Reach for it when an agent needs local input automation on a Mac with Xcode and Simulator available.

Use cases

  • Enter text into an iOS Simulator during local testing
  • Send keyboard input to a macOS application
  • Register a local automation server with an MCP client
  • Test simulator-based workflows from an AI agent

Key features

  • iOS Simulator automation on macOS
  • macOS app automation
  • Paste input tool
  • Keyboard input tool
  • TypeScript MCP layer
  • Swift native bridge

Tools47

What Baepsae lets your agent do. Expand a tool for its parameters.

Verified live~7.7k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

8/8 checks healthy over the last 50d

What it can do

From the 47 tools this server returned when we ran it.

Runs commands · 3Can delete or modify data · 3Makes network requests · 1Read-only tools · 41
Network at startup3 connections
Files written at startupNone
Install scriptspostinstall, prepare
npm provenanceSigned build
Package age250 days
Maintainers1

Observed 2026-10-15 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · mcp-baepsae@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars26Stargazers on the source repository.
npm downloads254Package downloads in the last 30 days.
Last commit7mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed47Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Baepsae works

What baepsae MCP server does

The baepsae MCP server provides local automation for iOS Simulator and macOS applications through the Model Context Protocol. Its currently listed MCP tools are paste and keyboard, allowing an MCP client to send text or keyboard input to the local automation environment.

The project is intended for macOS-based development workflows. It targets iOS Simulator sessions and macOS apps rather than remote devices or cloud-hosted systems. The implementation has two parts: a TypeScript MCP layer that handles the server interface and a Swift native bridge for macOS automation functions.

This setup fits workflows where an agent needs to enter text or control keyboard input while testing or interacting with a simulator or desktop application. It is not a cross-platform MCP server: Linux and Windows are unsupported because the native component depends on macOS frameworks and the Xcode xcrun simctl command.

How it works

The server runs locally and communicates with an MCP client over its configured runtime. The TypeScript portion is started through a local build, an npm package, npx, or another supported JavaScript runtime. When native functionality is available, the Swift bridge handles macOS-specific operations using AppKit, CoreGraphics, and Accessibility frameworks.

The native binary is built as part of the npm installation when Swift is available. A source checkout can also build the TypeScript server and Swift component together. If Swift is unavailable during npm installation, simctl-based functionality can still operate, but native features that depend on the Swift binary may not be available.

Setup and configuration

Use macOS 14 or later, Xcode or Xcode Command Line Tools, Node.js 18 or newer, and Swift 6 or newer. The simplest installation is npx mcp-baepsae@latest; alternatively, install the package globally with npm or clone the repository and run npm install followed by npm run build.

The repository includes an installer that can register the server with supported MCP clients. Its runtime choices include a local Node build, npx, bunx, and a globally installed command. The installer can also preview changes, check dependencies, or remove registrations.

For a local build, BAEPSAE_NATIVE_PATH can point the MCP configuration to the compiled baepsae-native executable. This is useful when the TypeScript server and native binary are built from source.

Tools and capabilities

  • paste: provides a tool for paste-oriented local automation.
  • keyboard: provides a tool for keyboard input automation.
  • iOS Simulator support through macOS and Xcode tooling.
  • macOS application automation through the native Swift bridge.

The baepsae MCP server may require Accessibility permission for input automation. Grant permission to the process that actually launches it, such as the MCP client, terminal, Node runtime, or native binary. After changing permissions, restart the relevant launching process if macOS does not apply the change immediately.

Limitations and notes

The baepsae MCP server requires macOS and does not support Linux or Windows. iOS Simulator use also depends on Xcode or its Command Line Tools. Simulator-specific commands rely on xcrun simctl, while native automation relies on macOS-only frameworks.

Permission failures may come from the host process rather than the target application. Check the MCP client or terminal, the runtime such as node, and baepsae-native when it is invoked directly.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Baepsae

baepsae is an MCP server that connects AI clients to local iOS Simulator and macOS app automation on macOS. Its main exposed tools are paste and keyboard, implemented through a TypeScript MCP layer with a Swift native bridge for native macOS interaction.

Install it with `npx mcp-baepsae@latest`, install it globally with npm, or build it from source. The repository also provides `scripts/install.sh` to register the server with supported MCP clients.

baepsae supports macOS 14 or later only. Its native bridge uses macOS frameworks, and its simulator commands depend on Xcode tooling, so Linux and Windows are not supported.

Grant Accessibility permission to the process that launches baepsae, such as the MCP client, terminal, Node runtime, or native binary. Restart that process after changing the permission if the error continues.

Setup instructions name Claude Code, Claude Desktop, Codex CLI and Desktop, Gemini, Google Antigravity, GitHub Copilot, and OpenCode. The installer or manual MCP commands configure the server for the selected client.

Related MCP servers

All in OS Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewBaepsae AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/baepsae?style=directory)](https://allmcps.com/mcp/baepsae)
HTML Embed
<a href="https://allmcps.com/mcp/baepsae"><img src="https://allmcps.com/api/badge/baepsae?style=directory" alt="Baepsae on AllMCPs" /></a>