mcp -idapro

This MCP server bridges AI assistants with IDA Pro, enabling control and data extraction from binaries through a standardized MCP interface. The server exposes a set of tools that let you run IDA Pro Python scripts, search for strings, imports, exports, and functions, and retrieve disassembly or binary metadata. Typical usage involves installing and running the IDA Pro Remote Control Plugin inside IDA Pro (which starts a local HTTP API), then running the MCP server to expose those capabilities to your AI assistant. Tools available include run_ida_command to execute Python scripts in IDA Pro, search_immediate_value to locate immediate operands, search_text to find strings, search_byte_sequence to locate specific byte patterns, get_disassembly to fetch disassembly for a range, and get_functions/get_exports/get_strings to retrieve binary metadata. The IDA Pro Remote Control API endpoints are exposed over localhost, secured by default, and the MCP layer delegates tool calls to the IDA Pro plugin to perform the actual work.

Prerequisites:

• IDA Pro 8.3 or later
• Node.js 18 or later
• npm (comes with Node.js)

Installation steps:

1. Install and run the IDA Pro Remote Control Plugin inside IDA Pro (refer to the IDA Pro MCP README). The plugin starts an HTTP server on 127.0.0.1:9045.

2. Install this MCP server package:

# Clone the repository (or initialize as a package if you have a copy locally)
git clone <repository-url>
cd ida-server

# Install dependencies
npm install

3. Build the MCP server (TypeScript project):

npm run build

4. Configure the MCP in your AI assistant’s MCP settings file to point to this server (example shown):

{
  "mcpServers": {
    "fdrechsler-mcp-server-idapro": {
      "command": "node",
      "args": ["path/to/ida-server/dist/index.js"],
      "env": {}
    }
  }
}

5. Start the MCP server (depending on your environment, e.g., via a process manager) and ensure the IDA Pro plugin is running and accessible at 127.0.0.1:9045.

Notes and tips:

• By default, the IDA Pro Remote Control Plugin only listens on localhost for security. If you need remote access, adjust the DEFAULT_HOST in ida_remote_server.py, but be aware of security risks.
• Ensure the MCP server’s node process has access to the IDA Pro instance via the local HTTP API (127.0.0.1:9045).
• When configuring tools, you’ll typically pass JSON-encoded arguments to run_ida_command and other tools. Validate shapes against the tool definitions (e.g., scriptPath for run_ida_command, text for search_text, etc.).
• Build artifacts for production should be served from dist/index.js, as referenced in the configuration.
• If you encounter port or binding issues, confirm firewall rules or local proxy settings aren’t blocking 127.0.0.1 communications between the MCP server and the IDA Pro plugin.