IDA Pro MCP Server

IDA Pro Plugin for serving MCP SSE server for cursor / claude. Exposed over MCP by the ida pro mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

IDA Pro MCP Server is a plugin that allows remote querying and control of IDA Pro through the Model Context Protocol (MCP) interface. This plugin enables AI assistants (such as Claude) to interact directly with IDA Pro for binary analysis tasks.

This server provides a series of tools that allow AI assistants to perform the following operations: - Get byte data from specific addresses - Get disassembly code - Get decompiled pseudocode - Query function names - Get segment information - List all functions - Find cross-references - Get import/export tables - Get entry points - Define/undefine functions - Get various data types (dword, word, byte, qword, float, double, string) - Get all strings in the binary file - Get the length of the instruction at the specified address

Its toolset

Everything the assistant can do here goes through one of these:

• get_bytes — Get bytes at a specified address
• get_disasm — Get disassembly at a specified address
• get_decompiled_func — Get pseudocode of the function containing the specified address
• get_function_name — Get function name at a specified address
• get_segments — Get all segment information
• get_functions — Get all functions in the binary
• get_xrefs_to — Get all cross-references to a specified address
• get_imports — Get all imported functions
• get_exports — Get all exported functions
• get_entry_point — Get the entry point of the binary
• make_function — Create a function at a specified address
• undefine_function — Undefine a function at a specified address

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. IDA Pro's toolset — get_bytes, get_disasm, get_decompiled_func and 11 more — is a fair guide to whether it matches your workflow. It is maintained by taida957789; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch IDA Pro.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the ida pro mcp server does with a few real requests.