Frida MCP Server
A MCP server that provides dynamic instrumentation capabilities through Frida. Built with TypeScript and optimized for Bun runtime.
Features
Dynamic Instrumentation: Hook functions, inspect memory, and modify behavior of running processes
Device Management: Support for local, USB, and remote Frida devices
Process Control: Spawn, attach, resume, and kill processes
Interactive Sessions: Create persistent sessions for complex instrumentation workflows
Script Execution: Execute JavaScript code with both one-shot and persistent modes
File Operations: Download files from instrumented processes and query module information
Prerequisites
Installation
Configuration
Environment Variables
FRIDA_REMOTE_HOST: Remote Frida server hostname/IP (e.g., "192.168.1.100")FRIDA_REMOTE_PORT: Remote Frida server port (default: 27042)
Claude Desktop Configuration
Add to your Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Roo Configuration
This project includes a pre-configured .roo/mcp.json file for project-level MCP server configuration. The configuration is automatically available when you open this project in VS Code with Roo installed.
Project Configuration (
To use with a remote Frida device:
Edit .roo/mcp.json and set the FRIDA_REMOTE_HOST environment variable:
Available Tools
Device & Process Management
Tool | Description | Parameters |
| Attach to a running process by PID. Returns attachment status without creating a persistent session. Use
for session-based instrumentation. |
(number)
(optional string or connection string hostname:port) |
| Spawn a process with Frida attached in paused state. The process will be paused at startup. Use
after loading scripts to continue execution. |
(string)
(optional string[])
(optional string or connection string) |
| Resume a spawned process. |
(number)
(optional string or connection string) |
| Kill a process by PID. |
(number)
(optional string or connection string) |
Interactive Sessions
Tool | Description | Parameters |
| Create an interactive session for dynamic instrumentation. Establishes a Frida session for injecting JavaScript, hooking functions, and monitoring the target process. The session persists until explicitly closed or the process terminates. |
(number)
(optional string or connection string) |
| Execute JavaScript code within an existing Frida session. Modes: •
(default): Script runs once, results in initial_logs •
: Script persists for hooks, retrieve messages via
resource |
(string)
(string)
(optional boolean, default: false) |
| Load and execute a Frida JavaScript file into an existing session. |
(string)
(string)
(optional boolean, default: true) |
File Operations
Tool | Description | Parameters |
| Download a file from remote system using Frida instrumentation. Uses double backslashes for Windows paths. Attaches to specified PID or finds explorer.exe. Works best for files up to ~500MB with 60s timeout. |
(string)
(string)
(optional number)
(optional string or connection string) |
Available Resources
Resources provide real-time, read-only access to Frida state via URI.
Direct Resources
URI | Description |
| List all connected Frida devices |
| List all active Frida sessions and their statuses |
Resource Templates
URI Template | Description |
| Get detailed information about a specific device by ID |
| List processes on a specific Frida device. Use "local", "usb", or "remote" for automatic device selection, provide a specific device ID, or use a connection string (hostname:port or hostname). |
| Find a process by name (case-insensitive partial match) on a specific device. Supports connection strings (hostname:port or hostname). |
| Get main module information for a process (path, base address, size). Supports connection strings (hostname:port or hostname). |
| Retrieve messages from persistent scripts. Append
to limit results (e.g.,
for last 10 messages) or
for unlimited. Default limit is 100 messages. Messages are consumed when retrieved. |
This server cannot be installed
hybrid server
The server is able to function both locally and remotely, depending on the configuration or use case.
Enables dynamic instrumentation of running processes through Frida, allowing users to hook functions, inspect memory, modify process behavior, and execute JavaScript code for debugging and reverse engineering.