Home › Other › Frida Mobile MCP

Frida Mobile MCP

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

TypeScript
★ 21 stars Last pushed 2026-11-17 License: MIT

Connect

Review any command before running it. Package names and URLs come from the server's own registry entry.

Package (npm 0.7.3)

npx -y frida-mobile-mcp@0.7.3

Or add to your MCP client config:

{
  "mcpServers": {
    "frida-mobile-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "frida-mobile-mcp@0.7.3"
      ],
      "env": {
        "FRIDA_MCP_REMOTE_TOKEN": "<YOUR_VALUE>",
        "FRIDA_MCP_HTTP_TOKEN": "<YOUR_VALUE>"
      }
    }
  }
}
  • FRIDA_DEVICE_ID — 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 — Set to "1" to enable execution of custom Frida scripts (execute_script and custom hook_function handlers). Disabled by default.
  • FRIDA_MCP_MEMORY_WRITE — Set to "1" to enable the write_memory tool. Disabled by default for safety.
  • FRIDA_MCP_ALLOW_NATIVE_INJECTION — Set to "1" to enable the inject_library tool (loads a native .so/.dylib into the target via Frida's injector). Disabled by default.
  • FRIDA_MCP_ALLOW_ADB_SHELL — Set to "1" to enable the adb_shell tool (arbitrary shell commands on an Android device via adb). Disabled by default.
  • FRIDA_MCP_SNAPSHOTS — Set to "1" to use V8 script-runtime snapshots to speed up repeated script loads (requires FRIDA_MCP_RUNTIME=v8). Disabled by default.
  • FRIDA_MCP_EVIDENCE — Set to "0" to stop persisting every tool result (params, status, structured result) to the evidence store; "1" forces it on. Enabled by default.
  • FRIDA_MCP_EVIDENCE_PATH — Directory of the evidence store (records at <path>/YYYY-MM-DD/<evidence_id>.json plus index.jsonl, mode 0600). Defaults to ~/.config/frida-mobile-mcp/evidence.
  • FRIDA_MCP_EVIDENCE_MAX_MB — Size cap of the evidence store in MB; oldest records are pruned beyond it. Defaults to 200.
  • FRIDA_MCP_REMOTE — host[:port] of a remote frida-server to add as a remote device at startup (port defaults to 27042).
  • FRIDA_MCP_REMOTE_TOKEN secret — Auth token of the remote frida-server in FRIDA_MCP_REMOTE (frida-server --token).
  • FRIDA_MCP_REMOTE_CERT — Path to the PEM certificate of a TLS remote frida-server in FRIDA_MCP_REMOTE (frida-server --certificate).
  • FRIDA_MCP_SCHEMA_PROFILE — Tool schema profile. "compact" shortens tool schemas and descriptions for clients with small context windows.
  • FRIDA_MCP_TOOL_PROFILE — Tool exposure profile. "core" registers only 32 core tools to keep the tool catalog small next to other MCP servers.
  • FRIDA_MCP_TOOLS_EXCLUDE — Comma-separated tool-name globs that are never registered, e.g. "adb_*,frida_server_*".
  • FRIDA_MCP_MAX_RESPONSE_CHARS — Maximum number of characters in a single tool response; longer output is truncated.
  • FRIDA_MCP_HTTP_TOKEN secret — 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 — Frida script runtime to use for injected agents.
  • FRIDA_MCP_DEBUG — Set to "1" to enable debug logging on stderr. Can also be set with --debug.
  • FRIDA_MCP_BRIDGES_DIR — Directory with prebuilt Java/ObjC bridge bundles (defaults to dist/bridges inside the package)
  • FRIDA_MCP_COMPILER_PROJECT_DIR — Cache directory for the frida.Compiler project used to compile ES module scripts
  • FRITAP_AGENT_PATH — 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 — friTap release tag to download when no local agent is found (default v2.6.5)
  • FRITAP_AGENT_SHA256 — Bare sha256 of the downloaded friTap agent for the selected FRITAP_VERSION tag. v2.6.5 is pinned in the package; set this for other tags.

Related servers

Data from the Official MCP Registry