Testa MCP Server

Testa MCP server exists for a simple reason — assistants are far more useful when they can act on Testa directly instead of describing what you should do. npx launcher for the Testa MCP server (iOS Simulator E2E driver for AI agents). Requires the native testa binary — install it with Homebrew.

What you get

Real HID touches (every gesture), screen reading via the accessibility tree or on-device OCR, token-efficient, fast, and zero third-party dependencies. Test React Native / Expo and native SwiftUI apps end-to-end — without adding a single testID — then save the run as a flow file and let CI replay it for free.

• 🧠 No app setup required. Reads the accessibility tree, and falls back to
• 🪙 Token-efficient. One compact line per element (e5 Button "Save" #save @120,300)
• 🔁 Acting commands answer with the UI diff. Every tap/type/swipe
• 🎬 Record once, replay forever. testa flow record save smoke.flow writes
• ⚡ Fast. A warm daemon keeps the connection, accessibility translator and HID
• 👆 Every gesture, for real. Tap, long-press, swipe, drag-and-drop,

Setting it up

Installation goes through your MCP client rather than a global install: point it at @valewnrt/testa-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What the assistant can call

Once Testa is connected, these are the calls the assistant has available:

• uses — actions/checkout@v4
• run — xcodebuild -scheme MyApp -sdk iphonesimulator -derivedDataPath dd build
• Icon — only controls with no text and no accessibility label** are ambiguous to
• Platforms — iOS

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the testa mcp server does with a few real requests.

Choosing this one

Among the payments and commerce options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Testa's toolset — uses, run, Icon and 1 more — is a fair guide to whether it matches your workflow. It is maintained by seized1019; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.