Skip to main content
Glama
HexRaysSA

IDA MCP

Official
by HexRaysSA

Related Servers

Alternatives to IDA MCP

No user-submitted related servers found.

    Related 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
      3
      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.
      26 npm
      MIT
    • 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.
      2
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Enables large language models to read and write IDA Pro databases through structured tool calls for reverse engineering, binary analysis, and hook development. Provides broker-based routing, SQLite-backed static caching, multi-instance analysis, and both cached and live IDA API queries.
      66
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to autonomously inspect and control IDA Pro via MCP, providing tools for decompilation, disassembly, cross-references, renaming, typing, patching, searching, debugging, and arbitrary IDAPython execution.
      MIT

    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

    ActivityActive
    ResponsivenessResponsive