MCP server and Claude Code plugin for connecting IDA Pro or headless idalib to AI assistants for reverse engineering, decompilation, xref lookup, renaming, commenting, and binary analysis workflows.
Reverse engineering may be legally or contractually restricted; confirm authorization before analyzing proprietary binaries or third-party samples., Malware samples and exploit tooling should be handled in isolated environments with network and filesystem controls., LLMs can hallucinate reverse-engineering conclusions; verify findings against disassembly, decompiler output, xrefs, and reproducible scripts., Do not let an agent patch, rename, comment, or save IDA databases used for evidence without review and backups.
Privacy notes
Binaries, IDA databases, symbol names, strings, comments, decompiler output, and vulnerability findings may be sent to the MCP client and model., Proprietary firmware, customer crash samples, malware indicators, license keys, and embedded secrets can appear in extracted strings or decompiled code., Reports and prompts may reveal unreleased product internals or sensitive security research.
Author
mrexodia
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
4 safety and 3 privacy notes across 6 risk areas. Review closely: credentials & tokens, permissions & scopes, network access, third-party handling.
6 areas
SafetyPermissions & scopesReverse engineering may be legally or contractually restricted; confirm authorization before analyzing proprietary binaries or third-party samples.
SafetyNetwork accessMalware samples and exploit tooling should be handled in isolated environments with network and filesystem controls.
SafetyExecution & processesLLMs can hallucinate reverse-engineering conclusions; verify findings against disassembly, decompiler output, xrefs, and reproducible scripts.
SafetyGeneralDo not let an agent patch, rename, comment, or save IDA databases used for evidence without review and backups.
PrivacyThird-party handlingBinaries, IDA databases, symbol names, strings, comments, decompiler output, and vulnerability findings may be sent to the MCP client and model.
PrivacyCredentials & tokensProprietary firmware, customer crash samples, malware indicators, license keys, and embedded secrets can appear in extracted strings or decompiled code.
PrivacyGeneralReports and prompts may reveal unreleased product internals or sensitive security research.
Safety notes
Reverse engineering may be legally or contractually restricted; confirm authorization before analyzing proprietary binaries or third-party samples.
Malware samples and exploit tooling should be handled in isolated environments with network and filesystem controls.
LLMs can hallucinate reverse-engineering conclusions; verify findings against disassembly, decompiler output, xrefs, and reproducible scripts.
Do not let an agent patch, rename, comment, or save IDA databases used for evidence without review and backups.
Privacy notes
Binaries, IDA databases, symbol names, strings, comments, decompiler output, and vulnerability findings may be sent to the MCP client and model.
Proprietary firmware, customer crash samples, malware indicators, license keys, and embedded secrets can appear in extracted strings or decompiled code.
Reports and prompts may reveal unreleased product internals or sensitive security research.
Prerequisites
IDA Pro 8.3 or newer, with IDA Pro 9 recommended; IDA Free is not supported.
Python 3.11 or newer and uv.
Globally activated idalib for the headless Claude Code plugin path.
Supported MCP client such as Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI, or another documented host.
Authorization to analyze each binary, firmware image, sample, or database used with the tool.
IDA Pro MCP connects IDA Pro and headless idalib workflows to MCP clients. It
lets an AI assistant retrieve decompilation, inspect disassembly, follow xrefs,
rename functions and variables, add comments, and build reverse-engineering
reports from actual IDA analysis.
The project supports a Claude Code plugin path and manual MCP server options for
GUI IDA or headless idalib sessions.
These sources were reviewed on 2026-06-05. Prefer the live repository for
current IDA version support, plugin status, idalib-mcp commands, transport
options, and supported MCP clients.
Features
Claude Code plugin install through the documented marketplace.
GUI IDA plugin integration and headless idalib-mcp support.
Decompilation, disassembly, xref, naming, typing, and commenting workflows.
Stdio, SSE/HTTP, and shared stdio modes documented by the project.
Multi-database headless session support.
Prompting guidance for reverse-engineering workflows.
Installation
For Claude Code plugin setup:
claude plugin marketplace add mrexodia/claude-marketplace
claude plugin install ida-pro-mcp@mrexodia
Follow the repository instructions for activating idalib and choosing GUI,
headless, stdio, shared stdio, or SSE transports.
Use Cases
Analyze a crackme or malware sample with decompiler and xref context.
Rename functions, variables, and types after human-reviewed analysis.
Generate reverse-engineering notes from IDA evidence.
Ask a model to compare decompilation with disassembly for tricky functions.
Use headless idalib to analyze multiple binaries from one MCP server.
Safety and Privacy
Reverse-engineering workflows can involve sensitive or regulated material. Work
only on binaries you are authorized to inspect, isolate suspicious samples, and
verify every model-generated conclusion against IDA output. Keep backups before
allowing an agent to modify comments, names, types, or saved database state.
Duplicate Check
No mrexodia/ida-pro-mcp entry or source URL was found in content/mcp. This
entry is separate from Ghidra MCP and other security-analysis content.
Show that IDA Pro MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/ida-pro-mcp-server)
How it compares
IDA Pro MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
MCP server and Claude Code plugin for connecting IDA Pro or headless idalib to AI assistants for reverse engineering, decompilation, xref lookup, renaming, commenting, and binary analysis workflows.
Apache-licensed Ghidra MCP bridge with GUI and headless workflows for binary analysis, decompilation, scripting, debugger access, batch operations, and Ghidra Server collaboration.
Ghidra plugin and MCP bridge that lets AI assistants inspect, decompile, rename, comment, and analyze binaries through Ghidra reverse-engineering workflows.
✓Reverse engineering may be legally or contractually restricted; confirm authorization before analyzing proprietary binaries or third-party samples.
Malware samples and exploit tooling should be handled in isolated environments with network and filesystem controls.
LLMs can hallucinate reverse-engineering conclusions; verify findings against disassembly, decompiler output, xrefs, and reproducible scripts.
Do not let an agent patch, rename, comment, or save IDA databases used for evidence without review and backups.
✓Use this server only for binaries and systems you are authorized to inspect, debug, emulate, modify, document, or reverse engineer.
The tool surface includes write-capable operations such as renaming, typing, commenting, label changes, script execution, structure creation, and project/version-control workflows.
Unknown binaries, malware samples, debugger targets, and imported scripts can be dangerous; isolate analysis environments and avoid running untrusted code on a primary workstation.
Headless, Docker, CI, and Ghidra Server workflows can affect shared repositories or automated pipelines if configured with write access.
Keep human review on operations that change analysis state, scripts, project metadata, or shared Ghidra Server content.
✓Reverse engineering may be legally restricted; confirm authorization before analyzing third-party or proprietary binaries.
Malware, exploit samples, and unknown binaries should be handled in isolated environments with limited network and filesystem access.
LLM-generated names, comments, and conclusions must be verified against Ghidra decompiler output, disassembly, imports, exports, and xrefs.
Keep backups of Ghidra projects before allowing an agent to rename symbols, alter comments, or save project state.
✓Use this server only for APKs and Android applications you own, are responsible for, or are explicitly authorized to inspect.
The plugin exposes decompiled classes, methods, fields, smali, manifests, strings, resources, xrefs, and debugger state to the MCP client.
Rename and refactor tools can modify JADX project state and naming decisions; review changes before saving project output or using generated reports.
The architecture docs describe a local plugin service with no built-in authentication; keep it bound to localhost unless you add network controls.
Optional HTTP mode for the MCP server should not be exposed to untrusted networks without authentication, TLS, and firewall restrictions.
Decompiled strings, manifests, and resources can contain prompt-injection text or untrusted content; treat tool output as untrusted input.
Privacy notes
✓Binaries, IDA databases, symbol names, strings, comments, decompiler output, and vulnerability findings may be sent to the MCP client and model.
Proprietary firmware, customer crash samples, malware indicators, license keys, and embedded secrets can appear in extracted strings or decompiled code.
Reports and prompts may reveal unreleased product internals or sensitive security research.
✓Tool calls may expose binary names, file paths, hashes, strings, imports, exports, symbols, decompiled code, comments, type names, project names, repository URLs, debugger state, memory reads, and trace metadata.
Reverse engineering projects often contain proprietary firmware, customer binaries, vulnerability findings, credentials embedded in samples, exploit indicators, and private research notes.
MCP client logs, model transcripts, Ghidra project history, Docker volumes, CI logs, and Ghidra Server repositories may retain sensitive analysis data.
Do not commit private binaries, generated Ghidra projects, debugger traces, analysis exports, credentials, proprietary symbols, or customer-specific reverse engineering notes.
✓Binaries, function names, strings, imports, exports, decompilation output, comments, and analysis notes may be sent to the MCP client and model.
Extracted strings and decompiled code can expose proprietary logic, credentials, API endpoints, malware indicators, or customer data.
Generated reports can reveal sensitive vulnerability research or product internals.
✓APK source, package names, manifests, resources, strings, selected text, debugger variables, and analysis prompts may be sent to the model provider.
Debugger tools can expose runtime values, tokens, identifiers, device data, or user information from the analyzed application.
Reverse-engineering work can reveal proprietary code, licensed assets, customer data, or confidential security findings.
Avoid uploading malware samples, third-party apps, client applications, or regulated data to external model providers without approval.
Prerequisites
IDA Pro 8.3 or newer, with IDA Pro 9 recommended; IDA Free is not supported.
Python 3.11 or newer and uv.
Globally activated idalib for the headless Claude Code plugin path.
Supported MCP client such as Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI, or another documented host.
Ghidra 12.1 or a compatible version installed and available on the local machine or analysis host.
Java 21, Maven 3.9 or newer, Python 3.10 or newer, and Python package installation available.
Ghidra extension deployment permissions for the user profile or headless environment.
Authorization to analyze the binaries, firmware, traces, symbols, and shared Ghidra projects loaded into the tool.
Installed Ghidra.
Python 3.
MCP Python SDK dependencies required by the project.
Latest GhidraMCP release zip imported as a Ghidra extension.
Java 11 or newer and JADX-GUI installed.
Python and uv available for installing or running the companion MCP server.
The JADX AI MCP plugin installed in JADX-GUI.
An Android APK, JADX project, or reverse-engineering target you are authorized to analyze.
Install
claude plugin marketplace add mrexodia/claude-marketplace && claude plugin install ida-pro-mcp@mrexodia