Ship headless MCP server on Windows

Open
#8,442 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
cpp
Domain
operating-systems, release

Research direction

The payload names no files or tests. Start by reproducing a Windows update while binaryninja_mcp.exe is running and trace the installer path; done means the update no longer bricks or leaves a half-updated installation, allowing the headless MCP server to ship safely.

Written by the indexing model from the issue text.

Description

We recently discovered that shipping binaryninja_mcp.exe might brick the installation during update. This is because if binaryninja_mcp.exe is running during the installation, it cannot be overwritten, and the installer would bail out (for good), and it will leave behind a half-updated binja installation

Until this is fixed, we cannot ship the headless MCP server on Windows. A workaround is to use the HTTP MCP server for now

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

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.

More from Vector35/binaryninja-api

All issues in Vector35/binaryninja-api

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.