이것은 자동화된 AI .NET 리버스 엔지니어링을 위한 dnSpy MCPServer 확장입니다 \dnSpy\Extensions\Examples\AgentSmithers dnSpy MCPServer.Extension은 MCPServer 로직을 포함하도록 업데이트되었으며, 디컴파일된 코드를 LLM에 다시 전달하는 몇 가지 시작 함수가 추가되었습니다. 이 프로젝트는 진행 중이며, 시간이 지남에 따라 계속 명령어를 추가할 계획입니다.

서버를 실행하려면 관리자 자격으로 실행하여 Http 서버가 +:3001(현재 릴리스 3003으로 설정됨)과 *:50301에서 스트리밍 가능한 MCP 서버에서 Listen 할 수 있도록 하세요.

다음 명령어로 충분합니다:

권장 디버그 워크플로우:

1단계:
dnSpy가 시작 프로젝트로 설정되어 있는지 확인하세요

2단계: 발사 설정 여김 솔루션 탐색기에서 프로젝트를 우클릭하세요 부동산 선택 왼쪽 사이드바에서 디버그(또는 디버깅)를 클릭하세요 그다음 “디버그 실행 프로필 UI” 로 가세요.

3단계: 명령줄 인자 추가 명령줄 인자 텍스트 박스에서 다음을 입력하세요: –extension-directory “$(SolutionDir)Extensions\Examples\Example1.Extension\bin\Debug\net48”

4단계: 저장 저장을 클릭하거나 Ctrl+S 키를 누르세요 속성 창을 닫습니다

5단계: 테스트 F5를 누르거나 초록색 재생 버튼을 클릭하세요 이제 dnSpy가 확장 프로그램이 실행된 상태로 실행될 것입니다!

AgentSmithers dnSpyEx MCPServer Extension

This is a dnSpy MCPServer Extension for the use of automated AI .NET reverse engineering The \dnSpy\Extensions\Examples\AgentSmithers dnSpy MCPServer.Extension has been updated to include the MCPServer logic with a few starting function to feed the decompiled code back to the LLM. This is an ongoing project and I plan to continue to add commands as time persist.

To execute the server, run as Administrator so the the Http server may Listen on +:3001 (release is currently set to 3003) and *:50301 for the streamable MCP Server.

The following command will suffice:

Recommended debug workflow:

Step 1: Ensure dnSpy is set as Startup Project

Step 2: Open Launch Settings In Solution Explorer, right-click on your project Select Properties In the left sidebar, click on Debug (or Debugging) Then go to “Open debug launch profiles UI”

Step 3: Add Command Line Arguments In the Command line arguments text box, enter: –extension-directory “$(SolutionDir)Extensions\Examples\Example1.Extension\bin\Debug\net48”

Step 4: Save Click Save or press Ctrl+S Close the properties window

Step 5: Test Press F5 or click the green play button Your dnSpy should now launch with your extension loaded!

OR

cd {dnspy directory}

dnspy.exe --extension-directory {Path to extension} Example 1: dnspy.exe --extension-directory “C:\repos\dnSpy\Extensions\Examples\Example1.Extension\bin\Debug\net48”

Example 2 in CMD: C:\Users\user>“C:\Users\user\source\repos\DnSpy-MCPserver-Extension\dnSpy\dnSpy\bin\Debug\net48\dnspy.exe” --extension-directory “C:\Users\user\source\repos\DnSpy-MCPserver-Extension\dnSpy\dnSpy\bin\Debug\net48\Extensions”

OR

In alternative you may copy the release into the Extension folder within the dnSpy\Extensions\AgentSmithersMCPServer path.

Modifying the project

Ensure to compile the primary DnSpy Soultion (Clean and rebuild) so that the dependancies for “AgentSmithers DnSpyEx MCPServer” can use them for its own build. (Note: When compiling DnSpyEx you may have approx. ~20 errors, this will not prevent the 45 Projects from compiling)

Once dnSpy is fully cleaned and compiled, navigate to the Example1 Extension Project. In there is the modified code. Make your adjustments, compile then use the --extension-directory argument when executing DnSpy.exe to point to your projects extension path.

In alternative you may pull down the latest dnSpyEx then rename the Extension sample folder to another name and bring the modified extension folder over to recompile.

Compiling

Clean and rebuild (I used visual Studio 2026, I think you’ll need .NET Framework 4.8 and Core 10 Installed to compile the full solution)