Frida MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Frida MCP list all running processes on my Android device"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Frida MCP
A Model Context Protocol (MCP) implementation for Frida dynamic instrumentation toolkit.
Overview
This package provides an MCP-compliant server for Frida, enabling AI systems to interact with mobile and desktop applications through Frida's dynamic instrumentation capabilities. It uses the official MCP Python SDK to enable seamless integration with AI applications.
Demo
https://github.com/user-attachments/assets/5dc0e8f5-5011-4cf2-be77-6a77ec960501
Features
Built with the official MCP Python SDK
Comprehensive Frida tools exposed through MCP:
Process management (list, attach, spawn, resume, kill)
Device management (USB, remote devices)
Interactive JavaScript REPL with real-time execution
Script injection with progress tracking
Process and device monitoring
Resources for providing Frida data to models
Prompts for guided Frida analysis workflows
Progress tracking for long-running operations
Full support for all MCP transport methods
Installation
Prerequisites
Python 3.8 or later
pip package manager
Frida 16.0.0 or later
Quick Install
pip install frida-mcpDevelopment Install
# Clone the repository
git clone https://github.com/yourusername/frida-mcp.git
cd frida-mcp
# Install in development mode with extra tools
pip install -e ".[dev]"Claude Desktop Integration
To use Frida MCP with Claude Desktop, you'll need to update your Claude configuration file:
Locate your Claude Desktop configuration file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.json
Add the following to your configuration file:
{
"mcpServers": {
"frida": {
"command": "frida-mcp"
}
}
}Usage
Once installed, you can use Frida MCP directly from Claude Desktop. The server provides the following capabilities:
Process Management
List all running processes
Attach to specific processes
Spawn new processes
Resume suspended processes
Kill processes
Device Management
List all connected devices (USB, remote)
Get device information
Connect to specific devices
Smart Device Selection
Launch the server with the desired mode each time. For example:
frida-mcp --mode remote --remote-address 10.211.55.3 --remote-alias windows_vmThe command above pins future MCP requests to the remote Frida server at
10.211.55.3:27042and exposes it asdevice_id="windows_vm".Available CLI flags:
--mode {local,usb,remote}to force a specific target class.--remote-address <host[:port]>and optional--remote-alias <name>to register a remote endpoint for the session. When the port is omitted the default 27042 is used.--fallback-order remote,usb,local(comma separated) to control automatic discovery order whendevice_idis omitted.
Environment variables (
FRIDA_DEFAULT_DEVICE,FRIDA_DEFAULT_REMOTE,FRIDA_DEVICE_FALLBACKS) still work and merge with CLI settings.Use the
configure_remote_devicetool at runtime to add or update remote endpoints without restarting the MCP server.
Interactive JavaScript REPL
Create interactive sessions with processes
Execute JavaScript code in real-time
Monitor process state and memory
Hook functions and intercept calls
Capture console.log output
Handle errors and exceptions gracefully
Script Injection
Inject custom JavaScript scripts
Track injection progress
Handle script errors and exceptions
Resources
Get Frida version information
Access process list in human-readable format
Access device list in human-readable format
Development
# Clone repository
git clone https://github.com/yourusername/frida-mcp.git
cd frida-mcp
# Install development dependencies
pip install -e ".[dev]"License
MIT
Available Tools
14 toolsattach_to_processC
Attach to a process by ID.
Inputs: pid (required), device_id.
configure_remote_deviceB
Connect to a remote Frida server and make it available for future requests.
Inputs: address (required), alias, set_as_default. Returns: result
create_interactive_sessionB
Create an interactive REPL-like session with a process.
This returns a session ID that can be used with execute_in_session to run commands.
Returns:
Information about the created session
Inputs: process_id (required), device_id. Returns: result
enumerate_devicesA
List all devices connected to the system.
Returns:
A list of device information dictionaries containing:
- id: Device ID
- name: Device name
- type: Device type
- hint: How to reference the device via device_id
- alias: Configured alias for remote devices (if any)
- default_candidate: Whether the device is the current default choice
Inputs: no named parameters. Returns: result
enumerate_processesA
List all processes running on the system.
Returns:
A list of process information dictionaries containing:
- pid: Process ID
- name: Process name
Inputs: device_id. Returns: result
execute_in_sessionA
Execute JavaScript code within an existing interactive Frida session.
This tool allows for dynamic scripting against a process previously attached to
via `create_interactive_session`.
Inputs: session_id (required), javascript_code (required), keep_alive. Returns: result
get_deviceC
Get a device by its ID.
Returns:
Information about the device
Inputs: device_id (required). Returns: result
get_local_deviceC
Get the local device.
Returns:
Information about the local device
Inputs: no named parameters. Returns: result
get_process_by_nameC
Find a process by name.
Inputs: name (required), device_id.
get_session_messagesA
Retrieve and clear messages sent by persistent scripts in a session.
Returns:
A list of messages captured since the last call, or an error if the session is not found.
Inputs: session_id (required). Returns: result
get_usb_deviceC
Get the USB device connected to the system.
Returns:
Information about the USB device
Inputs: no named parameters. Returns: result
kill_processC
Kill a process by ID.
Returns:
Status information
Inputs: pid (required), device_id. Returns: result
resume_processC
Resume a process by ID.
Returns:
Status information
Inputs: pid (required), device_id. Returns: result
spawn_processC
Spawn a program.
Returns:
Information about the spawned process
Inputs: program (required), args, device_id. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 14 tools
Most tools have distinct purposes, but some potential overlap exists between 'attach_to_process' and 'create_interactive_session' (both involve attaching to processes), and between 'get_device', 'get_local_device', and 'get_usb_device' (all retrieve device information). The descriptions help clarify differences, but an agent might initially confuse these pairs.
All tool names follow a consistent snake_case pattern with clear verb_noun structures (e.g., 'enumerate_processes', 'get_session_messages', 'spawn_process'). There are no deviations in naming conventions, making the set predictable and readable.
With 14 tools, this server is well-scoped for Frida's dynamic instrumentation domain. The count covers essential operations like device management, process control, and session handling without being excessive, ensuring each tool has a clear role.
The tool set provides strong coverage for Frida's core workflows, including device enumeration, process management, and interactive scripting. A minor gap is the lack of tools for detaching from processes or terminating sessions, which agents might need to work around, but overall, the surface supports key operations effectively.
Related MCP Connectors
Drive real devices from your AI Coding tool. Embed a client SDK (Unity, Godot, Flutter, iOS/macOS, Android, React Native, Web) in your app, then capture screenshots, traverse the UI tree, inject taps and key events, and run automated test tasks on the physical device over a secure relay.
Let AI agents control Android and iOS devices on Mobilerun Cloud: screen, input, apps, workflows.
- DNS-DATA RemoteDeprecatedcom.dns-data
Connect AI assistants to authorized Windows and macOS devices for files, commands, and management.
Give your AI agent a real cloud Android phone: push APKs, drive it, get screenshots and logs.