Tapp

Name: Tapp
Author: aarwitz

作者：aarwitz版本 0.35.1i★ –i在你的电脑上运行

注册名称io.github.aarwitz/tapp

安装

概览

作者提供的说明（英文原文）

Test iOS, Android, and web apps with agent exploration, replayable flows, and CI gates.

PopNx MCP 的三大支柱

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

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

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

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

安装

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

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

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

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

{
  "mcpServers": {
    "tapp": {
      "command": "npx",
      "args": [
        "-y",
        "@aarwitz/tapp"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add tapp -- npx -y @aarwitz/tapp

在 Cursor 中打开

或者自己复制设置

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

{
  "mcpServers": {
    "tapp": {
      "command": "npx",
      "args": [
        "-y",
        "@aarwitz/tapp"
      ]
    }
  }
}

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

在 VS Code 中打开

或者自己复制设置

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

{
  "servers": {
    "tapp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@aarwitz/tapp"
      ]
    }
  }
}

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

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

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

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

它能做什么

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

基础检查i

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

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 aarwitz 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

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

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

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

常见问题

Tapp 安全吗？

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

它需要哪些密钥或代码？

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

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

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

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.35.1）于5天前进入注册中心。

哪些应用可以使用它？

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

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Fomu MCP

替代选择

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

如何看卡片：★ 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昨天更新

安装

Fomu MCP

作者：gabrielmahia

Kenya government form guides: checklists, draft letters, eCitizen, Huduma, timelines. Sample data.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

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

Tapp

Tapp lets coding agents verify UI changes on real iOS, Android, and web surfaces, then turns reviewed proof into deterministic CI checks. It can inspect and drive screens, explore for technical failures, and save important journeys as replayable tests.

Exploration reports findings, coverage, evidence, and limits. Only the repository-connected gate returns pass, fail, or inconclusive. Tapp does not turn an autonomous crawl into a subjective "ship-ready" score.

Real evidence, not a mock: this public DemoApp run reached the requested iOS surface in three observed route actions. Watch 45 seconds of autonomous exploration or inspect a complete sanitized web evidence report.

Supported targets:

Target app	Runtime
iOS	Simulator on macOS with Xcode; driven through XCUITest and accessibility
Android	Connected emulator or device with `adb`; driven through UIAutomator
Web	Owned browser app in Playwright Chromium
macOS desktop	Any `.app` on a Mac, driven through the Accessibility API; needs the Accessibility permission (`tapp doctor` says how)
Windows desktop	WPF, WinForms, and WinUI apps through Windows UI Automation — early runs are set up through the pilot

Windows hosts Android and web testing when their prerequisites are installed, and is the home of the Windows desktop target.

Give Tapp to your coding agent

After setup, the whole user prompt is:

Use Tapp to test this app.

The official skill teaches the agent to choose the smallest useful operation, handle repositories with multiple app targets, inspect visual evidence, and keep exploration observations separate from gate decisions.

Claude Code, Codex, Cursor, Copilot, and other Agent Skills clients (recommended):

npx -y skills add aarwitz/tapp --skill tapp

This installs the open Agent Skills workflow into the current project and lets the agent run the npm CLI directly. Inspecting, focused evidence, autonomous exploration, deterministic replay, and gating need no MCP server, plugin, account, API key, global Tapp install, or pasted prompt block. Add -g for a user-wide install, or --agent claude-code, --agent codex, and similar selectors to constrain the clients. Start or restart the agent from the application repository and use the short prompt above.

Claude Code — optional enhanced skill and MCP tools:

claude plugin marketplace add aarwitz/tapp

claude plugin install tapp@tapp

The plugin bundles the same tapp Agent Skill with the matching npm-backed MCP server. Add it when you want inline screenshot results or when the agent must interactively tap, type, and record an arbitrary multi-step journey in one persistent session. It is not required for the core skill-to-CLI workflow.

A live site, production, or a site you do not own: the agent uses tapp explore --read-only / tapp_explore {readOnly:true}, which renders and reads the page but never clicks, types or submits. Exploration is for apps and environments you own.

No agent integration: run the npm package directly from an app repository in one line:

npx -y @aarwitz/tapp@latest init . --explore

VS Code: install Tapp from the Marketplace. It contributes the same cross-platform Agent Skill to Copilot plus focused iOS simulator tools and an auto-refreshing screenshot preview. The preview is not an embedded Simulator or video stream. Android and web remain available through the skill's CLI/MCP workflow.

Teams: Tapp's core stays MIT licensed. A small paid founding pilot is open for hands-on repository onboarding, important-journey setup, and CI integration in infrastructure you control. Apply without sharing private data.

you:    "Add a logout button to the settings screen"

agent: *writes the Swift* agent: *tapp: finds Settings in source, follows its previously observed route, screenshots it* agent: "Done — and here it is working on the simulator: [screenshot]"

npm CLI quickstart

Requirements: Node ≥ 18. iOS needs macOS + Xcode; Android needs adb plus a connected emulator/device (and JDK 17 when Tapp builds source rather than installing an existing APK); web needs Playwright + Chromium. tapp doctor reports these separately.

From the app repository, ground Tapp once, then use the smallest operation for later checks:

npx -y @aarwitz/tapp@latest init . --explore # first run: detect/build, explore, and ground .tapp/ui-map.json

npx -y @aarwitz/tapp@latest look # one current screen + screenshot npx -y @aarwitz/tapp@latest explore --goal "Save storefront settings visible above keyboard" # source + observed-route fast path npx -y @aarwitz/tapp@latest explore # later broad exploration (observation, not a gate)

Source tells explore --goal where the requested UI likely lives; only a route already observed in .tapp/ui-map.json authorizes navigation. If a fresh repository has no such route yet, Tapp returns the source evidence instead of guessing through the app.

Claude Code can read the saved image with its file-reading tool; Codex can open it with view_image. The agent should report what the screenshot proves, relay the exploration findings as-is (an observation, not a merge decision — tapp ci gates that), and link the HTML evidence report. No Tapp server, account, global install, API key, or bundle id is required for this loop. The platform runtime still needs to be installed, and repository onboarding can write reviewed configuration under .tapp/.

The product, executable, and package leaf are all Tapp: npm distributes it as @aarwitz/tapp, while the installed command remains tapp.

To bootstrap maintained release infrastructure, preview the repository model and grounded plan before Tapp writes anything:

npx -y @aarwitz/tapp@latest init . --dry-run --json-out /tmp/tapp-init.json

Build/start the detected web target, ground the first UI Map, then stop it.

npx -y @aarwitz/tapp@latest init . --explore --platform web

Or build/install the detected Xcode target, ground the map, and persist the validated scheme.

npx -y @aarwitz/tapp@latest init . --explore --platform ios --target .

Or connect to an already-running owned URL:

npx -y @aarwitz/tapp@latest init . --explore --platform web --url http://127.0.0.1:4173

If the app has roles/accounts, bind names once; values stay in local/CI secrets.

npx -y @aarwitz/tapp@latest plan actor set alice . --role member --session isolated \ --credential email=ALICE_EMAIL --credential password=ALICE_PASSWORD

Review-only path: tapp init . → tapp plan show → tapp plan review --approve ...

After approved drafts replay and are promoted, establish the selected target's baseline

through the ordinary full gate, then generate the reviewable GitHub workflow.

npx -y @aarwitz/tapp@latest ci baseline . --platform web npx -y @aarwitz/tapp@latest ci install .

Actor setup refuses to overwrite an existing actor. Repeat actor set with --replace only when you intend to replace that actor's reviewed role, session, provisioning, or credential bindings.

In a repository containing multiple apps (for example, iOS plus web), tapp init . --explore without an explicit target does not guess from detection order—even when a prior choice is recorded. A human terminal gets a numbered selector; a non-interactive CLI prints exact target-selection commands, while MCP also returns structured choices. Neither builds or writes before the choice. After you choose one, the model retains every detected target and records the choice as the default for the next bare tapp explore; explicit init --explore continues to ask because it is the onboarding/refresh operation. Setup gaps belonging only to unselected targets are shown as informational, not as failures of the selected run.

The baseline command writes only after exploration and every selected deterministic suite pass conclusively. It stores .tapp/baselines/ / .json; the generated workflow uses that exact target identity so two apps on the same platform never share a baseline. ci install writes .github/workflows/tapp.yml plus .tapp/ci.json, refuses unresolved build configuration and existing-file collisions, and never commits, pushes, enables branch protection, or creates GitHub resources. Review and pin the generated Tapp release reference to its immutable commit SHA before production.

look and explore accept a repo directory, a path/to/App.app, a bundle id, or no target (auto-detecting the repository or installed app):

npx -y @aarwitz/tapp@latest look [target]         # launch the app → screen summary + screenshot file

npx -y @aarwitz/tapp@latest look [target] --tree # + the accessibility tree of the current screen npx -y @aarwitz/tapp@latest look # no target on iOS: the booted simulator as it is right now

On iOS, look --tree inspects an installed app and never builds, uninstalls, or replaces it. With no target, it uses the repository's recorded iOS target or the sole installed app. If the choice is ambiguous, it lists the installed apps for you to select. Pass a bundle id to inspect a specific sandbox build; run tapp_build (MCP) or init . --explore when you intend to replace it.

iOS Flow evidence includes flow-final.png on passing and failing replays, plus flow-failure-N.png at a failed step, alongside the log, JSON report, and XCTest result bundle.

Web: npx -y @aarwitz/tapp@latest explore http://localhost:3000 *(one-time setup: npm i -g playwright && npx playwright install chromium)*. Add --watch to open Tapp's controlled, isolated Chromium window and follow its clicks with an on-page pointer/action label. Tapp hides that watch UI from saved evidence screenshots and does not automate your personal/default browser profile.

Focused web inspection waits briefly for loading states to settle. If a consent or location modal blocks the screen, dismiss it and wait for the content you care about in the same package-only call:

npx -y @aarwitz/tapp@latest look https://example.com --tap "Not now" --wait-for "Dashboard"

npx -y @aarwitz/tapp@latest look https://example.com --tree --tap "Not now" --wait-for "Dashboard" --json

Android:

npx -y @aarwitz/tapp@latest explore path/to/app-debug.apk --platform andr

只显示了开头部分；其余内容请在仓库中阅读

Tapp

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

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

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

Fomu MCP

作者的 README

Tapp

Give Tapp to your coding agent

npm CLI quickstart

Build/start the detected web target, ground the first UI Map, then stop it.

Or build/install the detected Xcode target, ground the map, and persist the validated scheme.

Or connect to an already-running owned URL:

If the app has roles/accounts, bind names once; values stay in local/CI secrets.

Review-only path: tapp init . → tapp plan show → tapp plan review --approve ...

After approved drafts replay and are promoted, establish the selected target's baseline

through the ordinary full gate, then generate the reviewable GitHub workflow.