What is the feature you'd like to have?
I'd like to see support for a HTTP-based MCP transport for the headless MCP client. It should allow for multiple clients to connect and share binary views and analysis state.
Is your feature request related to a problem?
Yes, the current headless MCP only communicates over STDIO, which effectively ties one agent to one instance of Binary Ninja. As a result, my current workflow that batches read-only initial analysis cannot share analysis state without incurring overhead. Each sub-agent has to spin up its own instance of Binary Ninja which is a waste of my system resources.
Are any alternative solutions acceptable?
Some sort of multiplexer over STDIO connections.
Additional Information:
I am able to use the HTTP MCP over the GUI in the interim, but I don't want UI overhead when I don't need it.
What is the feature you'd like to have?
I'd like to see support for a HTTP-based MCP transport for the headless MCP client. It should allow for multiple clients to connect and share binary views and analysis state.
Is your feature request related to a problem?
Yes, the current headless MCP only communicates over STDIO, which effectively ties one agent to one instance of Binary Ninja. As a result, my current workflow that batches read-only initial analysis cannot share analysis state without incurring overhead. Each sub-agent has to spin up its own instance of Binary Ninja which is a waste of my system resources.
Are any alternative solutions acceptable?
Some sort of multiplexer over STDIO connections.
Additional Information:
I am able to use the HTTP MCP over the GUI in the interim, but I don't want UI overhead when I don't need it.