Skip to main content
Glama
HexRaysSA

IDA MCP

Official
by HexRaysSA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to IDA MCP

No user-submitted related servers found.

    Related Servers

    • IDA Pro MCP

      icryo
      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
      2
      MIT

    • IDA Pro MCP

      yoavgghuser
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI-powered reverse engineering in IDA Pro by letting MCP clients inspect decompilation and disassembly, rename symbols, convert integers, and otherwise interact with the database through natural language.
      MIT

    • IDAssistMCP

      symgraph
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLM clients like Claude to interact with IDA Pro for binary analysis, decompilation, cross-references, patching, and more via 41 MCP tools, 8 resources, and 7 guided prompts.
      52
      MIT

    • IDA Pro MCP Server

      31Benzi
      A
      license
      B
      quality
      C
      maintenance
      Bridges Claude Code with IDA Pro 9.0+ to provide 87 tools for AI-assisted reverse engineering, including decompilation, navigation, debugging, and patching.
      87
      1
      MIT

    • ida-pro-mcp-dsh

      Xilin3
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to perform binary analysis and reverse engineering via IDA Pro's headless idalib, providing 66 MCP tools like decompile, disasm, and xrefs without requiring the IDA GUI.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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
    ResponsivenessResponsive

    Resources