What dependencies does BinjaLattice require?
Binary Ninja (with Python API) and Python 3. The plugin creates a dedicated virtual environment and installs dependencies from `requirements.txt`.
@Invoke-RE
Basic information
Plugin interface for remote communications with Binary Ninja database and MCP server for interfacing with LLMs.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"binja-lattice-mcp": {
"command": "python",
"args": [
"-m",
"venv",
".venv"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
BinjaLattice is a secure communication protocol for Binary Ninja that enables interaction with external Model Context Protocol (MCP) servers and tools. It provides a structured way to acquire information from Binary Ninja and modify an active Binary Ninja database over HTTP using a REST API.
Install by copying the plugin files (lattice_server_plugin.py and lattice_config.ini) to Binary Ninja’s plugins directory, generating a secure API key, creating a Python virtual environment, and installing dependencies. In Binary Ninja, go to Plugins > Start Lattice Protocol Server; the server prints the API key which you set as the BNJLAT environment variable in your MCP configuration. You can then use the bundled MCP server (mcp_server.py) or the Lattice client library / lattice_client.py CLI.
Binary Ninja (with Python API) and Python 3. The plugin creates a dedicated virtual environment and installs dependencies from `requirements.txt`.
The server generates a random API key on startup and displays it in the Binary Ninja log. All requests require this key (or a short-lived token obtained after authentication). Tokens expire after 8 hours by default.
The server runs locally on port 9000 by default. Optional SSL/TLS encryption can be enabled by providing a certificate and key. The protocol uses HTTP and is intended for local or trusted networks.
Tools for binary information (`get_binary_info`), function analysis (`get_function_disassembly`, `get_function_pseudocode`, `get_call_graph`), data access (`get_data_at_address`, `search_bytes`), type management (`create_struct`, `update_struct`), and annotations (`update_function_name`, `add_comment_to_address`, `create_tag`).
All data resides within the active Binary Ninja database. BinjaLattice reads and writes to that database; no external storage is used.

See and control a real Windows PC you own — from any MCP client, locally or remotely. Observe (UIA + screenshots), click/type/drag/scroll, launch apps, owner Live View. BYOH: your machine, your key.
YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context
AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

Yuppsy MCP: build and publish real estate websites from your AI assistant. Yuppsy lets your AI assistant create live websites for real estate agents and individual property listings. You don't need a designer or any code

Model Context Protocol Servers
Comments