原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

MCP Ios

作者:dockndevai版本 0.1.0i★ –i在你的电脑上运行
注册名称io.github.dockndevai/mcp-ios

安装

概览

作者提供的说明(英文原文)

Drive iPhone/iPad via Appium/WebDriverAgent from AI agents — safe-by-default, read-only by default.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 需要你自己填写: IOS_APPIUM_URL, IOS_UDID, IOS_MODE

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "ios": {
      "command": "npx",
      "args": [
        "-y",
        "@dockndevai/mcp-ios"
      ],
      "env": {
        "IOS_APPIUM_URL": "your-value",
        "IOS_UDID": "your-value",
        "IOS_MODE": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add ios --env IOS_APPIUM_URL=your-value --env IOS_UDID=your-value --env IOS_MODE=your-value -- npx -y @dockndevai/mcp-ios

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "ios": {
      "command": "npx",
      "args": [
        "-y",
        "@dockndevai/mcp-ios"
      ],
      "env": {
        "IOS_APPIUM_URL": "your-value",
        "IOS_UDID": "your-value",
        "IOS_MODE": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "ios": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@dockndevai/mcp-ios"
      ],
      "env": {
        "IOS_APPIUM_URL": "your-value",
        "IOS_UDID": "your-value",
        "IOS_MODE": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • IOS_APPIUM_URL env
    Base URL of the running Appium server (default http://127.0.0.1:4723).
  • IOS_UDID env
    Target device UDID.
  • IOS_MODE env
    Access mode: read-only | read-write | admin.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 dockndevai 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 32706 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 32706 个服务器的 62% 更新
  • 基础检查结果等于或优于此分类中其他 32706 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

MCP Ios 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.1.0)于24天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, Kanal Varna — drains, leaks & plumbing (Varna, BG)

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者:formulahendry

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

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

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

在云端运行★ 211前天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

mcp-ios

A Model Context Protocol server to drive an iPhone/iPad — the iOS counterpart to mcp-android. Read this first: iOS is fundamentally more locked down than Android or macOS, so this server takes the only legitimate route to real UI control.

The honest landscape

A stock iPhone does not allow a background app to see and control other apps the way Android's Accessibility service (or macOS) does. Apple's sandbox forbids it. So there is no on-device "iOS-use" agent like the Mac/Android ones. The viable routes, in order of capability:

RouteControl levelNeedsNotes
Appium + WebDriverAgent (XCUITest) ✅ *(this server)*Full UI: tap, type, swipe, read elements, screenshots, launch appsA Mac with Xcode; iPhone connected by USB (or same-network); WDA signed to the deviceThe real "phone-use". Built for automation/QA — perfect for a personal agent on your own device.
ShortcutsRun user-defined actions (set alarm, send message, toggles)Shortcuts app; a URL/x-callback bridgeNo arbitrary UI control, but great for safe, specific actions. Exposed here via run_shortcut.
MDMPolicy/config, app installEnrollmentDevice management, not interactive control.

This server implements the Appium/WDA route: it runs on a Mac, talks to a local Appium server driving WebDriverAgent on the tethered iPhone, and exposes the same safe-by-default MCP shape as the rest of the suite. A set_alarm-style action can also go through Shortcuts (run_shortcut) when the device isn't tethered.

If you want control *from the phone itself with nothing attached*, that isn't possible on iOS — use mcp-android on the Fold 7 for that experience, or the Shortcuts subset here.

Setup (Appium route)

brew install node

npm i -g appium appium driver install xcuitest

Xcode + command line tools installed; sign WebDriverAgent to your device once (Xcode)

Connect the iPhone by USB, Trust the Mac, enable Developer Mode on the device

appium # starts the Appium server (default http://127.0.0.1:4723)

The server creates the XCUITest session lazily on the first tool call, so it starts even before Appium or the device are up — the first call that needs the device returns a clear "start appium / sign WDA / connect the device" message if it can't connect.

Security model

ConcernFlagDefaultEffect
What can the server do?IOS_MODEread-onlyread-only exposes inspection only; read-write adds UI control; admin adds app management. Tools above the mode are never registered.
Which apps are in scope?IOS_APP_ALLOWLIST*(all)*When set, launching/managing any other bundle ID is refused.
Which apps are read-only forever?IOS_PROTECTED_APPScom.apple.Preferences, com.apple.springboardInspectable/launchable but never terminated, reset, or uninstalled.
Can it install/terminate/reset apps?IOS_ALLOW_MANAGEfalseThe admin tools need this and admin mode; otherwise they aren't even advertised.
Interactive confirmation*(automatic)*—terminate_app and reset_app prompt the human to approve the exact bundle ID via MCP elicitation before running; clients without elicitation fall back to the IOS_ALLOW_MANAGE gate.
Preview without touching the deviceIOS_DRY_RUNfalseWrite/admin tools validate + log intent, then return.
Audit trailIOS_AUDIT_LOGtrueEmits a JSON line to stderr per guarded operation.

Connection: IOS_APPIUM_URL (default http://127.0.0.1:4723), IOS_UDID (target device), IOS_BUNDLE_ID (optional default app). See .env.example for all variables and docs/CLIENTS.md for the full per-client install guide.

Tools

Read (read-only+): list_targets, device_info, screenshot, page_source (element tree), current_app, list_apps

Write (read-write+): tap, swipe, input_text, press_button (home/volume), launch_app, open_url, run_shortcut (via Shortcuts)

Admin (admin + IOS_ALLOW_MANAGE): install_app, terminate_app, reset_app (the last two confirm via elicitation; protected apps refused)

screenshot returns an MCP image content block so the agent can see the screen before acting.

Quickstart — add to your agent

Published on npm as @dockndevai/mcp-ios. No clone or build needed — your MCP client runs it on demand with npx. It must run on the Mac with a running Appium server. Start in `read-only` mode.

Claude Code (CLI)

claude mcp add ios -e IOS_APPIUM_URL="http://127.0.0.1:4723" -e IOS_MODE="read-only" -- npx -y @dockndevai/mcp-ios

Claude Desktop · Cursor · Windsurf — same block in claude_desktop_config.json, .cursor/mcp.json, or ~/.codeium/windsurf/mcp_config.json:

{

"mcpServers": { "ios": { "command": "npx", "args": [ "-y", "@dockndevai/mcp-ios" ], "env": { "IOS_APPIUM_URL": "http://127.0.0.1:4723", "IOS_MODE": "read-only" } } } }

VS Code (GitHub Copilot, Agent mode) — in .vscode/mcp.json:

{

"servers": { "ios": { "type": "stdio", "command": "npx", "args": [ "-y", "@dockndevai/mcp-ios" ], "env": { "IOS_APPIUM_URL": "http://127.0.0.1:4723", "IOS_MODE": "read-only" } } } }

Example prompts

  • *"Take a screenshot of my phone and tell me what's on screen."*
  • *"Open Safari and go to news.ycombinator.com."* (needs read-write)
  • *"Run my 'Good morning' Shortcut."* (needs read-write)

Run from source (development)

npm install

npm run build node dist/index.js # with the environment variables set, and appium running

Develop

npm run dev

npm test # security policy + elicitation confirmation (pure; no device needed) npm run typecheck

The policy and elicitation tests are pure and run anywhere. The device-driving path can't be smoke-tested without a Mac + Xcode + signed WDA + a tethered iPhone, so it's built against your real device setup.

Publishing

This server ships a server.json for the official MCP registry and an mcpName for npm ownership validation. See [PUBLISHING.md](PUBLISHING.md) for publishing to npm and listing on the MCP registry, Smithery, Glama, Cursor, and PulseMCP.

License

MIT

问 PopNx