FridaC2MCP

An MCP server with streamable HTTP transport that runs Frida's dynamic instrumentation entirely on-device — no client-side tooling required.

This project runs directly on rooted Android and jailbroken iOS devices, exposing Frida as a set of tools callable over HTTP. Any MCP-compatible client can connect to a device on the network and perform dynamic instrumentation without installing any Frida tooling locally.

Going forward, development is targeting Gemini CLI and Claude Code as primary clients, since both are building native multi-agent orchestration and MCP support — which aligns with this project's direction of composing multiple MCP servers (e.g. FridaC2MCP + Jadx-MCP) into automated workflows. 5ire was used extensively during early development and remains a great GUI option for interacting with the server.

Gemini CLI — register the device MCP server (replace <DEVICE_IP> with your phone’s LAN address):

gemini mcp add --transport http frida-c2-mcp http://<DEVICE_IP>:6767/mcp

Android Demo

https://github.com/user-attachments/assets/7cee77c5-ed40-4797-b6b5-3edb5fdd03ce

iOS Demo

https://github.com/user-attachments/assets/1f0fa9c4-6fd0-4dfd-a640-78c9f8a95a6b

Core Functionality

• Process & Application Management: List installed applications, enumerate running processes, and get information about the foreground application.
• Application Control: Start and terminate applications by their identifier or PID.
• Dynamic Instrumentation: Create interactive sessions by attaching to running processes.
• Remote Script Execution: Execute custom Frida (JavaScript) scripts within an attached session. Scripts are compiled on-the-fly to ensure compatibility with Frida 17+. This supports both one-shot scripts and persistent hooks (keep_alive=True).

Intended Use Case

The goal is fully automated, agent-driven mobile security testing. By exposing Frida as an MCP server, a pentester or an AI agent can inspect and manipulate an application's behavior without a direct USB connection or local shell access after initial setup. The client needs zero Frida tooling — everything runs on the target device.

A typical workflow:

1. Point your AI agent (Claude Code, Gemini CLI, etc.) at the device's MCP endpoint.
2. The agent starts a target application, attaches a Frida session, and injects hooks.
3. Security controls (root/jailbreak detection, SSL pinning, etc.) are bypassed dynamically.
4. The agent observes results and iterates — all without human intervention.

This extends naturally to multi-device setups: run multiple phones on the same network, each with its own MCP server, and orchestrate them from a single agent.

Platform Support

Android (cli.py)

Runs in Termux on rooted Android. Uses esbuild for on-the-fly script bundling and frida-java-bridge for Java/Android runtime instrumentation. While frida-compile is technically available via frida-tools, it cannot be used on Termux because Android's untrusted_app SELinux domain blocks the W^X memory mappings required by V8's JIT compiler — causing a SIGSEGV on any non-trivial script. esbuild is a statically linked Go binary with no JIT, so it runs cleanly in any SELinux context.

iOS (ios.py)

Runs on rootless jailbroken iOS (tested on iPhone X, iOS 16.7.12 with palera1n). Uses frida-compile for script bundling and frida-objc-bridge for Objective-C runtime instrumentation. Node.js is not required on-device.

The iOS port required custom-compiling an entire Python 3.12 toolchain for arm64, since none of these packages were available for rootless jailbroken iOS:

| Package | Version | Build System | Why | |

... View full README on GitHub