Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Mobile Frida MCP Server - AI-powered mobile app exploration and testing via Frida instrumentation
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
FRIDA_DEVICE_ID, FRIDA_MCP_ALLOW_CUSTOM_SCRIPTS, FRIDA_MCP_MEMORY_WRITE, FRIDA_MCP_REMOTE, FRIDA_MCP_SCHEMA_PROFILE, FRIDA_MCP_MAX_RESPONSE_CHARS, FRIDA_MCP_HTTP_TOKEN, FRIDA_MCP_RUNTIME, FRIDA_MCP_DEBUG, FRIDA_MCP_BRIDGES_DIR, FRIDA_MCP_COMPILER_PROJECT_DIR, FRITAP_AGENT_PATH, FRITAP_VERSIONAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"frida-mobile": {
"command": "npx",
"args": [
"-y",
"frida-mobile-mcp"
],
"env": {
"FRIDA_DEVICE_ID": "your-value",
"FRIDA_MCP_ALLOW_CUSTOM_SCRIPTS": "your-value",
"FRIDA_MCP_MEMORY_WRITE": "your-value",
"FRIDA_MCP_REMOTE": "your-value",
"FRIDA_MCP_SCHEMA_PROFILE": "your-value",
"FRIDA_MCP_MAX_RESPONSE_CHARS": "your-value",
"FRIDA_MCP_HTTP_TOKEN": "your-value",
"FRIDA_MCP_RUNTIME": "your-value",
"FRIDA_MCP_DEBUG": "your-value",
"FRIDA_MCP_BRIDGES_DIR": "your-value",
"FRIDA_MCP_COMPILER_PROJECT_DIR": "your-value",
"FRITAP_AGENT_PATH": "your-value",
"FRITAP_VERSION": "your-value"
}
}
}
}Führe das in deinem Terminal aus
claude mcp add frida-mobile --env FRIDA_DEVICE_ID=your-value --env FRIDA_MCP_ALLOW_CUSTOM_SCRIPTS=your-value --env FRIDA_MCP_MEMORY_WRITE=your-value --env FRIDA_MCP_REMOTE=your-value --env FRIDA_MCP_SCHEMA_PROFILE=your-value --env FRIDA_MCP_MAX_RESPONSE_CHARS=your-value --env FRIDA_MCP_HTTP_TOKEN=your-value --env FRIDA_MCP_RUNTIME=your-value --env FRIDA_MCP_DEBUG=your-value --env FRIDA_MCP_BRIDGES_DIR=your-value --env FRIDA_MCP_COMPILER_PROJECT_DIR=your-value --env FRITAP_AGENT_PATH=your-value --env FRITAP_VERSION=your-value -- npx -y frida-mobile-mcpTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"frida-mobile": {
"command": "npx",
"args": [
"-y",
"frida-mobile-mcp"
],
"env": {
"FRIDA_DEVICE_ID": "your-value",
"FRIDA_MCP_ALLOW_CUSTOM_SCRIPTS": "your-value",
"FRIDA_MCP_MEMORY_WRITE": "your-value",
"FRIDA_MCP_REMOTE": "your-value",
"FRIDA_MCP_SCHEMA_PROFILE": "your-value",
"FRIDA_MCP_MAX_RESPONSE_CHARS": "your-value",
"FRIDA_MCP_HTTP_TOKEN": "your-value",
"FRIDA_MCP_RUNTIME": "your-value",
"FRIDA_MCP_DEBUG": "your-value",
"FRIDA_MCP_BRIDGES_DIR": "your-value",
"FRIDA_MCP_COMPILER_PROJECT_DIR": "your-value",
"FRITAP_AGENT_PATH": "your-value",
"FRITAP_VERSION": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"frida-mobile": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"frida-mobile-mcp"
],
"env": {
"FRIDA_DEVICE_ID": "your-value",
"FRIDA_MCP_ALLOW_CUSTOM_SCRIPTS": "your-value",
"FRIDA_MCP_MEMORY_WRITE": "your-value",
"FRIDA_MCP_REMOTE": "your-value",
"FRIDA_MCP_SCHEMA_PROFILE": "your-value",
"FRIDA_MCP_MAX_RESPONSE_CHARS": "your-value",
"FRIDA_MCP_HTTP_TOKEN": "your-value",
"FRIDA_MCP_RUNTIME": "your-value",
"FRIDA_MCP_DEBUG": "your-value",
"FRIDA_MCP_BRIDGES_DIR": "your-value",
"FRIDA_MCP_COMPILER_PROJECT_DIR": "your-value",
"FRITAP_AGENT_PATH": "your-value",
"FRITAP_VERSION": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
FRIDA_DEVICE_ID envFRIDA_MCP_ALLOW_CUSTOM_SCRIPTS envFRIDA_MCP_MEMORY_WRITE envFRIDA_MCP_REMOTE envFRIDA_MCP_SCHEMA_PROFILE envFRIDA_MCP_MAX_RESPONSE_CHARS envFRIDA_MCP_RUNTIME envFRIDA_MCP_DEBUG envFRIDA_MCP_BRIDGES_DIR envFRIDA_MCP_COMPILER_PROJECT_DIR envFRITAP_AGENT_PATH envFRITAP_VERSION envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto monkeywave bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: FRIDA_MCP_HTTP_TOKEN
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.6.0) kam vor 14 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Node.js auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, topo^alpin
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
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.
Avalanche bulletins and mountain weather forecasts for any place in the Alps.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
An MCP server that gives AI agents dynamic instrumentation of Android and iOS apps through Frida 17, and runs next to REA, ReVa (Ghidra) and IDA MCP servers. It exposes 71 tools: high-level ones that manage devices, sessions and scripts for you (explore an app, hook a Java/ObjC/native method, trace calls, map reachability coverage and autonomously drive the UI toward it, find secrets in memory and turn them into reusable friTap patterns, cast a wide net over crypto, bypass SSL pinning, capture TLS keys and plaintext with friTap, run prebuilt analysis scripts, validate custom scripts) and low-level primitives (spawn/attach, module and symbol enumeration, address resolution, control-flow analysis, memory dumps). Addresses use the same module+0xoffset notation as Ghidra/IDA so results move between static and dynamic tools without conversion, and every result carries an evidence envelope (evidence_id, limitations, coverage). Optional UI automation goes through mobile-mcp.
npx frida-mobile-mcp # stdio MCP server (default `serve` command)
frida-mobile-mcp doctor # check Node, frida-node, adb, devices, frida-server, bridge bundles frida-mobile-mcp setup --client cursor # write the server into a client config (claude-code, claude-desktop, cursor, vscode, windsurf, codex) frida-mobile-mcp gadget --platform android --print # generate a frida-gadget config.json + APK/IPA repackaging guidance
The gadget command generates a frida-gadget config.json (--interaction listen or --interaction script) and prints the APK/IPA repackaging steps. Embedding the gadget is the only way to instrument native detection that runs in .init_array / JNI_OnLoad before an attach-time script can load, and it removes the frida-server :27042 port as a fingerprint — see frida_help({ topic: "evasion" }).
Claude Code:
claude mcp add frida -- npx -y frida-mobile-mcp
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": { "frida": { "command": "npx", "args": ["-y", "frida-mobile-mcp"], "env": { "FRIDA_DEVICE_ID": "emulator-5554" } } } }
Per-client instructions, HTTP mode and remote frida-server setup are in docs/clients.md. A Claude Desktop extension manifest (manifest.json, MCPB) and an MCP registry entry (server.json) ship in the repo.
npm install runs the frida package's install script, which downloads the native frida-node prebuild.^17.24.3; frida-server on the device must have the same major version (17) and ideally the same minor version. frida-mobile-mcp doctor prints both versions and flags mismatches.frida-server-17.x.y-android- .xz from https://github.com/frida/frida/releases, then xz -d frida-server-17.24.3-android-arm64.xz
adb push frida-server-17.24.3-android-arm64 /data/local/tmp/frida-server adb shell "chmod 755 /data/local/tmp/frida-server" adb shell "su -c '/data/local/tmp/frida-server &'"
pip install friTap for capture_tls (otherwise the pinned agent is downloaded on first use), and network access for npx -y @mobilenext/mobile-mcp@latest on first mobile_action.npm run build:bridges bundles frida-java-bridge and frida-objc-bridge into dist/bridges/{java,objc}.js; the server injects the right one by platform (Java on Android, ObjC on iOS/macOS) ahead of every script.execute_script runs classic (non-module) scripts through Script.evaluate, so a Java.perform(...) script written for Frida 16 runs unchanged and keeps its own line numbers in errors. ES modules (import Java from "frida-java-bridge", JS or TS) are compiled on the host with the Frida Compiler; frida-compile bundles (starting with the 📦 marker) are loaded as-is.validate_script flags the static Module.findExportByName/findBaseAddress/enumerateExports, Memory.readX/writeX and *Sync enumerators that throw on Frida 17 and suggests the Module-instance / NativePointer replacements. Generated scripts get findExport(lib, name) and hookNative(lib, name, callbacks) helpers from the agent preamble, and template options as __FRIDA_MCP__.options.analyze_native_function uses Process.findFunctionRange and the Frida 17.12+ ControlFlowGraph (with a linear-disassembly fallback reported in limitations).| Tool | Description |
|---|---|
get_status | Connected devices, active sessions (platform, script count, last activity), hooks, traces and recent detaches/crashes. Run first and after a session is lost. |
frida_help | Topic help: overview, hooking, tracing, memory, scripts, native, tls, mobile, examples, advanced, evasion, script_catalog, script_api, recipes, interop. |
detect_app_technologies | Fingerprint libraries, frameworks and security mechanisms; returns recommended script targets. |
explore_app | Spawn an app suspended, instrument, resume; returns pid, platform, modules and a filtered class list. |
get_app_info | Identify the installed artifact: version, SDK levels, debuggable, installer and every APK (base + splits) with on-device sha256/size; pull_to pulls and hash-verifies them for a static tool such as REA inspect_android_package. iOS: Frida app parameters only. |
search_classes_and_methods | Regex search over classes (and methods with include_methods) in a running app. |
describe_class | Full shape of one loaded class: every method overload with parameter/return types and a hook-ready signature, constructors, fields, superclass/interfaces (ObjC: selectors with type encodings). Feed a signature to hook_method evidence: {class, signature}. |
discover_crypto | Find where an app does crypto (or any API family) without assuming javax.crypto: ranked candidate hook targets across Java/ObjC classes and native symbols. |
find_secrets_in_memory | Content-aware memory scan for the *structure* of secrets: RC4 S-box (byte[] or Java int[256]), AES key schedule (aeskeyfind — encryption and decryption, mode-independent), ChaCha20/Salsa20 keys (sigma constant), high-entropy 16/24/32-byte keys, PEM/DER private keys, JWTs. Finds keys without reaching the code that uses them. |
generate_memory_pattern | Turn a located secret into a reusable anchor pattern (stable byte signature near the key + offset): re-locate it with scan_memory, or hand it to friTap via capture_tls (patterns/offsets). |
monitor_crypto | Crypto-oracle wide net: discover and hook all likely crypto sinks at once (app-owned classes + javax.crypto/Mac/MessageDigest, iOS CommonCrypto, native OpenSSL/BoringSSL) and dump every key, input and output as hex. |
trace_coverage | Reachability map: arm cheap persistent entry-hooks over a class/package/module scope and track covered vs cold targets across trigger_and_wait drives, so you know what code you have not yet exercised. |
drive_coverage | Autonomously drive an instrumented session's UI toward uncovered code — taps on-screen elements breadth-first and stops the instant a crypto/secret signal fires (or coverage stalls / max_steps). Pair with monitor_crypto / trace_coverage. |
watch_loads | Watch for late-loaded .so libraries and Java classes, plus anti-Frida probes; emits watch_event messages as the app runs. |
trigger_and_wait | Perform a UI action and block until the resulting hook/message output arrives, so you learn which hook a tap fired (or that none did). |
hook_method | Hook Java (com.example.Class.method), ObjC (-[Class sel:]) or native targets (libssl.so!SSL_read, libfoo.so+0x1234, 0x7f..., !open) with auto session management; backtraces as module+0xoff (symbol). |
trace_method | frida-trace style tracing of glob patterns (com.example.net.*, -[NSURL*], libssl.so!SSL_*) for a duration. |
execute_script | Run a custom script: classic JS (bridges injected), ES module JS/TS (compiled with the Frida Compiler) or a frida-compile bundle. timeout_ms bounds the initial run. Requires allowCustomScripts. |
validate_script | Syntax, type and Frida 17 removed-API check without a device. Use before execute_script. |
run_prebuilt_script | Run one of the 9 prebuilt scripts below; call without script_name to list them. |
bypass_ssl_pinning | One-click pinning bypass (Android: TrustManager, OkHttp CertificatePinner, Conscrypt; iOS: SecTrust, ATS, BoringSSL). |
capture_tls | friTap: TLS session keys (NSS key log) and optional decrypted plaintext / synthetic pcap for OpenSSL/BoringSSL, Conscrypt, NSS, GnuTLS, wolfSSL, mbedTLS, Secure Transport and more. Accepts friTap patterns/offsets (e.g. from generate_memory_pattern or BoringSecretHunter) for stripped libraries. |
read_memory | Read up to 4 MB at any address notation; returns hex plus absolute address and module+offset. |
write_memory | Write hex bytes to memory. Disabled unless memoryWriteEnabled. |
scan_memory | Byte-pattern scan (48 89 5c 24 ?? 57), optionally limited to a module. |
get_messages | Buffered hook invocations, trace hits, send() output and errors; since paginates. |
get_evidence | Re-read a persisted tool result (params, status, structured result) by evidence_id. |
export_evidence_bundle | Export persisted results as a JSON or Markdown bundle, inline or to a file. |
stop_instrumentation | Remove all hooks, scripts and traces on a target and detach. |
unload_script | Unload a single script (hook, trace or custom) from a session while keeping it attached. |
mobile_action | Gateway to mobile-mcp UI automation (screenshot, elements, tap, swipe, type, launch app, list apps). |
search_recipes | Search the purpose-indexed library of ready-to-run classic-JS recipes (custom crypto-key capture, native/JNI hooks, classloader/intent/WebView, iOS Keychain); returns ranked recipes with source to adapt and run via execute_script. |
save_script | Save a script under ~/.config/frida-mobile-mcp/scripts for reuse. Requires allowCustomScripts. |
list_saved_scripts | List scripts saved with save_script. |
run_saved_script | Run a saved script by name against a target. Requires allowCustomScripts. |
export_script | Export a script as a standalone classic .js that runs under the plain frida -U -f -l file.js CLI (preamble + source; bridges provided by the frida-tools CLI, not bundled). |
| Tool | Description |
|---|
| list_devices | Local, U
Nur der Anfang wird gezeigt; den Rest findest du im Repo