MobiLoop

Name: MobiLoop
Author: enessubass

by enessubassversion 0.1.0-alpha.15i★ –iRuns on your computer

Registry nameio.github.enessubass/mobiloop-mcp

Install

Overview

Description from the maker (original English)

Guarded AI mobile Appium testing, security scanning, verification, and fix-retest MCP tools.

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 checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiVery new★ –

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: Cybersecurity

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: MOBILOOP_WORKSPACE_ROOT, APPIUM_SERVER_URL

You need

DockerDocker installed

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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": {
    "mobiloop": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MOBILOOP_WORKSPACE_ROOT",
        "-e",
        "APPIUM_SERVER_URL",
        "ghcr.io/enessubass/mobiloop-mcp:0.1.0-alpha.15"
      ],
      "env": {
        "MOBILOOP_WORKSPACE_ROOT": "your-value",
        "APPIUM_SERVER_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add mobiloop --env MOBILOOP_WORKSPACE_ROOT=your-value --env APPIUM_SERVER_URL=your-value -- docker run -i --rm -e MOBILOOP_WORKSPACE_ROOT -e APPIUM_SERVER_URL ghcr.io/enessubass/mobiloop-mcp:0.1.0-alpha.15

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "mobiloop": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MOBILOOP_WORKSPACE_ROOT",
        "-e",
        "APPIUM_SERVER_URL",
        "ghcr.io/enessubass/mobiloop-mcp:0.1.0-alpha.15"
      ],
      "env": {
        "MOBILOOP_WORKSPACE_ROOT": "your-value",
        "APPIUM_SERVER_URL": "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.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "mobiloop": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MOBILOOP_WORKSPACE_ROOT",
        "-e",
        "APPIUM_SERVER_URL",
        "ghcr.io/enessubass/mobiloop-mcp:0.1.0-alpha.15"
      ],
      "env": {
        "MOBILOOP_WORKSPACE_ROOT": "your-value",
        "APPIUM_SERVER_URL": "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

MOBILOOP_WORKSPACE_ROOT env
Workspace path mounted into the container.
APPIUM_SERVER_URL env
Appium server URL reachable from the container.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

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 9, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account enessubass, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… 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

Compared with others in Cybersecurityi

More stars than 0% of the other 1005 servers in this category
Published to the registry more recently than 61% of the other 1005 servers in this category
Basic checks equal to or better than 100% of the other 1005 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 MobiLoop safe?

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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

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 –, and the latest version (0.1.0-alpha.15) reached the registry 24 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Zeqqat, Exepal, GitHits

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

Zeqqat

The safe MCP for Dokploy: agents deploy and fix apps without holding keys or seeing secrets.

by zeqqatVery newUpdated today

Runs in the cloud

Install

Exepal

Safety tools for AI agents: safe page reader, prompt-injection, secrets, PII and MCP server scans

by exepal.comEarlyUpdated today

Runs in the cloud✓ exepal.com

Install

GitHits

Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.

by githits-comGrowing↓ 3.3K/wkUpdated today

Computer or cloud✓ githits.com

Install

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.

MobiLoop MCP

Guarded MCP servers for agentic mobile build-test-fix loops.

Documentation site | Installation | Security model | Tool reference

code change -> build -> install on device -> Appium test -> evidence -> classify -> report

MobiLoop MCP is a controlled tool layer between an AI coding agent and a real mobile development environment. It lets an MCP client read and patch a mobile project, build it, install it on Android or iOS targets, drive the app through Appium, verify logs/screens/API results, remember known app-flow checkpoints, and produce evidence-based reports.

The name reflects the core contract: mobile work should run through a measurable loop of change, build, device execution, verification, and evidence-backed triage.

It is built for the workflow where the agent does not just write code. It builds, runs, tests, observes, classifies failures, and hands back evidence. An agent can still use the separate guarded code tools to patch and retest, but that patch step is intentionally outside the default orchestrator.

Today, MobiLoop provides guarded build-test-verify loops and evidence-based failure classification. Fully automated patch-and-retest is intentionally kept outside the default orchestrator until stricter approval, rollback, and review controls are enabled.

Highlights

Evidence-first mobile loops: build logs, screenshots, Appium XML source, logcat/simulator logs, API responses, screenshot diffs, and iteration records.
Android and iOS tool split: Android adb/emulator tools and iOS xcrun simctl/xcodebuild tools are separated.
Appium UI automation: semantic taps, typing, swipes, back navigation, visibility assertions, screenshots, and accessibility summaries.
Flow memory: record runtime screen checkpoints, remember the latest passing path, and auto-replay stable setup steps to a target checkpoint.
Scenario generation and flow DSL: scan source for candidate E2E scenarios, then run high-level JSON flows with wait/tap/type/assert/evidence steps.
Source-flow analysis: scan Flutter, React Native, Android, and iOS source for screen, route, transition, and visible-text candidates.
Root-cause classification: classify logcat evidence into app bugs, automation errors, missing environment, remote rules, and test-data issues.
Server-side approval gate: secure mode requires valid approval payloads for high-impact tools.
Built-in mobile security loop: scan source and platform settings, generate a test plan, compare fixes, and gate release decisions without another scanner package.
Redaction by default: redact common secrets, bearer tokens, API keys, emails, and phone numbers from text artifacts, command output, and MCP/CLI text responses.
Guarded code tools: workspace-only reads/searches/patches, forbidden secret paths, guarded branches, commits, and PR creation.
Docker-ready MCP runtime: package the Node MCP server in Docker while keeping mobile SDKs, emulators, devices, and Appium on the host or runner.
Composable binaries: run everything as one server or split each responsibility into its own MCP server.
Portable mobile QA skill: an MIT-licensed agent skill for planning tests, collecting evidence, and running bounded fix-and-retest workflows with the existing tools.

What This Is

This project provides MCP tools for this architecture:

AI / MCP client

The server does not claim that a test passed because a model says so. A pass should be backed by tool output: command exit codes, screenshots, page source, log checks, API assertions, and recorded loop iterations.

What This Is Not

It is not a replacement for Android SDK, Xcode, Flutter, Gradle, React Native, Appium, or platform drivers.
It is not a universal mobile emulator container. iOS simulator requires macOS, and Android emulator portability depends on host acceleration and device access.
It is not an unrestricted shell bridge. Tools are structured and guarded.
It is not a production deployer. Release signing, store upload, and production secrets remain outside the default scope.

Requirements

Install only what your target app needs.

Workflow	Host	Required tools
MCP runtime	macOS, Linux, Windows	Node.js 20+
Android build/test	macOS, Linux, Windows	Android SDK, `adb`, emulator or physical device, Java/Gradle as needed, Appium, compatible UiAutomator2 driver
Flutter Android	macOS, Linux, Windows	Flutter SDK, Android SDK, Appium for UI flows
React Native Android	macOS, Linux, Windows	Node/npm, Android Gradle toolchain, Android SDK, Appium
iOS simulator	macOS only	Xcode, `xcrun simctl`, iOS Simulator, Appium, compatible XCUITest driver
Docker MCP runtime	macOS, Linux, Windows	Docker, plus host-side mobile tools when driving devices

Start Appium before Appium or flow replay tools:

appium --address 127.0.0.1 --port 4723

Local Appium installs also work:

npx appium --address 127.0.0.1 --port 4723

For Android, make sure the Appium process can see:

export ANDROID_HOME=/absolute/path/to/android/sdk

export ANDROID_SDK_ROOT=/absolute/path/to/android/sdk export PATH="$ANDROID_HOME/platform-tools:$ANDROID_HOME/emulator:$PATH"

For an already-running Genymotion device, add its Android SDK platform tools to PATH, then verify the device before starting a flow:

export PATH="$HOME/Library/Android/sdk/platform-tools:$PATH"

adb devices -l

Install From Source

npm ci

npm test

Configure project-local MCP and the bundled skill, then diagnose the host:

node dist/src/cli.js setup --workspace /absolute/path/to/mobile/app --client codex --yes

node dist/src/cli.js doctor --workspace /absolute/path/to/mobile/app --target android

Clients: codex, claude, cursor, vscode, generic. Use --dry-run to preview. Setup preserves other servers, backs up changed files, and does not install SDKs or modify app data. See installation for Windows, upgrades, and prerequisites. NPM registry publication is not enabled; these commands use the built checkout.

Run the all-in-one MCP server:

MOBILOOP_WORKSPACE_ROOT=/absolute/path/to/mobile/app \

node dist/src/index.js

For development:

npm run dev

CLI Fallback

When an MCP client cannot expose the server as callable tools, use the CLI wrapper:

MOBILOOP_WORKSPACE_ROOT=/absolute/path/to/mobile/app \

node dist/src/cli.js list-tools

Inspect tool policy metadata:

MOBILOOP_WORKSPACE_ROOT=/absolute/path/to/mobile/app \

node dist/src/cli.js list-tools --json

The same metadata is available inside MCP through policy.list_tools.

Call any tool directly:

MOBILOOP_WORKSPACE_ROOT=/absolute/path/to/mobile/app \

node dist/src/cli.js call flow.generate_test_scenarios '{"goal":"login smoke and validation"}'

Generate scenario candidates:

MOBILOOP_WORKSPACE_ROOT=/absolute/path/to/mobile/app \

node dist/src/cli.js generate-scenarios "cover onboarding, login, and validation"

MCP Client Configuration

All-In-One Server

Use this for local development and simpler MCP clients.

"mcpServers": { "mobiloop": { "command": "node", "args": ["/absolute/path/to/mobiloop-mcp/dist/src/index.js"], "env": { "MOBILOOP_WORKSPACE_ROOT": "/absolute/path/to/mobile/app", "APPIUM_SERVER_URL": "http://127.0.0.1:4723" } } } }

