Vector35 / Vector35/binaryninja-api

MCP CLI can't see open files

Open
#8,472 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component: MCP Impact: Medium
Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Description

Version and Platform:

  • Binary Ninja Version: 6.1.10533-dev
  • Edition: Ultimate
  • OS: OSX
  • OS Version: 26.5.2
  • CPU Architecture: M3

Bug Description:
When I ask an LLM to use binaryninja_cli, they report as not being able to see open files. When you start the MCP from the Plugins menu, they can. The split here is confusing, and sometimes it causes the agents to reopen files and confuse analysis states.

Screenshots/Video Recording:
If applicable, please add screenshots/video recording here to help explain your problem.

Image

...

Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Compare the MCP started through binaryninja_cli with the MCP started from the Plugins menu, focusing on how each launch path discovers open files. Reproduce the issue on the reported macOS setup and consider the bug fixed when both launch paths expose the same open files without reopening them.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli, reverse-engineering, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.