Skip to main content
Glama
frida-mcp
by SnowLuma

frida-mcp

미니멀한 Frida MCP 서버.

설계 철학

  • Attach → LoadScript → Call/Listen → Unload의 최단 워크플로우

  • Frida 코퍼스는 대부분의 모델이 광범위하게 학습함 즉시 사용 가능

  • 도구 수 최소화 단 6개의 도구만 노출, 적을수록 좋으며 컨텍스트가 간결함

Related MCP server: Frida MCP

도구 목록

도구

용도

attach

프로세스(PID 또는 프로세스 이름)에 Frida 연결. 프로세스 detach/crash 후에는 반드시 다시 호출해야 함

detach

현재 프로세스를 능동적으로 연결 해제하고 모든 지속적 스크립트를 언로드함. 대상 변경 전 호출에 적합

load_script

지속적 Frida JS를 로드함. rpc.exports = {...}를 정의할 수 있으며 send(data)를 사용하여 로그를 출력할 수 있음

call_rpc

load_script로 등록된 RPC 메서드를 호출하고 결과를 동기적으로 반환함

get_script_output

스크립트의 send(...) 메시지 큐를 가져오고 비움(tail log와 유사)

unload_script

지속적 스크립트를 언로드하고 정리함

설치

소스 코드에서 빌드:

npm install
npm run build

또는 Release에서 다운로드: GitHub Releases에서 플랫폼에 맞는 압축 파일(win-x64 / linux-x64 / macos-arm64)을 선택하여 압축을 풀면 바로 사용할 수 있으며, npm install은 필요하지 않습니다:

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

사용법

직접 실행 (선택적으로 PID 사전 연결)

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

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

MCP 클라이언트 설정

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

Thanks

  • Claude - AI 프로그래밍 어시스턴트

  • Frida - 동적 계측 프레임워크

  • MCP - 모델 컨텍스트 프로토콜

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