Frida MCP Server
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.
README
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
# Clone the repository
git clone https://github.com/nonsleepr/frida-mcp.ts
cd frida-mcp.ts
# Install dependencies
bun install
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
{
"mcpServers": {
"frida": {
"command": "bun",
"args": ["run", "/path/to/frida-mcp.ts/src/index.ts"]
}
}
}
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 (.roo/mcp.json):
{
"mcpServers": {
"frida": {
"command": "bun",
"args": ["run", "src/index.ts"],
"env": {
"FRIDA_REMOTE_HOST": "",
"FRIDA_REMOTE_PORT": "27042"
},
"disabled": false,
"alwaysAllow": []
}
}
}
To use with a remote Frida device:
Edit .roo/mcp.json and set the FRIDA_REMOTE_HOST environment variable:
"env": {
"FRIDA_REMOTE_HOST": "192.168.1.100",
"FRIDA_REMOTE_PORT": "27042"
}
Available Tools
Device & Process Management
| Tool | Description | Parameters |
|---|---|---|
attach_to_process |
Attach to a running process by PID. Returns attachment status without creating a persistent session. Use create_interactive_session for session-based instrumentation. |
pid (number)<br>device_id (optional string or connection string hostname:port) |
spawn_process |
Spawn a process with Frida attached in paused state. The process will be paused at startup. Use resume_process() after loading scripts to continue execution. |
program (string)<br>args (optional string[])<br>device_id (optional string or connection string) |
resume_process |
Resume a spawned process. | pid (number)<br>device_id (optional string or connection string) |
kill_process |
Kill a process by PID. | pid (number)<br>device_id (optional string or connection string) |
Interactive Sessions
| Tool | Description | Parameters |
|---|---|---|
create_interactive_session |
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. | process_id (number)<br>device_id (optional string or connection string) |
execute_in_session |
Execute JavaScript code within an existing Frida session.<br><br>Modes:<br>• keep_alive=false (default): Script runs once, results in initial_logs<br>• keep_alive=true: Script persists for hooks, retrieve messages via frida://sessions/{session_id}/messages resource |
session_id (string)<br>javascript_code (string)<br>keep_alive (optional boolean, default: false) |
load_script_file |
Load and execute a Frida JavaScript file into an existing session. | session_id (string)<br>script_path (string)<br>keep_alive (optional boolean, default: true) |
File Operations
| Tool | Description | Parameters |
|---|---|---|
download_file |
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. | file_path (string)<br>output_path (string)<br>pid (optional number)<br>device_id (optional string or connection string) |
Available Resources
Resources provide real-time, read-only access to Frida state via URI.
Direct Resources
| URI | Description |
|---|---|
frida://devices |
List all connected Frida devices |
frida://sessions |
List all active Frida sessions and their statuses |
Resource Templates
| URI Template | Description |
|---|---|
frida://devices/{device_id} |
Get detailed information about a specific device by ID |
frida://devices/{device_id}/processes |
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). |
frida://devices/{device_id}/processes/by-name/{process_name} |
Find a process by name (case-insensitive partial match) on a specific device. Supports connection strings (hostname:port or hostname). |
frida://devices/{device_id}/processes/{pid}/module |
Get main module information for a process (path, base address, size). Supports connection strings (hostname:port or hostname). |
frida://sessions/{sessionId}/messages |
Retrieve messages from persistent scripts. Append /last:N to limit results (e.g., /last:10 for last 10 messages) or /all for unlimited. Default limit is 100 messages. Messages are consumed when retrieved. |
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.