IDA Pro MCP
Related Servers
Alternatives to IDA Pro MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceEnables AI agents and external tools to perform reverse engineering on compiled binaries through IDA, including decompilation, disassembly, cross-references, type management, patching, signature generation, and dynamic debugging.7972 npmMIT
- AlicenseAqualityAmaintenanceEnables AI agents to interact with IDA Pro databases and GUI, supporting reverse engineering tasks such as analyzing binaries and querying open files via natural language.672 npm7,577 PyPI1,468MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to inspect, reverse engineer, decompile, and operate on binaries through IDA Pro, including headless and GUI sessions, over stdio or Streamable HTTP.72 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients such as Claude, Cursor, Cline, and Codex to remotely drive IDA Pro over HTTP through 88 tools, covering Hex-Rays decompilation, disassembly, cross-reference tracing, type and struct reconstruction, C header import, memory reading and patching, and full dynamic debugging with breakpoints, registers, and stepping.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to drive IDA Pro for reverse engineering and binary analysis by executing Python scripts, listing strings, imports, exports, and functions, searching for immediate values, text, and byte sequences, and retrieving disassembly for address ranges. All operations are brokered over a localhost HTTP bridge to a running IDA Pro instance.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to control IDA Pro for reverse engineering and binary analysis by running Python scripts and querying binaries. It supports retrieving strings, imports, exports, and functions, searching immediate values, text, and byte sequences, and getting disassembly for address ranges over a secure local HTTP bridge.-
TDQS
Scored across 66 tools
Several tools appear to duplicate each other: instance_list vs list_instances both list IDA instances, imports vs imports_query, list_funcs vs func_query, and xrefs_to vs xref_query cover overlapping ground. Analysis tools (analyze_function, analyze_component, analyze_batch, func_profile, survey_binary) also overlap heavily, making selection between them uncertain.
The conventions are mixed: some tools are verb_noun (list_funcs, get_bytes, find_regex), others noun_verb (xrefs_to), others bare nouns (decompile, disasm, patch, rename, callees). The most glaring flaw is instance_list vs list_instances, the same concept with inverted word order.
At 66 tools this is far above a comfortable surface, and a meaningful subset are redundant query variants (imports_query, func_query, xref_query, entity_query) or near-duplicate instance/signature helpers. The domain is broad but the count is inflated by overlapping tools rather than distinct capabilities.
The surface is remarkably thorough for binary reverse engineering: decompilation, disassembly, xrefs, callgraphs, read/write/patch of memory and code, stack frames, type declaration, signatures, comments, renaming, and cache management are all present. Only minor lifecycle gaps (e.g. segment-level operations, richer diffing) seem missing.