Baepsae vs MCP Osascript
A side-by-side look at the Baepsae and MCP Osascript MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Baepsae for os automation work as a local process; choose MCP Osascript for os automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Baepsae when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
BAEPSAE_NATIVE_PATH. - You want tools like
baepsae_help, baepsae_version, doctor.
Choose MCP Osascript when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
check_permissions, run_osascript, get_clipboard.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 59/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | BAEPSAE_NATIVE_PATH | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 26 | 12 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 47 | 18 |
| Full listing | View Baepsae | View MCP Osascript |
Tools & capabilities
Baepsae tools 47
baepsae_helpShow help. Optionally pass subcommand name for compatibility reference.baepsae_versionShow server and native binary versions.doctorRun readiness self-checks for host process, parent process, native binary, booted simulator availability, and accessibility permission.list_appsList running macOS applications with their bundle IDs.get_focused_appGet information about the currently focused macOS app.list_simulatorsList available simulators using simctl.open_urlOpen a URL in the simulator (e.g. Safari or deep link).install_appInstall an app (.app, .ipa) on the simulator.uninstall_appUninstall an app from the simulator.launch_appLaunch an installed app on the simulator.terminate_appTerminate a running app on the simulator.analyze_uiDescribe app UI hierarchy. Works with both simulator (udid) and macOS (bundleId/appName) targets.- +35 more on the listing page
MCP Osascript tools 18
check_permissionsReport which permissions are granted and what each unlocksrun_osascriptExecute any AppleScript or JXA scriptget_clipboardRead clipboard as textset_clipboardWrite text to clipboardsend_notificationShow macOS notification banneropen_urlOpen URL in browser (http/https/mailto only)open_appLaunch or bring app to frontget_frontmost_appGet active app name + bundle IDget_browser_tabsList tabs in Safari, Chrome, or Arctype_textType text into active app (max 500 chars)press_keyPress key with modifiers (cmd+c, return, f5)manage_windowsList / move / resize / minimize / fullscreen / close- +6 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Baepsae
{
"mcpServers": {
"baepsae": {
"command": "npx",
"args": [
"-y",
"mcp-baepsae@latest"
],
"env": {
"BAEPSAE_NATIVE_PATH": "YOUR_BAEPSAE_NATIVE_PATH_HERE"
}
}
}
}
MCP Osascript
{
"mcpServers": {
"mcp-osascript": {
"command": "npx",
"args": [
"-y",
"mcp-osascript"
]
}
}
}
Frequently asked questions
Baepsae is categorized under OS Automation and uses a local stdio subprocess. MCP Osascript belongs to OS Automation and uses a local stdio subprocess. Pick Baepsae for os automation work and MCP Osascript for os automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Baepsae has no declared pricing — check the project's own site. MCP Osascript has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add baepsae and mcp-osascript as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Baepsae has a quality signal of 59/100 (Good) with 2 views, 0 installs and 26 GitHub stars. MCP Osascript has 52/100 (Good) with 1 views, 0 installs and 12 GitHub stars.