- Home
- MCP servers
- WineDbg
WineDbg
- python
0
GitHub Stars
python
Language
7 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"maci0-mcp-winedbg": {
"command": "/ABSOLUTE/PATH/TO/PARENT/FOLDER/mcp-winedbg/.venv/bin/python",
"args": [
"/ABSOLUTE/PATH/TO/PARENT/FOLDER/mcp-winedbg/src/mcp_server.py"
]
}
}
}This MCP server wraps the Wine Debugger (winedbg) and exposes its functionality through a simple API, enabling you to debug Windows applications running under Wine from a remote client. It provides convenient programmatic access to common debugger actions and state information, making remote debugging workflows practical and repeatable.
How to use
You interact with the server through an MCP client to control Wine’s debugger. Start the local server, then issue commands to run programs under Wine, set breakpoints, inspect memory and variables, and step through code. The client will translate your actions into debugger calls and return results you can display or log.
How to install
Prerequisites you need before installing the MCP server include a Python interpreter and the dependencies that the project requires.
python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
Additional sections
Configuration, startup, and testing are described below to help you get running quickly and securely.
Starting the MCP server locally allows you to exercise its functionality with a test client. Use a dedicated virtual environment to isolate dependencies and avoid conflicts with other Python projects.
Available tools
run
Launches an executable under the Wine Debugger to start a debug session.
attach
Attaches the debugger to an already running process within Wine.
quit
Terminates the Wine Debugger session and exits.
detach
Detaches from the current process while keeping the debugging session alive.
kill
Forcibly terminates the target process.
cont
Continues execution after a breakpoint or pause.
break_at
Sets a breakpoint at a specified location in the program being debugged.
watch
Sets a watchpoint on a memory location or variable.
info_break
Retrieves information about current breakpoints.
delete_breakpoint
Deletes a specified breakpoint.
backtrace
Provides a backtrace of the current thread.
frame
Selects a specific stack frame for inspection.
up
Moves up the call stack to higher frames.
down
Moves down the call stack to lower frames.
step
Steps over the next line of code.
next
Executes until the next line, skipping function calls.
stepi
Steps a single machine instruction.
nexti
Executes the next instruction without entering function calls.
finish
Continues execution until the current function returns.
print_var
Prints the value of a variable in the current scope.
examine_memory
Inspects a region of memory.
info_locals
Gets local variables in the current frame.
info_args
Gets function arguments for the current frame.
info_proc
Provides information about the process being debugged.
info_threads
Retrieves information about running threads.
info_share
Gets information about shared libraries loaded in the process.
set_debug_channel
Sets the WINEDEBUG environment channel for filtering output.
get_debug_channels
Retrieves the configured WINEDEBUG channels.