IDA Pro MCP Server

Created By
fdrechslera year ago
A Model Context Protocol (MCP) server that enables AI assistants to interact with IDA Pro for reverse engineering and binary analysis tasks.
Overview

What is IDA Pro MCP Server?

IDA Pro MCP Server is a Model Context Protocol (MCP) server that allows AI assistants to interact with IDA Pro, a popular tool for reverse engineering and binary analysis.

How to use IDA Pro MCP Server?

To use the IDA Pro MCP Server, install the IDA Pro Remote Control Plugin and the MCP Server, then configure your AI assistant to communicate with the MCP server.

Key features of IDA Pro MCP Server?

  • Execute Python scripts in IDA Pro from AI assistants.
  • Retrieve binary information such as strings, imports, exports, and functions.
  • Automate IDA Pro operations through a standardized interface.
  • Secure communication between components.

Use cases of IDA Pro MCP Server?

  1. Automating reverse engineering tasks using AI.
  2. Analyzing binary files for vulnerabilities.
  3. Integrating AI capabilities into existing IDA Pro workflows.

FAQ from IDA Pro MCP Server?

  • Can I use IDA Pro MCP Server with any version of IDA Pro?

No, it requires IDA Pro 8.3 or later.

  • Is there a cost associated with using IDA Pro MCP Server?

No, it is open-source and free to use under the MIT License.

  • How secure is the communication with IDA Pro MCP Server?

By default, it listens only on localhost for security, but remote access can be configured with caution.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fdrechsler
Star
6
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago