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 Attach to notepad and load script to intercept WriteFile calls"
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 minimalist Frida MCP server.
Design Philosophy
Shortest workflow: Attach → LoadScript → Call/Listen → Unload
Frida corpus is widely trained by most models: Ready to use directly
Minimal toolset: Only 6 tools exposed; less is more, keeping context concise
Related MCP server: Frida MCP
Tool Overview
Tool | Purpose |
| Attach Frida to a process (PID or process name). Must be called again after process detach/crash |
| Manually disconnect from the current process and unload all persistent scripts; suitable for use before switching targets |
| Load a persistent Frida JS script. Can define |
| Call an RPC method registered by |
| Fetch and clear the script's |
| Unload and clean up persistent scripts |
Installation
From source:
npm install
npm run buildOr download from Releases: Select the archive corresponding to your platform (win-x64 / linux-x64 / macos-arm64) from GitHub Releases, extract it, and use it directly without npm install:
# 解压后会得到 frida-mcp/ 目录
node frida-mcp/dist/index.jsUsage
Direct Launch (Optional pre-attach PID)
# 不带参数启动,由 LLM 通过 attach 工具连接
node dist/index.js
# 或启动时直接 attach 到 PID
node dist/index.js 12345MCP Client Configuration
{
"mcpServers": {
"frida": {
"command": "node",
"args": ["e:/mcp-ida-frida/dist/index.js"]
}
}
}Thanks
Available Tools
6 toolsattachAttach to ProcessA
Attach Frida to a process. AI MUST call this first, and MUST call it again whenever any other tool reports that the process is detached or crashed.
Inputs: target (required).
call_rpcCall RPC MethodA
Call a function exported by a persistent script loaded via load_script. If this fails because the process is detached/crashed, call the attach tool again and then load_script before retrying.
Inputs: script (required), method (required), args.
detachDetach from ProcessA
Detach Frida from the current process and unload all persistent scripts. Call this when finished with the target or before attaching to a different process. After detach you MUST call attach again before any other tool.
Inputs: no named parameters.
get_script_outputGet Script OutputA
Retrieve accumulated messages (send(data)) from a persistently loaded script and clear its message queue. Similar to tailing a log.
Inputs: name (required).
load_scriptLoad Persistent ScriptA
Load a persistent background Frida script. Use this to set up hooks that collect data over time or long-running RPC exports. Afterwards, use call_rpc to invoke functions or get_script_output to check logs. If this fails because the process is detached/crashed, call the attach tool again and retry.
Inputs: name (required), source (required).
unload_scriptUnload Persistent ScriptC
Securely unload and clean up a persistent script.
Inputs: name (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a clear, distinct purpose: attach/detach for lifecycle, load_script/unload_script for script management, call_rpc for function invocation, and get_script_output for log retrieval. There is no overlap or ambiguity between tools.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., attach, load_script, call_rpc), making them predictable and easy to understand.
With 6 tools, the set is well-scoped for the purpose of Frida process attachment and persistent script management. Each tool serves a necessary step in the workflow without being excessive or insufficient.
The tool set covers the core workflow of attaching, detaching, loading/unloading scripts, calling RPC, and retrieving output. However, it lacks support for ad-hoc scripts or advanced Frida operations, which might be a minor gap for some use cases.
Maintenance
Related MCP Connectors
Remote MCP for Android CLI agent build gate, structured receipts, audit logs, and reviewer-ready evi
Remote MCP service for evidence-backed work memory and continuity.
Search and inspect source-pinned agent skills, plugins and tools through a free public MCP.
An authenticated remote MCP server for user-owned devices and one-shot capability invocation.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP-compliant server that enables AI systems to interact with mobile and desktop applications through Frida's dynamic instrumentation capabilities, allowing for process management, device control, JavaScript execution, and script injection.468MIT
- AlicenseBqualityNot gradedmaintenanceEnables AI systems to interact with mobile and desktop applications through Frida's dynamic instrumentation capabilities. Provides process management, device control, JavaScript REPL execution, and script injection for runtime analysis and reverse engineering.142MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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.3MIT
- AlicenseCqualityDmaintenanceA Frida MCP server for authorized dynamic analysis and application security research, exposing device/session management, script injection, process and memory inspection, and platform-specific workflows.21004MIT