Skip to main content
Glama
IDA MCP

IDA MCP

Official
by HexRaysSA

IDA MCP

⚠️ 实验性预发布版本 ️

此仓库正在积极开发中(WIP),请勿使用。

IDA GUI 插件

为了在使用 IDA MCP 时支持 IDA GUI 实例,请安装该插件:

uvx ida-hcli plugin install https://github.com/HexRaysSA/ida-mcp
# or if you have hcli installed:
hcli plugin install https://github.com/HexRaysSA/ida-mcp

注意:如果没有 GUI 插件,IDA MCP 将只能在无头模式下运行。

Related MCP server: IDA MCP

MCP 安装

要求

  • 已安装至你的 PATH

  • IDA 9.4 或更高版本,附带 idalib 和 Python 3.11+

  • 必须禁用其他 IDA MCP 服务器,以减少智能体的困惑。

Claude Code

claude plugin marketplace add HexRaysSA/claude-marketplace
claude plugin install ida-mcp@HexRaysSA

Codex CLI

codex plugin marketplace add HexRaysSA/codex-marketplace
codex plugin add ida-mcp@HexRaysSA

Pi

pi install git:github.com/HexRaysSA/ida-mcp@latest

oh-my-pi

omp plugin install github:HexRaysSA/ida-mcp#latest

其他智能体

在你的 MCP JSON 配置中配置一个常规的 stdio MCP 服务器:

{
  "mcpServers": {
    "ida": {
      "command": "uvx",
      "args": [
        "ida-nexus",
        "mcp",
        "--agent=my-agent"
      ]
    }
  }
}

uvx 会从 PyPI 解析最新的 ida-nexus 稳定版本,因此无需为每个版本更新此配置。当前需要预发布依赖解析,因为 ida-domain 是以开发版本的形式发布的。

--agent=my-agent 是一个由人工选择的标签(例如 claude-code、cursor、my-custom-agent 等),用于在指标仪表板中区分不同的会话。

我们测试了以下客户端,但任何 MCP 客户端都应能类似地工作:

示例用法

启动你的 agent harness 并询问它类似这样的问题:

帮我逆向 /path/to/sample.elf

要测试 GUI 集成,请在 IDA 中打开某个文件,然后询问你的 agent harness:

我在 IDA GUI 中打开了什么?

开发者:IDA Nexus

IDA MCP 项目构建于 IDA Nexus 之上,它允许多个客户端无缝地共享和操作 IDA 数据库。

你可以基于 ida-nexus 库构建自己的工具,更多信息请参阅 文档。

Available Tools

6 tools
close_databaseA

Release this MCP's IDA Nexus database handle without disrupting other clients.

If this is the final lease on a managed idalib worker, orphaned execution is cancelled and this call waits for the IDB to finish closing. GUI databases are never closed here.

Inputs: instance_id. Returns: closed

execute_pythonA

Execute Python and return its result plus captured stdout and stderr.

Inputs: code (required), timeout, instance_id. Returns: result, stderr, stdout

list_databasesA

Discover registered GUI and idalib databases in IDA Nexus.

Inputs: no named parameters. Returns: hint, instances

open_databaseB

Attach to a GUI database or shared managed idalib worker through IDA Nexus.

Inputs: path (required), set_current. Returns: hint, status, backend, log_path, +3 more

referenceA

Look up the active ida-domain API and return a plain-text IDA reference.

Inputs: query (required).

save_databaseA

Explicitly save an active GUI or idalib database.

Inputs: instance_id. Returns: path

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 clearly distinct purpose: reference for API lookup, open_database for attaching, execute_python for running code, list_databases for discovery, save_database for persistence, and close_database for cleanup. No two tools overlap in functionality, making misselection unlikely.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (open_database, list_databases, save_database, close_database, execute_python). The exception is 'reference', which is a noun and deviates from the verb-first convention, but it remains clear and unambiguous, so the minor inconsistency is acceptable.

    Tool Count5/5

    Six tools is well within the ideal range for a focused server. Each tool covers a distinct operation necessary for IDA database interaction and Python execution, with no redundancy or bloat.

    Completeness4/5

    The surface covers the core lifecycle (open, list, save, close) and execution (execute_python) along with reference lookup. While there is no explicit 'create database' or 'get database info' tool, execute_python can handle arbitrary operations, mitigating any gaps. Minor missing features like status checks are workable.

    Maintenance

    ActivityMaintained
    ResponsivenessMixed handling

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      C
      quality
      D
      maintenance
      Enables AI-assisted reverse engineering in IDA Pro by providing tools to analyze binaries, decompile functions, manage comments, search patterns, and interact with the IDA database through natural language.
      56
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to inspect, reverse engineer, decompile, and operate on binaries through IDA Pro, including headless and GUI sessions, over stdio or Streamable HTTP.
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to drive IDA Pro for reverse engineering and binary analysis, including running Python scripts inside the disassembler, extracting strings, imports, exports and functions, searching for immediate values, text and byte sequences, and retrieving disassembly for address ranges.
      -