MCP Servers

A collection of Model Context Protocol servers, templates, tools and more.

I
Ida Multi MCP
by @MeroZemory
GitHub Repo(1 stars)

Multi-instance IDA Pro MCP server — analyze multiple binaries simultaneously through a single MCP endpoint.

Created 1/29/2026
Updated 26 days ago
README
View Source
Repository documentation and setup instructions

ida-multi-mcp

Multi-instance IDA Pro MCP server for simultaneous reverse engineering of multiple binaries through a single MCP endpoint.

Overview

ida-multi-mcp enables you to analyze multiple binaries in parallel using IDA Pro, with all instances accessible through a single MCP connection. Instead of juggling multiple MCP client configurations, you open multiple IDA instances and the server automatically discovers and routes requests to each.

MCP Client (Claude, Cursor, etc.)
    │  stdio (MCP Protocol)
    ▼
┌─────────────────────────────────┐
│  ida-multi-mcp Server (Router)  │
│  - Dynamic tool discovery       │
│  - instance_id injection        │
│  - Management tools             │
└───┬──────┬──────┬───────────────┘
    │      │      │  HTTP JSON-RPC
    ▼      ▼      ▼
  IDA #1  IDA #2  IDA #3
  (auto)  (auto)  (auto)

Key Features

  • Zero-configuration instance discovery — Each IDA Pro instance auto-registers on startup
  • Port-collision free — Uses OS auto-assigned ports (port 0)
  • Dynamic tool discovery — All 71+ IDA tools available automatically
  • Cross-binary analysis — Target specific instances via instance_id parameter
  • Smart instance tracking — 4-character IDs (k7m2, px3a, etc.) with automatic binary-change detection
  • File-based registry — Tracks all active instances
  • Graceful fallback — Handles binary changes, stale instances, and crashes

Requirements

  • Python 3.11 or later
  • IDA Pro 8.3+ (9.0 recommended)

Installation

For Humans

The easiest way to install is to let your AI agent handle it. Copy and paste one of these prompts into your AI tool:

Claude Code / AmpCode:

Install and configure ida-multi-mcp by following the instructions here: https://raw.githubusercontent.com/MeroZemory/ida-multi-mcp/main/docs/installation.md

Cursor:

@Web fetch https://raw.githubusercontent.com/MeroZemory/ida-multi-mcp/main/docs/installation.md and follow the installation steps.

Or install manually:

macOS

Important: IDA Pro typically uses a different Python version than your system default (e.g., IDA uses Python 3.11 while macOS ships with 3.14). You must install the package for both your terminal Python and IDA's Python.

Step 1: Check IDA's Python version

Open IDA Pro, then in the IDA console run:

Python> import sys; print(sys.version)

Note the version (e.g., 3.11).

Step 2: Install

# 1. Install CLI tool via pipx (for terminal commands)
pipx install git+https://github.com/MeroZemory/ida-multi-mcp.git

# 2. Install package for IDA's Python (replace 3.11 with your IDA's version)
python3.11 -m pip install --user git+https://github.com/MeroZemory/ida-multi-mcp.git

# 3. Install IDA plugin + configure MCP clients
ida-multi-mcp --install

# 4. Configure Claude Code manually (recommended over --install for Claude Code)
claude mcp add ida-multi-mcp -s user -- ida-multi-mcp

Note: ida-multi-mcp --install registers MCP servers using python3 -m ida_multi_mcp, which may point to the wrong Python version on macOS. For Claude Code, use claude mcp add as shown above to ensure it uses the pipx-managed CLI directly.

Windows

# 0. (Recommended) Clean previous install to avoid stale scripts/config
ida-multi-mcp --uninstall
python -m pip uninstall -y ida-multi-mcp

# 1. Install ida-multi-mcp
python -m pip install git+https://github.com/MeroZemory/ida-multi-mcp.git

# 2. Install IDA plugin + configure all MCP clients
ida-multi-mcp --install

