We recently discovered that shipping binaryninja_mcp.exe might brick the installation during update. This is because if binaryninja_mcp.exe is running during the installation, it cannot be overwritten, and the installer would bail out (for good), and it will leave behind a half-updated binja installation
Until this is fixed, we cannot ship the headless MCP server on Windows. A workaround is to use the HTTP MCP server for now
We recently discovered that shipping binaryninja_mcp.exe might brick the installation during update. This is because if binaryninja_mcp.exe is running during the installation, it cannot be overwritten, and the installer would bail out (for good), and it will leave behind a half-updated binja installation
Until this is fixed, we cannot ship the headless MCP server on Windows. A workaround is to use the HTTP MCP server for now