Another™ MCP Server for Binary Ninja
@MCPPhalanx
Another™ MCP Server for Binary Ninja with superpower 🥵
Overview
What is Another™ MCP Server for Binary Ninja?
Another™ MCP Server for Binary Ninja is a Model Context Protocol (MCP) server that exposes Binary Ninja’s reverse engineering tools and binary analysis data to MCP-compatible clients, such as Claude Desktop and Cherry Studio. It is designed for binary analysts and developers who want to interact with Binary Ninja through large language models.
How to use Another™ MCP Server for Binary Ninja?
Install as a Binary Ninja UI plugin via the plugin manager (auto-starts on first file load, configurable port). Or run in headless mode: uvx binaryninja-mcp install-api (once), then uvx binaryninja-mcp server <filename>.... Configure MCP clients with stdio relay (uvx binaryninja-mcp client) or SSE endpoint (http://localhost:7000/sse). Use --port to change the default port 7000.
Key features of Another™ MCP Server for Binary Ninja
- Exposes Binary Ninja analysis as MCP tools and resources
- Provides 15+ analysis tools (e.g., rename, pseudo‑C, disassembly)
- Supports both UI plugin and headless modes
- Connects to MCP clients via stdio or SSE transport
- Automatically exposes all opened binary files as URIs
- Configuration of auto‑start and port via Binary Ninja settings
Use cases of Another™ MCP Server for Binary Ninja
- Automate reverse engineering tasks with LLMs
- Query binary metadata (imports, exports, segments, strings)
- Decompile functions into pseudo‑C or pseudo‑Rust
- Analyze triage summaries and disassembly via chat interfaces
FAQ from Another™ MCP Server for Binary Ninja
How do I install this server?
You can install it via Binary Ninja’s plugin manager (UI plugin) or use uvx binaryninja-mcp install-api once, then uvx binaryninja-mcp server <filename> for headless mode.
Can I change the default port?
Yes. Use the --port flag on both the server and client command lines (default is 7000) or configure the port in Binary Ninja Settings under “MCP Server – Server port number”.
What is the difference between UI plugin and headless mode?
The UI plugin auto‑starts when the first file is loaded and offers configurable auto‑start and port in Binary Ninja’s settings. Headless mode requires explicit file arguments and runs without a graphical interface.
What transport protocols are supported?
Both SSE (recommended for Cherry Studio) and stdio relay (for Claude Desktop) are supported.
Does the server require Binary Ninja to be installed?
Yes. Binary Ninja must be installed because the server uses the Binary Ninja API. The headless mode also requires prior installation of the API (install-api command).