Frida Mobile MCP

Name: Frida Mobile MCP
Author: monkeywave

by monkeywaveversion 0.6.0i★ –iRuns on your computer

Registry nameio.github.monkeywave/frida-mobile-mcp

Install

Overview

Description from the maker (original English)

Mobile Frida MCP Server - AI-powered mobile app exploration and testing via Frida instrumentation

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
UsageiNot measured yet★ –

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: Other
You need to fill in: FRIDA_MCP_HTTP_TOKEN

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

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

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": {
    "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"
      }
    }
  }
}

Run this in your terminal

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-mcp

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": {
    "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"
      }
    }
  }
}

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": {
    "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"
      }
    }
  }
}

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

FRIDA_DEVICE_ID env
Default Frida device ID to use (e.g. emulator-5554 or a USB serial). Can also be set with --device.
FRIDA_MCP_ALLOW_CUSTOM_SCRIPTS env
Set to "1" to enable execution of custom Frida scripts (execute_script and custom hook_function handlers). Disabled by default.
FRIDA_MCP_MEMORY_WRITE env
Set to "1" to enable the write_memory tool. Disabled by default for safety.
FRIDA_MCP_REMOTE env
host[:port] of a remote frida-server to add as a remote device at startup (port defaults to 27042).
FRIDA_MCP_SCHEMA_PROFILE env
Tool schema profile. "compact" shortens tool schemas and descriptions for clients with small context windows.
FRIDA_MCP_MAX_RESPONSE_CHARS env
Maximum number of characters in a single tool response; longer output is truncated.
FRIDA_MCP_HTTP_TOKEN secret env
Bearer token required by HTTP clients. Only used with --transport http (required when --host is not loopback); unused for the default stdio transport.
FRIDA_MCP_RUNTIME env
Frida script runtime to use for injected agents.
FRIDA_MCP_DEBUG env
Set to "1" to enable debug logging on stderr. Can also be set with --debug.
FRIDA_MCP_BRIDGES_DIR env
Directory with prebuilt Java/ObjC bridge bundles (defaults to dist/bridges inside the package)
FRIDA_MCP_COMPILER_PROJECT_DIR env
Cache directory for the frida.Compiler project used to compile ES module scripts
FRITAP_AGENT_PATH env
Path to a friTap fritap_agent.js bundle for capture_tls (otherwise the installed friTap Python package or a pinned download is used)
FRITAP_VERSION env
friTap release tag to download when no local agent is found (default v2.5.2)

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

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account monkeywave, 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 Otheri

More stars than 0% of the other 32623 servers in this category
Published to the registry more recently than 72% of the other 32623 servers in this category
Basic checks equal to or better than 100% of the other 32623 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 Frida Mobile MCP 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?

You need to fill in: FRIDA_MCP_HTTP_TOKEN

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.6.0) reached the registry 14 days 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: Spec Driven Development, Remote Desktop Commander, Draugr

Alternatives

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Draugr

by draugr-dev

Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.

Runs on your computerUpdated today

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.

frida-mobile-mcp

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.

Quick start

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.

Requirements

Node.js >= 22.12 (CI runs 22 and 24 on Linux, macOS and Windows). npm install runs the frida package's install script, which downloads the native frida-node prebuild.
A device or emulator running frida-server 17.x. This package depends on frida-node ^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.
Android: download the matching 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 &'"

iOS: a jailbroken device with the matching Frida package from the Frida Cydia/Sileo repository. Non-jailbroken devices need the app repackaged with the Frida Gadget; the server then attaches to the gadget-enabled process like any other.
Optional: 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.

What is new for Frida 17

Bridges are bundled. Frida 17 no longer ships the Java/ObjC bridges in the GumJS runtime. 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.
Legacy scripts still work. 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.
Removed APIs are linted. 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 reference

Tier 1: high-level tools

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).

Tier 2: advanced primitives

Tool	Description

| list_devices | Local, U

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

Frida Mobile MCP

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 Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Draugr

README from the maker

frida-mobile-mcp

Quick start

Requirements

What is new for Frida 17

Tool reference

Tier 1: high-level tools

Tier 2: advanced primitives