Skip to main content
Glama
frida-mcp
by SnowLuma

frida-mcp

Ein minimalistischer Frida MCP-Server.

Design-Philosophie

  • Kürzester Workflow: Attach → LoadScript → Call/Listen → Unload

  • Frida-Korpora sind von den meisten Modellen umfassend trainiert: Direkt einsatzbereit

  • Minimale Anzahl an Tools: Nur 6 Tools werden bereitgestellt; weniger ist mehr, der Kontext bleibt schlank

Related MCP server: Frida MCP

Tool-Übersicht

Tool

Zweck

attach

Verbindet Frida mit einem Prozess (PID oder Prozessname). Muss nach einem Detach/Crash des Prozesses erneut aufgerufen werden

detach

Trennt aktiv die Verbindung zum aktuellen Prozess und entlädt alle persistenten Skripte; geeignet für den Aufruf vor einem Zielwechsel

load_script

Lädt ein persistentes Frida-JS-Skript. Kann rpc.exports = {...} definieren und send(data) für Protokollausgaben nutzen

call_rpc

Ruft eine über load_script registrierte RPC-Methode auf und gibt das Ergebnis synchron zurück

get_script_output

Ruft die send(...)-Nachrichtenwarteschlange des Skripts ab und leert sie, ähnlich wie tail log

unload_script

Entlädt und bereinigt persistente Skripte

Installation

Aus dem Quellcode:

npm install
npm run build

Oder als Release herunterladen: Wählen Sie in den GitHub Releases das für Ihre Plattform passende Archiv aus (win-x64 / linux-x64 / macos-arm64). Nach dem Entpacken ist es sofort einsatzbereit, npm install ist nicht erforderlich:

# 解压后会得到 frida-mcp/ 目录
node frida-mcp/dist/index.js

Verwendung

Direktstart (optional mit vorab angehängter PID)

# 不带参数启动,由 LLM 通过 attach 工具连接
node dist/index.js

# 或启动时直接 attach 到 PID
node dist/index.js 12345

MCP-Client-Konfiguration

{
  "mcpServers": {
    "frida": {
      "command": "node",
      "args": ["e:/mcp-ida-frida/dist/index.js"]
    }
  }
}

Dank

  • Claude - KI-Programmierassistent

  • Frida - Framework für dynamische Instrumentierung

  • MCP - Model Context Protocol

Available Tools

6 tools
attachAttach 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

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An 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.
      468
      MIT
    • A
      license
      B
      quality
      Not graded
      maintenance
      Enables 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.
      14
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      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.
      3
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      A 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.
      2
      100
      4
      MIT