Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Run verified iOS and Android UI workflows in one agent tool call with Jev.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
TYPESAFE_API_KEY, JEVSIM_MODEL, JEVSIM_XCODE_COMMAND, JEVSIM_XCODE_ARGS, JEVSIM_ANDROID_APPIUM_URL, JEVSIM_ADB_COMMANDValues 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.
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.
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.
JEVSIM_MODEL envJEVSIM_XCODE_COMMAND envJEVSIM_XCODE_ARGS envJEVSIM_ANDROID_APPIUM_URL envJEVSIM_ADB_COMMAND envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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 6, 2026
The registry name was verified with the GitHub account huaaudio, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 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.
You need to fill in: TYPESAFE_API_KEY
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).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Zoo MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
An MCP server that provides access to the Zoo API for various CAD operations and tools.
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.
English | 简体中文
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.
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.
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’s npx if the client has a restricted PATH. Source installation remains available for development.TYPESAFE_API_KEY through 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.| 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.
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.
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.