ida-multi-mcp

ida-multi-mcp is an MCP server/router that enables using multiple concurrently running IDA Pro instances through a single MCP endpoint. It auto-registers instances, assigns short instance_id values, routes tool calls to the correct IDA instance via local HTTP JSON-RPC, and handles instance expiration when binaries change.

Evaluated Mar 30, 2026 (21d ago)

Repo ↗ DevTools mcp ida-pro reverse-engineering router local-automation python

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

No auth is described; this is intended for localhost use. Transport details (HTTP vs stdio) and TLS are not documented; internal routing appears to use local HTTP JSON-RPC. The package is Python and includes vendor/tool schemas; dependency security status/CVEs are not verifiable from the provided content.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You have multiple local IDA Pro GUI instances running with different binaries and want one MCP connection for automated multi-instance analysis.

Avoid When

You need a secure multi-user service, remote access, or strong network-level controls; or you rely on headless IDA batch processing.

Use Cases

• Parallel reverse engineering with multiple IDA Pro instances
• LLM-assisted decompilation/decompilation comparisons across different binaries
• Managing and routing many IDA tool invocations without per-instance MCP configuration
• Handling binary reloads by using instance_id expiration/replacement guidance

Not For

• Remote/re-hosted IDA instances over the network (only localhost/127.0.0.1 is supported per README)
• Headless/batch IDA (idalib) workflows (not supported yet)
• Environments requiring authentication, authorization, or tenant isolation between users

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

OAuth: No Scopes: No

No authentication/authorization mechanism is described. The design is primarily local (127.0.0.1) and intended for single-user local use.

Pricing

Free tier: No

Requires CC: No

Open-source MIT license; no pricing model described.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ All IDA tool calls require instance_id; omitting it can cause routing/contension issues.
⚠ Instance IDs expire when the binary is changed in an IDA instance; agents must refresh/handle replacement IDs.
⚠ Python version mismatch on macOS/Windows can prevent plugin loading or MCP connection; ensure installation into IDA's Python.
⚠ Remote/multi-host use is not supported (localhost only per README), so agents running elsewhere will fail.

Alternatives

ida-pro-mcp (single-instance style) and run separate MCP servers per IDA instance Writing/using your own MCP wrapper around an IDA Pro JSON-RPC/HTTP interface (if available) with explicit routing Single-instance workflows using one IDA instance at a time

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for ida-multi-mcp.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-30.