Binary Ninja Cline MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_binary_infoC | Get binary metadata |
| list_functionsC | List functions in a binary |
| disassemble_functionC | Disassemble a function from a binary |
| decompile_functionC | Decompile a function to C |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: decompile_function produces C code, disassemble_function outputs assembly, get_binary_info retrieves metadata, and list_functions enumerates functions. There is no overlap in functionality, making tool selection unambiguous.
All tools follow a consistent verb_noun pattern with snake_case (e.g., decompile_function, disassemble_function). The naming is predictable and readable throughout the set.
With 4 tools, the count is reasonable for a binary analysis server, covering core operations like listing, disassembling, decompiling, and metadata retrieval. It might benefit from additional tools (e.g., for editing or searching), but it's well-scoped for basic tasks.
The tools cover fundamental read-only operations for binary analysis (list, disassemble, decompile, info), but there are notable gaps such as no tools for modifying binaries, searching for patterns, or handling symbols. This limits advanced workflows but supports basic inspection.