WineDbg MCP Server
Supports debugging of Windows applications compiled with MinGW-w64 cross-compiler, allowing testing and debugging of 32-bit Windows executables on non-Windows platforms.
Provides a server that wraps the Wine Debugger (winedbg) to debug Windows applications running under Wine from a remote client. Offers a comprehensive set of debugging tools including breakpoints, watchpoints, memory examination, stack navigation, and process control.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@WineDbg MCP Serverset a breakpoint at main in test_app.exe"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
WineDbg MCP Server
This project provides a server that wraps the Wine Debugger (winedbg) and exposes its functionality through a simple API. This allows you to debug Windows applications running under Wine from a remote client.
Installation
Install Wine and
winedbg.Create a Python virtual environment and install the required dependencies:
python -m venv .venv source .venv/bin/activate pip install -r requirements.txt
Related MCP server: MCP Server GDB
Usage
Start the server:
python -m src.mcp_serverRun the test client to see the server in action:
python tests/test_client.py
Testing with the Test App
This project includes a simple C application that can be used for testing the server.
Compile the test application for 32-bit Windows:
i686-w64-mingw32-gcc -o tests/test_app.exe tests/test_app.cIf you don't have the MinGW-w64 cross-compiler, you can install it on Debian/Ubuntu with:
sudo apt-get install gcc-mingw-w64-i686Run the test client:
python tests/test_client.pyThe test client will automatically use the
test_app.exeto test the server's functionality.
MCP Server Configuration
If you are using a client that supports launching MCP servers, you can configure it with the following JSON. This tells the client how to start the winedbg server.
Note: Make sure to replace /ABSOLUTE/PATH/TO/PARENT/FOLDER/mcp-winedbg with the actual absolute path to this project directory on your system.
{
"mcpServers": {
"winedbg": {
"command": "/ABSOLUTE/PATH/TO/PARENT/FOLDER/mcp-winedbg/.venv/bin/python",
"args": [
"/ABSOLUTE/PATH/TO/PARENT/FOLDER/mcp-winedbg/src/mcp_server.py"
]
}
}
}Available Tools
The server exposes the following tools:
run: Run an executable inwinedbg.attach: Attach to a process.quit: Quitwinedbg.detach: Detach from the process.kill: Kill the process.cont: Continue execution.break_at: Set a breakpoint.watch: Set a watchpoint.info_break: Get breakpoint info.delete_breakpoint: Delete a breakpoint.backtrace: Get a backtrace.frame: Select a stack frame.up: Move up the stack.down: Move down the stack.step: Step execution.next: Next execution.stepi: Step instruction.nexti: Next instruction.finish: Finish execution of the current function.print_var: Print a variable.examine_memory: Examine memory.info_locals: Get local variables.info_args: Get function arguments.info_proc: Get process info.info_threads: Get thread info.info_share: Get shared library info.set_debug_channel: Set theWINEDEBUGenvironment variable.get_debug_channels: Get theWINEDEBUGenvironment variable.
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/maci0/mcp-winedbg'
If you have feedback or need assistance with the MCP directory API, please join our Discord server