If IDA uses a different Python version than your default, use py -3.12 (replace with IDA's version) instead of python.

Linux

# 1. Install ida-multi-mcp
pip install --user git+https://github.com/MeroZemory/ida-multi-mcp.git

# 2. Install IDA plugin + configure MCP clients
ida-multi-mcp --install

For AI Agents

Fetch and follow the installation guide:

curl -s https://raw.githubusercontent.com/MeroZemory/ida-multi-mcp/main/docs/installation.md

The guide covers:

  1. Platform-specific package installation (macOS, Windows, Linux)
  2. IDA Python version matching
  3. IDA plugin setup + MCP client auto-configuration (ida-multi-mcp --install)
  4. Verification and troubleshooting

Supported MCP Clients

Works with any MCP-compatible client. Tested with:

| Client | Type | |--------|------| | Claude Code | CLI | | Claude Desktop | Desktop | | Cursor | IDE | | VS Code (Copilot) | IDE | | Windsurf | IDE | | Zed | IDE | | Augment Code | IDE | | Cline | Extension | | Kilo Code | Extension | | Kiro | IDE | | LM Studio | Desktop | | Opencode | CLI | | Qodo Gen | Extension | | Roo Code | Extension | | Trae | IDE | | Warp | Terminal | | Amazon Q Developer CLI | CLI | | Copilot CLI | CLI | | Gemini CLI | CLI |

MCP Client Configuration

ida-multi-mcp --install automatically configures all detected MCP clients:

  • Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, Zed, and 20+ more

For clients not auto-detected or to view the configuration JSON, run:

ida-multi-mcp --config

Uninstallation

macOS

# 1. Remove IDA plugin + MCP client configurations
ida-multi-mcp --uninstall

# 2. Remove packages
pipx uninstall ida-multi-mcp
python3.11 -m pip uninstall -y ida-multi-mcp  # replace 3.11 with IDA's version

Windows

# 1. Remove IDA plugin + MCP client configurations
ida-multi-mcp --uninstall

# (optional) If IDA is installed in a custom location
ida-multi-mcp --uninstall --ida-dir "C:\Program Files\IDA Pro 9.0"

# 2. Remove the Python package
python -m pip uninstall -y ida-multi-mcp

After uninstalling, fully restart IDA Pro and your MCP client(s) so the removed configuration is picked up.

Usage

Opening Multiple Binaries

  1. Open IDA Pro and load your first binary (e.g., malware.exe)

    • Plugin auto-loads (PLUGIN_FIX flag)
    • Instance auto-registers with 4-char ID (e.g., k7m2)

  2. Open another IDA Pro instance with a second binary (e.g., dropper.dll)

    • Another instance auto-registers (e.g., px3a)

  3. Repeat for more binaries

Viewing Registered Instances

ida-multi-mcp --list

Output:

Registered IDA instances (3):

  k7m2
    Binary: malware.exe
    Path: C:/samples/malware.exe
    Arch: x86_64
    Port: 49152
    PID: 12345

  px3a
    Binary: dropper.dll
    Path: C:/samples/dropper.dll
    Arch: x86_64
    Port: 49153
    PID: 12346

  9bf1
    Binary: payload.exe
    Path: C:/samples/payload.exe
    Arch: x86
    Port: 49154
    PID: 12347

Using in Your LLM

Once connected, all 71+ IDA tools are available. All IDA tool calls require the instance_id parameter to avoid cross-agent contention.

Analyzing a single instance:

Decompile the main function in malware.exe (k7m2)

Cross-binary analysis:

Decompile main in malware.exe (k7m2) and compare it with the entry point in dropper.dll (px3a)

Management Tools

The server provides built-in management tools:

list_instances()

Lists all registered IDA instances with metadata (binary name, path, architecture, port).

refresh_tools()

Re-discovers tools from IDA instances. Use this if you update the IDA plugin.

get_cached_output(cache_id: str, offset: int = 0, size: int = 20000)

Retrieve cached output from a previous tool call that was truncated.

decompile_to_file(...)

Decompile functions and save results directly to files on disk. Requires instance_id.

Instance IDs Explained

Instance IDs are 4-character base36 strings (0-9, a-z) like k7m2, px3a, 9bf1.

Why 4 characters?

  • Short and readable
  • 1.68 million combinations (collision-free for typical use)
  • Auto-expands to 5 characters if collision detected

How are they generated?

  • Based on: process ID, port, and IDB file path
  • Same binary reopened = same ID (deterministic)
  • Binary replaced/changed = new ID (automatic)

What happens when you change binaries? When you open a different binary in an IDA instance:

  1. Old instance expires (e.g., k7m2 → expired)
  2. New instance registers (e.g., b12)
  3. If LLM tries to use old ID, you get a helpful error with the replacement ID

CLI Commands

ida-multi-mcp

Start the MCP server (stdio). Used by MCP clients. This is the default command.

ida-multi-mcp

ida-multi-mcp --list

List all registered IDA instances.

ida-multi-mcp --list

ida-multi-mcp --install [--ida-dir DIR]

Install the IDA plugin and auto-configure all detected MCP clients (Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, Zed, and 20+ more).

ida-multi-mcp --install
ida-multi-mcp --install --ida-dir "C:\Program Files\IDA Pro 9.0"  # Windows custom path

ida-multi-mcp --uninstall [--ida-dir DIR]

Remove the IDA plugin, clean up registry, and remove MCP client configurations.

ida-multi-mcp --uninstall

ida-multi-mcp --config

Print the MCP client configuration JSON for easy reference.

ida-multi-mcp --config

Architecture

Instance Registry

Location:

  • macOS/Linux: ~/.ida-mcp/instances.json
  • Windows: %USERPROFILE%\.ida-mcp\instances.json

Each registered instance includes:

  • id — 4-char instance identifier (k7m2, px3a, etc.)
  • pid — Process ID of the IDA Pro instance
  • host — Always 127.0.0.1 (localhost)
  • port — Dynamically assigned HTTP port
  • binary_name — Filename (malware.exe, driver.dll, etc.)
  • binary_path — Full path to binary
  • arch — Architecture (x86_64, x86, arm64, etc.)
  • registered_at — Timestamp when instance registered
  • last_heartbeat — Last heartbeat check timestamp

IDA Plugin Directory

  • macOS/Linux: ~/.idapro/plugins/
  • Windows: %APPDATA%\Hex-Rays\IDA Pro\plugins\

Request Routing

  1. MCP client calls a tool (e.g., decompile) with required instance_id parameter
  2. Server routes to the target instance via HTTP JSON-RPC
  3. IDA instance processes the request
  4. Result returned to client

Health Monitoring

  • Each IDA instance sends a heartbeat every 60 seconds
  • Stale instances (no heartbeat for 2+ minutes) are automatically cleaned up
  • On server startup, dead processes are removed from the registry
  • If an instance crashes, subsequent requests get a helpful error message

Binary Change Detection

Uses dual-strategy detection:

Primary (Fast) — IDA event hooks trigger immediately when binary changes Fallback (Safe) — Every tool call verifies binary hasn't changed, handles hook failures

When a binary change is detected:

  • Old instance ID is marked as expired
  • New instance registers with new ID
  • LLM receives helpful message with replacement ID

Troubleshooting

"No IDA instances registered"

Make sure:

  1. IDA Pro is running with a binary loaded
  2. Check IDA's plugin list (Edit → Plugins → Scan) to confirm ida-multi-mcp plugin loaded
  3. Check IDA console for error messages
  4. Run ida-multi-mcp --list again

"Instance 'k7m2' not found"

The instance has crashed or expired. Run:

ida-multi-mcp --list

to see available instances, then use a valid ID.

"Instance 'k7m2' expired. Replaced by 'px3a'"

You opened a different binary in that IDA instance. This is expected. Use the new instance ID (px3a).

Plugin doesn't load in IDA / "No module named 'ida_multi_mcp'"

This usually means IDA's Python cannot find the package due to a Python version mismatch.

  1. Check IDA's Python version — in the IDA console, run:

    import sys; print(sys.version)

  2. Install the package for that specific Python version:

    macOS:

    # Replace 3.11 with IDA's actual Python version
python3.11 -m pip install --user git+https://github.com/MeroZemory/ida-multi-mcp.git

    Windows:

    # Replace 3.12 with IDA's actual Python version
py -3.12 -m pip install git+https://github.com/MeroZemory/ida-multi-mcp.git

  3. Ensure the IDA plugins directory contains ida_multi_mcp.py:

    • macOS/Linux: ~/.idapro/plugins/
    • Windows: %APPDATA%\Hex-Rays\IDA Pro\plugins\

  4. Restart IDA Pro

MCP server fails to connect (macOS)

If your MCP client shows Status: failed for ida-multi-mcp, the registered command may point to the wrong Python version.

  1. Check what command is configured (e.g., in .claude.json, .cursor/mcp.json)

  2. If it shows python3 -m ida_multi_mcp, replace it with the pipx-managed CLI:

    Claude Code:

    claude mcp remove ida-multi-mcp -s user
claude mcp add ida-multi-mcp -s user -- ida-multi-mcp

    Other clients: Edit the MCP config JSON and change:

    {
  "command": "ida-multi-mcp",
  "args": []
}

  3. Restart the MCP client

Design Decisions

| Decision | Rationale | |----------|-----------| | Port 0 (auto-assigned) | Eliminates port conflicts, scales to unlimited instances | | 4-char base36 IDs | Short, readable, 1.68M combinations, easy to remember | | File-based registry | Simple, cross-process, debuggable, no database dependency | | Dynamic tool discovery | Future-proof, automatic updates, no hardcoded tool list | | Dual binary-change detection | Robust fallback if IDA hooks fail |

Performance

  • Registry operations: <1ms (JSON file, file-locked)
  • Tool discovery: ~50ms per IDA instance (one-time cache)
  • Tool call routing: <5ms (local HTTP JSON-RPC)
  • Heartbeat interval: 60 seconds (negligible overhead)

Limitations

  • Supports 127.0.0.1 only (localhost analysis)
  • Remote IDA instances not supported in v1.0
  • Does not support IDA batch/headless (idalib) mode yet
  • Resources (not tools) require manual routing in v1.0

License

MIT

Contributing

Contributions welcome! Please ensure:

  • Python 3.11+ compatibility
  • Cross-platform (Windows, macOS, Linux)
  • Clean, readable code
  • Tests for new features

Acknowledgments

This project was inspired by and builds upon ida-pro-mcp by Duncan Ogilvie (mrexodia). The IDA tool implementations (71+ tools) originated from ida-pro-mcp and have been absorbed into ida-multi-mcp as a bundled package, adding multi-instance orchestration on top.

The installation approach (AI-agent-friendly installation guides) was influenced by oh-my-opencode by Yeongyu Yun (code-yeongyu).

Related Projects

  • ida-pro-mcp — The original single-instance IDA MCP plugin (tools originated from here) (MIT License)
  • Claude Code — MCP client with native support
  • Cursor — Alternative MCP-enabled editor

Support

For issues, feature requests, or questions:

  • Check the troubleshooting section above
  • Review DESIGN.md for architecture details
  • Open an issue on GitHub
Quick Setup
Installation guide for this server

Install Package (if required)

uvx ida-multi-mcp

Cursor configuration (mcp.json)

{ "mcpServers": { "merozemory-ida-multi-mcp": { "command": "uvx", "args": [ "ida-multi-mcp" ] } } }