JevSim
Overview
Description from the maker (original English)
Run verified iOS and Android UI workflows in one agent tool call with Jev.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi2 of 2 passedChecked from public information; code not scanned yet
- UsageiVery new↓ 39/wk · ★ 0
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Developer tools
- You need to fill in: TYPESAFE_API_KEY
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 2 of 2 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
TYPESAFE_API_KEY,JEVSIM_MODEL,JEVSIM_XCODE_COMMAND,JEVSIM_XCODE_ARGS,JEVSIM_ANDROID_APPIUM_URL,JEVSIM_ADB_COMMAND
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"jevsim": {
"command": "npx",
"args": [
"-y",
"@huaaudio/jevsim"
],
"env": {
"TYPESAFE_API_KEY": "your-value",
"JEVSIM_MODEL": "your-value",
"JEVSIM_XCODE_COMMAND": "your-value",
"JEVSIM_XCODE_ARGS": "your-value",
"JEVSIM_ANDROID_APPIUM_URL": "your-value",
"JEVSIM_ADB_COMMAND": "your-value"
}
}
}
}Run this in your terminal
claude mcp add jevsim --env TYPESAFE_API_KEY=your-value --env JEVSIM_MODEL=your-value --env JEVSIM_XCODE_COMMAND=your-value --env JEVSIM_XCODE_ARGS=your-value --env JEVSIM_ANDROID_APPIUM_URL=your-value --env JEVSIM_ADB_COMMAND=your-value -- npx -y @huaaudio/jevsimFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"jevsim": {
"command": "npx",
"args": [
"-y",
"@huaaudio/jevsim"
],
"env": {
"TYPESAFE_API_KEY": "your-value",
"JEVSIM_MODEL": "your-value",
"JEVSIM_XCODE_COMMAND": "your-value",
"JEVSIM_XCODE_ARGS": "your-value",
"JEVSIM_ANDROID_APPIUM_URL": "your-value",
"JEVSIM_ADB_COMMAND": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"jevsim": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@huaaudio/jevsim"
],
"env": {
"TYPESAFE_API_KEY": "your-value",
"JEVSIM_MODEL": "your-value",
"JEVSIM_XCODE_COMMAND": "your-value",
"JEVSIM_XCODE_ARGS": "your-value",
"JEVSIM_ANDROID_APPIUM_URL": "your-value",
"JEVSIM_ADB_COMMAND": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- TypeSafe API key for semantic selection. Exact-identifier workflows need no key.
JEVSIM_MODELenvTypeSafe selection model.JEVSIM_XCODE_COMMANDenviOS only: XcodeBuildMCP executable. Use an absolute path if needed.JEVSIM_XCODE_ARGSenviOS only: JSON array of XcodeBuildMCP arguments.JEVSIM_ANDROID_APPIUM_URLenvAndroid only: separately running Appium 3/UIAutomator2 server on loopback.JEVSIM_ADB_COMMANDenvAndroid only: adb executable. Use an absolute path if needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 11, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account huaaudio, which owns the repo
- ✓ Pass
Still maintained
Code last changed 2 months ago
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
User reviews
No reviews yet
Compared with others in Developer toolsi
- More stars than 0% of the other 5742 servers in this category
- Published to the registry more recently than 41% of the other 5742 servers in this category
- Basic checks equal to or better than 100% of the other 5742 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is JevSim safe?
It passed 2 of 2 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: TYPESAFE_API_KEY
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed 2 months ago, and the latest version (0.1.0) reached the registry 2 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: REA, Netdata, Front-End Checklist
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Netdata
Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Front-End Checklist
Review frontend code and live pages against 386 quality-gated web development rules.
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
JevSim
Complete a mobile UI sequence in one agent tool call.
JevSim is a local MCP server for agents working with iOS and Android apps. Give it a short plan—navigate, enter text, save, verify—and it executes the steps without returning to your main reasoning loop after every interaction. Jev, a text-based selection model, matches descriptions to current accessibility controls. XcodeBuildMCP (iOS) or Appium/UIAutomator2 (Android) performs the actions and checks the results.
If you are a human, give your agent this repository URL and ask: “Install JevSim for my iOS/Android project, connect it to your MCP tools, and verify the setup.” The instructions below are for that agent.
Speed comparison
We reran the same ten-tap iOS Settings tour with the same checks after every action: open five sections and return from each. Pure agent means the main agent reads each screen and chooses the next control through XcodeBuildMCP. Agent + JevSim means it delegates the full route in one jevsim_run_steps call, with Jev selecting all ten targets.
| Approach | Median execution time | Verified runs | Speedup |
|---|---|---|---|
| Pure agent + XcodeBuildMCP | 117.3 s | 3/3 | 1× |
| Agent + JevSim + XcodeBuildMCP | 35.7 s | 3/3 | 3.3× |
Measured September 21, 2026: GPT-6-astra (high reasoning) in Codex, Jev 1.13.0, XcodeBuildMCP 2.7.0, iPhone 17e / iOS 26.5 Simulator. Times include observations, target decisions, actions, checks, and intermediate agent/tool round trips; setup and initial route planning are excluded. This is one navigation benchmark with three runs per approach, not a general debugging or Android speed guarantee. Run details and reproduction.
Agent installation
- Inspect the environment. Use Node.js 24 and npm. Choose the platform from the user's project; install only that backend. Reuse existing tools and credentials where available.
- Use the npm package. Configure the MCP client to run
npx -y --package=@huaaudio/jevsim@0.1.0 jevsim. This downloads the compiled package; no clone or build is needed. Use an absolute path to Node.js 24’snpxif the client has a restricted PATH. Source installation remains available for development. - Prepare the backend. For iOS, use macOS, Xcode, and a booted simulator; JevSim starts its own pinned XcodeBuildMCP process. For Android, prepare ADB and a device/emulator, then start local Appium with UIAutomator2 using the Android instructions. Build, install, and launch the user's app with your existing tools.
- Configure Jev. Supply
TYPESAFE_API_KEYthrough your client's secret/environment configuration. The npm launcher does not automatically read.env; use the env-file launch option if needed. Preserve an existing.env; use .env.example only as a template. Never print or commit the key. Exact-identifier workflows also work without a key. - Register and verify the MCP server. Follow the agent installation runbook for absolute launch paths, client configuration, and readiness checks. Preserve other MCP servers. Installation is complete when you can discover all three tools, connect to the chosen backend, and inspect the intended device. Report any missing prerequisite precisely.
Delegate a workflow
| Tool | Use it to |
|---|---|
jevsim_status | Check backend connectivity, credential presence, and device inventory |
jevsim_inspect | Read the current accessibility state of one explicit device |
jevsim_run_steps | Execute 1–10 supplied steps within 60 seconds; receive outcomes, timings, and any stop reason |
Call status and inspect first. For iOS, pass the observed simulatorId; for Android, pass platform: "android" and the ADB deviceId. Derive the plan from the app and the user's task. Every step must include a backend-verifiable expect condition.
For example, this is one step only if your app exposes the stated destination identifier:
{
"action": "tap", "target": { "description": "Open the profile editor" }, "expect": { "predicate": "exists", "identifier": "profile.name" } }
Use a unique observed target.identifier when available; it skips the model request. Otherwise, Jev selects among current action-compatible controls or abstains. It cannot invent steps or generate typing text. Supported actions are tap, type, scroll, wait, and assert. See the request schema and complete example.
Reserve the device until the call returns. A completed result means every supplied expectation matched. If execution stops, inspect completedSteps, reason, and actionStatus, then inspect the app and re-plan. Never blindly replay a workflow or an uncertain action. See agent usage and recovery.
When to use it
Delegate known sequences: reproduce a bug, navigate to a screen, exercise a form, or verify a change. Keep builds, code edits, visual interpretation, and decisions that depend on new information in your main agent. Split longer work into bounded sequences.
- Supported: iOS Simulator and native Android accessibility. Android has been live-tested on an Android 15 emulator on macOS; physical Android devices and Windows/Linux hosts remain unvalidated.
- Input: Android supports Unicode and empty replacement. The tested iOS backend accepts nonempty printable ASCII only.
- Limits: inaccessible controls, Android WebViews, and arbitrary desktop GUIs need other tools. JevSim does not interpret screenshots.
- Data: semantic selection sends accessibility text and field values to TypeSafe. Exact-identifier workflows skip those requests. Tool transcripts and backend logs may contain app data; see data handling.
Reference
Agent installation · Agent usage · Tools · Configuration · Troubleshooting · Release notes
Contributors: development guide for fixtures, tests, benchmark reproduction, and implementation history.
MIT. Independent project; automation backends and the TypeSafe service have their own terms and licenses.