Home / MCP / Binary Ninja Cline MCP Server

Binary Ninja Cline MCP Server

MCP server that enables Binary Ninja analysis via Cline by exposing a local HTTP API and a bridge.

other

4stars

View on GitHub

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
    "mcpServers": {
        "bn_mcp_http": {
            "url": "http://localhost:8088"
        }
    }
}

This MCP server enables Binary Ninja to analyze binaries through Cline by exposing a local HTTP API and a bridge that connects Cline to Binary Ninja. It lets you run a Binary Ninja MCP HTTP server and a Node.js bridge locally, so Cline can access Binary Ninja analysis results during your workflow.

How to use

To use this MCP server with Cline, start the local Binary Ninja MCP HTTP server first, then launch the bridge that connects Cline to Binary Ninja. Finally, configure Cline to load the MCP tool and point it at the bridge.

How to install

Prerequisites you need before installation:

Node.js and npm installed
Python installed (for the HTTP server)
Binary Ninja with the MCP Plugin installed

Step by step commands:

# 1) Start the Binary Ninja MCP HTTP server (in its own environment or terminal)
# The exact command to start the HTTP server is shown in the setup steps you perform inside Binary Ninja:
# python binary_ninja_mcp_http_server.py --port 8088
```
```
# 2) Start the bridge that connects Cline to Binary Ninja
# This is typically started via the Node.js bridge script with an environment variable pointing to the HTTP server
```
```
# 3) Start the MCP bridge service that Cline will communicate with
npm start
```
```
# 4) Configure your MCP client in Cline to use the bridge as shown in the example configuration
```
```
# Example MCP client configuration (as shown in the source):
{
  "mcpServers": {
    "BN MCP": {
      "command": "node",
      "args": ["/home/matteius/binary_ninja_cline/bn_cline_mcp/binaryninja-mcp-bridge.js"],
      "env": {
        "BN_HTTP_SERVER": "http://localhost:8088"
      },
      "autoApprove": [],
      "disabled": false,
      "timeout": 30
    }
  }
}

Additional content

Notes and guidance you should follow for smooth operation:
- The HTTP MCP server listens on port 8088 by default. Start the Python server with the port flag as shown in the steps above.
- The bridge script expects BN_HTTP_SERVER to point to the running HTTP server URL.
- When you start npm, it serves the bridge that your MCP client will connect to. Ensure that the bridge process remains running while you use the MCP features in Cline.
- If you encounter connection issues, verify that the HTTP server is reachable at http://localhost:8088 from the same environment where you run the bridge and the MCP client.
- Keep your Binary Ninja MCP Plugin up to date to ensure compatibility with the bridge and with Cline.

Available tools

binary_ninja_http_server

HTTP MCP server that exposes Binary Ninja analysis results to MCP clients via port 8088.

binaryninja_mcp_bridge

Bridge that connects Cline to the Binary Ninja MCP HTTP server using the BN_HTTP_SERVER environment variable.

cline_integration_tool

Cline integration support enabling analysis through the Binary Ninja MCP server and bridge.