Ida MCP Server Plugin

🚀 IDA Pro MCP Server Plugin

The IDA Pro MCP Server Plugin is a tool that allows remote querying and control of IDA Pro through the Model Context Protocol (MCP) interface. This plugin enables AI assistants (e.g., Claude) to directly perform binary analysis tasks with IDA Pro.

🚀 Quick Start

1. Open a binary file in IDA Pro.
2. The plugin will automatically load and start the local MCP server (port 3000).
3. Connect your AI assistant (e.g., Claude) to this server.
4. Use the AI assistant to perform binary analysis tasks.

✨ Features

The server provides a series of tools that allow AI assistants to perform the following operations:

• Retrieve byte data at a specified address.
• Obtain assembly code.
• Get decompiled pseudo - code.
• Query function names.
• Retrieve segment information.
• List all functions.
• Find cross - references.
• Get import/export tables.
• Obtain the entry point.
• Define/undefine functions.
• Retrieve various data types (dword, word, byte, qword, float, double, string).
• Get all strings in the binary file.
• Obtain the length of the instruction at a specified address.

📦 Installation

⚠️ Important Note

This plugin is designed and tested for IDA Pro version 9.0+.

1. Ensure Python and related dependencies are installed:

pip install -r requirements.txt

2. Copy the ida - mcp - server.py file to the IDA Pro plugin directory:
   • Windows: %Programfiles%\IDA Pro 9.0\plugins\
   • Linux: ~/.idapro/plugins/
   • macOS: ~/Library/Application Support/IDA Pro/plugins/

💻 Usage Examples

Basic Usage

In Claude or the mcp.json file of VSCode, add the following configuration:

{
  "mcpServers": {
    "IDAPro": {
      "url": "http://127.0.0.1:3000/sse",
      "type": "sse"
    }
  }
}

Available Analysis Tools

The IDA Pro MCP server provides the following tools:

• get_bytes: Retrieve byte data at a specified address.
• get_disasm: Obtain assembly code at a specified address.
• get_decompiled_func: Get the pseudo - code of the function containing the specified address.
• get_function_name: Retrieve the function name at a specified address.
• get_segments: Obtain all segment information.
• get_functions: Get all functions in the binary file.
• get_xrefs_to: Find all cross - references to a specified address.
• get_imports: Retrieve all imported functions.
• get_exports: Obtain all exported functions.
• get_entry_point: Get the entry point of the binary file.
• make_function: Create a function at a specified address.
• undefine_function: Undefine the function at a specified address.
• get_dword_at: Retrieve the double - word (dword) at a specified address.
• get_word_at: Obtain the word at a specified address.
• get_byte_at: Retrieve the byte at a specified address.
• get_qword_at: Obtain the quad - word (qword) at a specified address.
• get_float_at: Retrieve the floating - point number (float) at a specified address.
• get_double_at: Obtain the double - precision floating - point number (double) at a specified address.
• get_string_at: Retrieve the string at a specified address.
• get_string_list: Get all strings in the binary file.
• get_strings: Get all strings (with addresses) in the binary file.

📚 Documentation

Best Practices

When analyzing binary files, it is recommended to follow these steps:

1. Check the entry point.
2. Analyze the import table.
3. Review strings.
4. Track key API calls.
5. Identify main functional blocks.
6. Analyze the control flow.
7. Identify malicious behavior.
8. Analyze algorithms and encryption routines.
9. Document the analysis results.
10. Use advanced techniques.

📄 License

MIT License

Copyright (c) 2023

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

1. All copyright notices and permission notices shall be retained in all copies or substantial portions of the Software.
2. The Software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and non - infringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the Software or the use or other dealings in the Software.