tapflow.dev valid

tapflow

tapflow is an open-source, self-hosted tool that lets your entire team — PO, PM, designers, backend engineers, and QA — run iOS simulators and Android emulators directly in the browser. No IDE, no device setup, no data leaving your network.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T10:03:04.459Z. Cached copy · Source on tapflow.dev

# tapflow

> tapflow is an open-source, self-hosted tool that lets your entire team — PO, PM, designers, backend engineers, and QA — run iOS simulators and Android emulators directly in the browser. No IDE, no device setup, no data leaving your network.
>
> It is a self-hosted, open-source alternative to cloud testing services like Appetize and BrowserStack App Live. Unlike those services, tapflow runs on Macs your team already owns, so your app binaries and test data never leave your network.
>
> Architecture: a Mac Agent connects outbound to a Relay server; team members open the dashboard in any browser and interact with the simulator in real time. The Relay also exposes a REST API and an MCP server for LLM-based automation.
>
> Two testing paths:
> - Manual review (primary): CI uploads a build → team tests in the browser
> - AI Agent via MCP (experimental): an LLM agent controls the simulator using @tapflowio/mcp-server
>
> Every page below is also served as its source markdown at the same URL with a `.md` suffix, and all of them concatenated are at https://www.tapflow.dev/llms-full.txt. Korean translations of every page live under `/ko/` with the same paths and the same content.
>
> Read the page you need rather than the concatenation. A tool that truncates or summarises a large fetch loses the end of `llms-full.txt`, which is where the reference pages are — the CLI, the REST API and every configuration key.

## Get started

- [Introduction](https://www.tapflow.dev/get-started/introduction): What tapflow is, who does what (an operator sets up a Mac; teammates only open a browser), the key concepts (relay, agent, dashboard, App Center, build, QA Session, roles), architecture diagrams, and the three ways to use tapflow (manual QA, plus experimental AI agents and automation).
- [Quick Start](https://www.tapflow.dev/get-started/quick-start): Operator tutorial from install to the first tap: prerequisites, tapflow setup, optional tapflow init, tapflow start and its banner, the admin account, uploading your build, Start QA, picking a Mac and device, Launch app, and inviting a teammate with the dashboard's LAN address.
- [For teammates](https://www.tapflow.dev/get-started/teammates): For a teammate who received an invite link: accept it, save the dashboard address, pick a build in App Center, start a QA Session, leave comments, what each role (Viewer / QA / Developer / Admin) may do, and profile settings.

## Test apps

- [Test apps](https://www.tapflow.dev/testing): How teammates test builds in the browser: pick a build in App Center, drive a simulator or emulator in a QA Session, and leave what you found.
- [App Center](https://www.tapflow.dev/testing/app-center): The dashboard's build list, grouped by app and version: uploading builds (.app.zip / .tar.gz for iOS simulators, .apk), search and status filter, what each review status means, scheduled deletion, and the Start QA button (disabled for Done).

### QA Session

- [QA Session](https://www.tap
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=tapflow.dev · GET /v1/domain/tapflow.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for tapflow.dev:
1. POST https://agentwebmap.com/v1/sites/tapflow.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://tapflow.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/tapflow.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/tapflow.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.