Ida Pro MCP logo

Ida Pro MCP

by mrexodia

Connects AI assistants to IDA Pro for decompilation, disassembly, database changes, and reverse-engineering workflows.

Install Ida Pro MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mrexodia-ida-pro-mcp": {
      "command": "uvx",
      "args": [
        "https"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command didn't complete successfully in our automated test.

uvx https

error: No solution found when resolving tool dependencies cause: Because there are no versions of https and you require https, we can conclude that your requirements are unsatisfiable.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

The mrexodia/ida-pro-mcp MCP server connects supported AI clients to IDA Pro for binary analysis. It exposes workflows around decompilation, disassembly, database inspection, comments, renaming, and type changes, with an integer-conversion tool for analysis prompts. It requires Python 3.11 or newer, IDA Pro 8.3 or newer, activated idalib, and uv. Use it when an agent needs to inspect or annotate binaries inside IDA Pro; headless analysis is available through the related idalib-mcp mode.

Use cases

  • Analyze crackmes with decompilation and disassembly
  • Inspect suspicious binaries in IDA Pro
  • Annotate functions and rename variables during reverse engineering
  • Generate Markdown findings from an analysis session

Key features

  • IDA Pro decompilation access
  • Disassembly inspection
  • Database comments, renaming, and type updates
  • Integer conversion through int_convert
  • stdio and HTTP/SSE transports
  • Headless idalib database workers

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

28/33 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · https (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars13kStargazers on the source repository.
Last commit1mo agoMost recent push to the default branch.
Install checkInconclusiveInstall command did not finish in our automated test.
Directory activity14 viewsConfig copies, upvotes, and views on AllMCPs.

How Ida Pro MCP works

What mrexodia/ida-pro-mcp does

The mrexodia/ida-pro-mcp MCP server lets an MCP-compatible AI client work with an IDA Pro analysis database. Its intended use is interactive reverse engineering: an agent can retrieve analysis information, inspect decompiler output, examine assembly when needed, and improve the database by adding comments, renaming functions or variables, and correcting types.

The project is aimed at binary-analysis workflows such as crackme investigation and malware analysis. Results depend on the quality of the underlying IDA analysis and on how specifically the agent is prompted.

How it works

The server runs alongside IDA Pro and makes IDA analysis operations available through MCP. A supported client sends requests to the server, which works against the open analysis database. The project supports stdio and HTTP/SSE operation. An SSE endpoint can be started on a local address, while stdio is intended for clients that launch the process directly.

For headless use, the repository documents the idalib-mcp supervisor. It can open a binary at startup or start without one and later load files with idb_open(...). Each open database uses its own worker process. Workers can outlive the supervisor, can be adopted by a later supervisor on the same host, and exit after an idle period without requests.

Setup and configuration

Use Python 3.11 or later and IDA Pro 8.3 or later; IDA Free is not supported. The README recommends IDA 9 and requires idalib to be activated globally with idapyswitch. The activation step uses the Python activation script shipped with the local IDA installation. The uv tool must also be installed and available on PATH.

Installation options include plugins for Claude Code and Codex, a Kimi Code plugin, and manual GUI installation. The manual route installs the project from its GitHub archive and then runs ida-pro-mcp --install to configure the MCP servers and IDA plugin. IDA and the MCP client must be fully restarted after that installation.

Tools and capabilities

The documented workflow supports:

  • Retrieving decompiler output and disassembly for investigation.
  • Adding analysis comments to the IDA database.
  • Renaming functions and variables to clarify behavior.
  • Changing function, variable, and argument types, including pointer and array types.
  • Converting integer representations with the int_convert MCP tool.
  • Opening binaries in headless sessions with idb_open(...).
  • Connecting through stdio or an HTTP/SSE transport.

The mrexodia/ida-pro-mcp MCP server is intended to help an agent derive conclusions from the binary rather than rely on assumptions. The supplied prompting guidance recommends resolving library code with tools such as Lumina or FLIRT and addressing obfuscation before asking an LLM to analyze difficult samples.

Limitations and notes

IDA Pro licensing and installation are prerequisites, and IDA Free cannot be used. The README warns that language models can hallucinate, especially when interpreting numeric conversions, so prompts should direct them to use int_convert instead of converting bases independently. Obfuscated code—including encrypted strings, import hashing, control-flow flattening, code encryption, and anti-decompilation techniques—can reduce analysis accuracy.

The repository documents automatic report creation as a workflow outcome, not as a substitute for validating the agent's conclusions. For headless operation, use the documented idalib-mcp commands rather than assuming the GUI plugin is required. Database workers are host-local and persistent until their idle timeout; this behavior does not provide a separate shared-mode switch.

The mrexodia/ida-pro-mcp MCP server should therefore be selected when the environment already has a compatible, licensed IDA Pro installation and the user wants an MCP client to assist with reverse engineering inside that environment.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Ida Pro MCP

Manual installation uses pip with the project's GitHub archive, followed by `ida-pro-mcp --install`.

It requires IDA Pro 8.3 or newer. IDA Free is not supported, and the README recommends IDA 9.

Yes. Cursor is listed among the supported MCP clients.

Yes. The documented headless option uses `idalib-mcp`, which can start with a binary or open one later through `idb_open(...)`.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewIda Pro MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mrexodia-ida-pro-mcp?style=directory)](https://allmcps.com/mcp/mrexodia-ida-pro-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/mrexodia-ida-pro-mcp"><img src="https://allmcps.com/api/badge/mrexodia-ida-pro-mcp?style=directory" alt="Ida Pro MCP on AllMCPs" /></a>