Split Servers

Use split servers when you want tighter policy boundaries per responsibility.

"mcpServers": { "mobile-code": { "command": "node", "args": ["/absolute/path/to/mobiloop-mcp/dist/src/servers/code.js"], "env": { "MOBILOOP_WORKSPACE_ROOT": "/absolute/path/to/mobile/app" } }, "mobile-build": { "command": "node", "args": ["/absolute/path/to/mobiloop-mcp/dist/src/servers/build.js"], "env": { "MOBILOOP_WORKSPACE_ROOT": "/absolute/path/to/mobile/app" } }, "mobile-device": { "command": "node", "args": ["/absolute/path/to/mobiloop-mcp/dist/src/servers/device.js"], "env": { "MOBILOOP_WORKSPACE_ROOT": "/absolute/path/to/mobile/app" } }, "mobile-appium": { "command": "node", "args": ["/absolute/path/to/mobiloop-mcp/dist/src/servers/appium.js"], "env": { "MOBILOOP_WORKSPACE_ROOT": "/absolute/path/to/mobile/app", "APPIUM_SERVER_URL": "http://127.0.0.1:4723" } }, "mobile-flow": { "command": "node", "args": ["/absolute/path/to/mobiloop-mcp/dist/src/servers/flow.js"], "env": { "MOBILOOP_WORKSPACE_ROOT": "/absolute/path/to/mobile/app", "APPIUM_SERVER_URL": "http://127.0.0.1:4723" } }, "mobile-verify": { "command": "node", "args": ["/absolute/path/to/mobiloop-mcp/dist/src/servers/verify.js"], "env": { "MOBILOOP_WORKSPACE_ROOT": "/absolute/path/to/mobile/app" } }, "mobile-loop": { "command": "node", "args": ["/absolute/path/to/mobiloop-mcp/dist/src/servers/loop.js"], "env": { "MOBILOOP_WORKSPACE_ROOT": "/absolute/path/to/mobile/app" } } } }

All binaries are listed below.

Binary	Scope
`mobiloop`	CLI wrapper for listing tools, calling tools, and generating scenarios
`mobiloop-mcp`	All tools
`mobiloop-code-mcp`	Code and git tools
`mobiloop-env-mcp`	Environment preflight and compatibility matrix
`mobiloop-build-mcp`	Dependency, lint, test, and APK build tools
`mobiloop-device-mcp`	Android `adb` and emulator tools
`mobiloop-ios-mcp`	iOS simulator and Xcode tools
`mobiloop-appium-mcp`	Appium UI automation tools
`mobiloop-verify-mcp`	Assertions and evidence collection
`mobiloop-flow-mcp`	Source-flow analysis and checkpoint replay
`mobiloop-loop-mcp`	Iteration records and reports

| mobiloop-ci-mcp | Artifact manifests, GitHub summaries, PR comments

Only the beginning is shown; read the rest in the repo

MobiLoop

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Cybersecurityi

Common questions

Alternatives

Zeqqat

Exepal

GitHits

README from the maker

MobiLoop MCP

Highlights

What This Is

What This Is Not

Requirements

Install From Source

CLI Fallback

MCP Client Configuration

All-In-One Server

Split Servers