Skip to main content
Glama

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

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

  1. Locate your Claude Desktop configuration file:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows: %APPDATA%\Claude\claude_desktop_config.json

    • Linux: ~/.config/Claude/claude_desktop_config.json

  2. 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_vm

    The command above pins future MCP requests to the remote Frida server at 10.211.55.3:27042 and exposes it as device_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 when device_id is omitted.

  • Environment variables (FRIDA_DEFAULT_DEVICE, FRIDA_DEFAULT_REMOTE, FRIDA_DEVICE_FALLBACKS) still work and merge with CLI settings.

  • Use the configure_remote_device tool 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 tools
attach_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

    B3.4/5.0

    Scored across 14 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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