Top AI Repos — open-source AI, indexed and scored

Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.

SetsunaYukiOvO/x64dbg-mcp

MCP server plugin for x64dbg debugger - enables AI agents and external tools to control debugging via JSON-RPC 2.0 over HTTP/SSE

72MITC++

View on GitHub

Stars: 478
Forks: 61
Watchers: 2
Open issues: 3
Contributors: —

Star history, last 90 days+145 over 36 snapshots

2026-07-31 · 3332026-09-20 · 478

Star history, last 90 days
Date	Stars
2026-07-31	333
2026-08-02	337
2026-08-12	371
2026-08-18	393
2026-08-19	396
2026-08-20	399
2026-08-21	401
2026-08-22	405
2026-08-23	409
2026-08-24	414
2026-08-25	419
2026-08-26	424
2026-08-27	429
2026-08-28	431
2026-08-29	432
2026-08-30	435
2026-08-31	438
2026-09-01	446
2026-09-02	447
2026-09-03	451
2026-09-04	455
2026-09-05	454
2026-09-06	455
2026-09-07	455
2026-09-08	456
2026-09-09	457
2026-09-10	459
2026-09-11	462
2026-09-12	463
2026-09-13	464
2026-09-14	465
2026-09-15	469
2026-09-16	471
2026-09-17	474
2026-09-18	475
2026-09-20	478

Today

+3 stars today

This week

+14 stars this week

This month

+77 stars this month

Momentum

26.0

growth rate 3.02%/day

From the README

x64dbg MCP Server Plugin

English | 中文

A Model Context Protocol (MCP) server implementation for x64dbg and x32dbg, enabling remote debugging through a JSON-RPC 2.0 interface. This plugin allows external applications and AI agents to interact with the debugger programmatically.

Now supports both x64 and x86 architectures!

Features

Full MCP Specification Compliance: Implements all three core MCP building blocks
- Tools (79): AI-invokable debugging functions
- Resources (7 + 8 templates): Application-controlled context data sources
- Prompts (10): User-guided debugging workflow templates
JSON-RPC 2.0 Protocol: Standard, language-agnostic interface
Streamable HTTP transport (MCP 2025-03-26) on /mcp, plus legacy HTTP+SSE on /sse for older clients
Tools - AI-Controlled Debugging (79 functions):
- Execution control (init/run/pause/step/run_to/restart/stop)
- Memory read/write/search/allocate
- Register access (50+ registers including GPR, SSE, AVX)
- Breakpoint management (software, hardware, memory, conditional, logging)
- Disassembly and symbol resolution
- Thread management (list, switch, suspend, resume)
- Stack trace and analysis
- Dump & Analysis (module dump, memory dump, packer detection, OEP detection)
- Script execution (execute x64dbg/x32dbg commands, batch operations)
- Context snapshots (capture and compare debugging state)
Resources - Context Providers (7 direct + 8 templates):
- Direct resources: debugger state, registers, modules, threads, memory map, breakpoints, stack
- Resource templates: memory content, disassembly, module info, symbol resolution, function analysis
- Read-only, application-controlled access
Prompts - Workflow Templates (10 prompts):
- Crash analysis, vulnerability hunting, function tracing
- Binary unpacking, algorithm reversing, execution comparison
- String hunting, code patching, API monitoring
- Debug session initialization
Security: Permission-based access control
Extensible: Plugin architecture for custom methods, resources, and prompts

Prerequisites

Windows 10/11 (64-bit host; supports building both x64 and x86 plugins)
CMake 3.15 or higher
Visual Studio 2022 with C++ Desktop Development workload
vcpkg - Package manager for C++ libraries
Git - For cloning the repository

Quick Build

The easiest way to build is using the provided build script:

# Clone the repository
git clone https://github.com/SetsunaYukiOvO/x64dbg-mcp.git
cd x64dbg-mcp

# Build both x64 and x86 architectures (recommended)
.\build.bat

# Build only x64 architecture
.\build.bat --x64-only

# Build only x86 architecture
.\build.bat --x86-only

# Clean rebuild
.\build.bat --clean

# The script will:
# 1. Automatically detect vcpkg installation
# 2. Download dependencies (nlohmann_json)
# 3. Configure CMake for both architectures
# 4. Build using Visual Studio with parallel compilation
# 5. Copy output files to dist/ directory

Build script options:

.\build.bat               # Build both x64 and x86 (Release)
.\build.bat --clean       # Clean rebuild both architectures
.\build.bat --x64-only    # Build x64 only
.\build.bat --x86-only    # Build x86 only
.\build.bat --debug       # Debug build (future support)

Output files (in dist/ directory):

x64 plugin: dist\x64dbg_mcp.dp64 (~837 KB)
x86 plugin: dist\x32dbg_mcp.dp32 (~800 KB)

Manual Build Steps

If you prefer manual control:

Install vcpkg (if not already installed):

git clone https://github.com/Microsoft/vcpkg.git C:\vcpkg
C:\vcpkg\bootstrap-vcpkg.bat
setx VCPKG_ROOT "C:\vcpkg"

Clone the repository:

git clone https://github.com/SetsunaYukiOvO/x64dbg-mcp.git
cd x64dbg-mcp

Configure with CMake:

# For x64 build
cmake -B build_x64 -G "Visual Studio 17 2022" -A x64 ^
    -DCMAKE_TOOLCHAIN_FILE=C:/vcpkg/scripts/buildsystems/vcpkg.cmake ^
    -DVCPKG_TARGET_TRIPLET=x64-windows ^
    -DXDBG_ARCH=x64

# For x86 build
cmake -B build_x86 -G "Visual Studio 17 2022" -A Win32 ^
    -DCMAKE_TOOLCHAIN_FILE=C:/vcpkg/scripts/buildsystems/vcpkg.cmake ^
    -DVCPKG_TARGET_TRIPLET=x86-windows ^
    -DXDBG_ARCH=x86

Build:

cmake --build build_x64 --config Release
cmake --build build_x86 --config Release

Output:

x64 plugin: build_x64\bin\Release\x64dbg_mcp.dp64
x86 plugin: build_x86\bin\Release\x32dbg_mcp.dp32

Installation

Copy the compiled plugins to their respective debugger directories:

# For x64dbg (64-bit)
# Replace <x64dbg-path> with your actual x64dbg installation directory
copy dist\x64dbg_mcp.dp64 <x64dbg-path>\x64\plugins\

# For x32dbg (32-bit)
copy dist\x32dbg_mcp.dp32 <x64dbg-path>\x32\plugins\

# Example (if installed at C:\x64dbg):
# copy dist\x64dbg_mcp.dp64 C:\x64dbg\x64\plugins\
# copy dist\x32dbg_mcp.dp32 C:\x64dbg\x32\plugins\

(Optional) Copy the configuration file:

# For x64dbg
mkdir <x64dbg-path>\x64\plugins\x64dbg-mcp
copy config.json <x64dbg-path>\x64\plugins\x64dbg-mcp\

# For x32dbg
mkdir <x64dbg-path>\x32\plugins\x32dbg-mcp
copy config.json <x64dbg-path>\x32\plugins\x32dbg-mcp\

Restart x64dbg/x32dbg to load the plugin

Usage

Starting the Server

Open x64dbg for a 64-bit target or x32dbg for a 32-bit target
Navigate to Plugins → MCP Server → Start MCP HTTP Server
The server will start on the configured port (default: 3000)
Access the server at http://127.0.0.1:3000

Configuration

Edit config.json to customize settings:

{
  "version": "1.0.11",
  "server": {
    "address": "127.0.0.1",
    "port": 3000
  },
  "permissions": {
    "allow_memory_write": false,
    "allow_register_write": false,
    "allow_script_execution": false,
    "allow_breakpoint_modification": true,
    "allowed_methods": ["debug.*", "memory.*"]
  },
  "security": {
    "origin_allowlist": [],
    "host_allowlist": [],
    "auth_enabled": false,
    "auth_token": ""
  },
  "logging": {
    "enabled": true,
    "level": "info",
    "file": "x64dbg_mcp.log",
    "max_file_size_mb": 10,
    "console_output": true
  },
  "timeout": {
    "request_timeout_ms": 30000,
    "step_timeout_ms": 10000,
    "memory_read_timeout_ms": 5000
  },
  "features": {
    "enable_notifications": true,
    "enable_heartbeat": true,
    "heartbeat_interval_seconds": 30,
    "enable_batch_requests": true,
    "auto_start_mcp_on_plugin_load": false
  }
}

Configuration editor

Choose Plugins > MCP Server > Edit Config to edit the active configuration without manually changing JSON. The editor has pages for Server, Security, Permissions, Runtime, and Logging. It covers every runtime setting in the example above; the version field and any unknown future fields are preserved when saving.

For security allowlists, enter one Origin or Host per line. The Token field is masked and is required when Require Bearer token authentication is enabled. Saving a non-loopback listener without authentication requires confirmation. Restart the MCP HTTP server after saving for server settings to take effect.

Remote Access and Security

The server listens on 127.0.0.1 by default. This is intentional: the debugger exposes powerful operations. security.origin_allowlist and security.host_allowlist validate browser origins and Host headers; they are not passwords or API keys. Use security.auth_enabled and security.auth_token to enable HTTP Bearer authentication.

Local-only (recommended default)

Use 127.0.0.1:3000 and connect from the same Windows host. No firewall rule or port forwarding is required.

LAN or VM access

Only do this on a trusted network. Change the bind address and explicitly allow the address used by the client:

{
  "server": { "address": "0.0.0.0", "port": 3000 },
  "security": {
    "origin_allowlist": ["http://192.168.1.50:3000"],
    "host_allowlist": ["192.168.1.20", "debugger.example.test"]
  }
}

Use the actual client Origin, server hostname, or server IP. Do not add * as an Origin. Open TCP port 3000 only on the required Windows network profile, and configure the VM NAT/bridged adapter or router port forwarding separately. Restart the plugin after changing the file.

Endpoints:

Streamable HTTP clients: http://HOST:3000/mcp
Legacy HTTP+SSE clients: http://HOST:3000/sse
JSON-RPC compatibility endpoint: http://HOST:3000/rpc
Health check: GET http://HOST:3000/

Internet access

Do not publish the plugin directly to the Internet. Put it behind a VPN, SSH tunnel, or a reverse proxy that provides TLS, authentication, rate limiting, and IP allowlisting. Keep the plugin bound to 127.0.0.1 when the proxy runs on the same machine. A reverse proxy must preserve the MCP streaming response and forward Content-Type, Accept, Mcp-Protocol-Version, Mcp-Session-Id, and Last-Event-ID headers.

The plugin supports optional Authorization: Bearer validation but does not provide an OAuth authorization server. Never enable memory writes, register writes, or script execution on an unauthenticated public endpoint; these permissions are disabled by default and should remain disabled unless explicitly required.

To enable built-in Bearer authentication, store a high-entropy secret in the plugin configuration and restart the plugin:

{
  "security": {
    "auth_enabled": true,
    "auth_token": "replace-with-a-long-random-secret"
  }
}

All HTTP endpoints except CORS OPTIONS preflight then require Authorization: Bearer <auth_token>. The server refuses to start if authentication is enabled with an empty token, and logs a security warning when a non-loopback listener starts without authentication. Store the configuration with restrictive filesystem permissions and do not commit the token.

Common connection failures

Connection refused: verify the plugin server is started, the bind address/port, and VM NAT or firewall rules.
403 or rejected request: add the exact browser Origin to security.origin_allowlist and the proxy/client Hostname to security.host_allowlist.
MCP initialize succeeds but tools are missing: reconnect after initialize; clients discover capabilities from the response.
SSE hangs or returns 404: use /sse for legacy SSE clients and /mcp for Streamable HTTP clients.
Works through one proxy but not another: check that HTTP/1.1 streaming, long read timeouts, and SSE buffering are enabled.

For a first diagnostic, run curl http://127.0.0.1:3000/ on the debugger host, then test the same URL through each forwarding layer. Do not include debugger memory or credentials in issue logs.

Client Example

Python client example using HTTP:

import requests
import json

class MCPClient:
    def __init__(self, host='127.0.0.1', port=3000):
        self.base_url = f"http://{host}:{port}"
        self.request_id = 1
    
    def call(self, method, params=None):
        request = {
            "jsonrpc": "2.0",
            "id": self.request_id,
            "method": method,
            "params": params or {}
        }
        self.request_id += 1
        
        response = requests.post(
            f"{self.base_url}/rpc",
            json=request,
            headers={"Content-Type": "application/json"}
        )
        return response.json()
    
    def subscribe_events(self):
        """Subscribe to SSE events"""
        response = requests.get(
            f"{self.base_url}/sse",
            stream=True,
            headers={"Accept": "text/event-stream"}
        )
        for line in response.iter_lines():
            if line:
                yield line.decode('utf-8')

# Usage
client = MCPClient()
print(client.call("initialize"))
print(client.call("tools/list"))
print(client.call("resources/list"))
print(client.call("prompts/list"))

# Subscribe to debug events
for event in client.subscribe_events():
    print(f"Event: {event}")

Cursor and other MCP clients usually decide which sections to show from the initialize response capabilities. This server advertises tools, resources, and prompts, so after reconnecting you should see all three categories in the client UI.

VS Code Integration

Configure in VS Code settings or MCP client config. Recommended (Streamable HTTP, MCP 2025-03-26):

{
  "mcpServers": {
    "x64dbg": {
      "type": "http",
      "url": "http://127.0.0.1:3000/mcp"
    }
  }
}

Legacy HTTP+SSE clients (use the /sse path, not the root):

{
  "mcpServers": {
    "x64dbg": {
      "type": "sse",
      "url": "http://127.0.0.1:3000/sse"
    }
  }
}

Available Methods

System Methods

system.info - Get server information
system.ping - Test connection
system.methods - List all available methods

Debug Control

debug.run - Continue execution
debug.pause - Pause execution
debug.step_into - Step into instruction
debug.step_over - Step over instruction
debug.step_out - Step out of function
debug.get_state - Get current debug state
debug.run_to - Run to specific address
debug.restart - Restart debugging session
debug.stop - Stop debugging

Register Operations

register.get - Read single register
register.set - Write register value
register.list - List all registers
register.get_batch - Read multiple registers

Memory Operations

memory.read - Read memory region
memory.write - Write memory region
memory.search - Search memory pattern
memory.get_info - Get memory region info
memory.enumerate - List all memory regions
memory.allocate - Allocate memory
memory.free - Free allocated memory

Breakpoint Management

breakpoint.set - Set breakpoint
breakpoint.delete - Remove breakpoint
breakpoint.enable - Enable breakpoint
breakpoint.disable - Disable breakpoint
breakpoint.toggle - Toggle breakpoint state
breakpoint.list - List all breakpoints
breakpoint.get - Get breakpoint details
breakpoint.delete_all - Remove all breakpoints
breakpoint.set_condition - Set breakpoint condition
breakpoint.set_log - Set breakpoint log message
breakpoint.reset_hitcount - Reset breakpoint hit count

Disassembly

disassembly.at - Disassemble at address
disassembly.range - Disassemble address range
disassembly.function - Disassemble entire function

Symbol Resolution

symbol.resolve - Resolve symbol to address
symbol.from_address - Get symbol from address
symbol.search - Search symbols by pattern
symbol.list - List all symbols
symbol.modules - List loaded modules
symbol.set_label - Set symbol label
symbol.set_comment - Set symbol comment
symbol.get_comment - Get symbol comment

Module Operations

module.list - List all loaded modules
module.get - Get module information
module.get_main - Get main module

Thread Operations

thread.list - List all threads
thread.get_current - Get current thread
thread.get - Get thread information
thread.switch - Switch to thread
thread.suspend - Suspend thread
thread.resume - Resume thread
thread.get_count - Get thread count

Stack Operations

stack.get_trace - Get stack trace
stack.read_frame - Read stack frame
stack.get_pointers - Get stack pointers (RSP/RBP on x64, ESP/EBP on x86)
stack.is_on_stack - Check if address is on stack

For complete method signatures and examples, see the inline documentation in the source code or use the system.methods API call.

Architecture

The plugin is organized into four layers:

Communication Layer: HTTP server with SSE support for real-time events
Protocol Layer: JSON-RPC and MCP protocol parsing, validation, dispatching
Business Layer: Debugging operations, memory management, symbol resolution
Plugin Layer: x64dbg integration, event handling, callback management

Key Components

MCPHttpServer: HTTP server with SSE endpoint for event streaming
MethodDispatcher: Routes JSON-RPC calls to appropriate handlers
Business Managers: DebugController, MemoryManager, RegisterManager, etc.
Event System: Real-time debugging event notifications via SSE

Security Considerations

By default, memory and register write operations are disabled
Enable write permissions in config.json only if needed
Server listens on localhost (127.0.0.1) by default
Single client connection limit prevents resource exhaustion
All operations require the debugger to be in a paused state

Troubleshooting

Plugin not loading

Match the plugin to the debugger: x64dbg_mcp.dp64 in x64\plugins\ for x64dbg, or x32dbg_mcp.dp32 in x32\plugins\ for x32dbg
Do not load a .dp64 plugin in x32dbg or a .dp32 plugin in x64dbg
Check the corresponding x64dbg/x32dbg log for error messages
Verify debugger version compatibility (requires x64dbg/x32dbg build 2023+)

Server won't start

Check if port 3000 is already in use
Verify config.json is valid JSON
Check file permissions on the plugin directory
Review the corresponding x64dbg/x32dbg log file for detailed error messages

Connection refused

Ensure HTTP server is started via plugin menu ("Start MCP HTTP Server")
Check firewall settings for port 3000
Verify client is connecting to http://127.0.0.1:3000
Try accessing http://127.0.0.1:3000 in a web browser to test

Contributing

Contributions are welcome! Please:

Fork the repository
Create a feature branch
Make your changes with clear commit messages
Submit a pull request

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments

x64dbg - The debugger this plugin extends
nlohmann/json - JSON library
Model Context Protocol specification

Contact

GitHub Issues: For bug reports and feature requests

Note: This is experimental software. Use at your own risk. Always test in a safe environment before using with critical applications.

Rendered by GitHub from the current README

Read on GitHub

Top contributors

No contributor data yet — it is fetched during the contributor sync pass.

Quality score

Would you bet a product on this? Bounded 0–100 and slow moving.

72/10072

Maintenance: 70%; How recently the default branch was pushed to
Releases: 81%; Recency and cadence of tagged releases
Community: 20%; Contributor breadth and bus factor
Issue backlog: 100%; Open issues measured against the size of the audience
Documentation: 91%; README depth, plus a homepage and topics
Licensing: 100%; How freely the code can be adopted

What to know before adopting

Nothing flagged — maintained, documented and cleanly licensed.
Usable in commercial products with attribution.

Details

Created: 10 months ago
Last push: last month
Last release: last month
Release tag: v1.0.11
Releases in the last year: 11
Default branch: main
Size: 544 KB
Owner type: User
Owner location: China
Discovered via: phrase:mcp server
First indexed: 2 months ago
Last synced: 7 days ago

SetsunaYukiOvO/x64dbg-mcp

MCP server plugin for x64dbg debugger - enables AI agents and external tools to control debugging via JSON-RPC 2.0 over HTTP/SSE

72MITC++

View on GitHub

Stars: 478
Forks: 61
Watchers: 2
Open issues: 3
Contributors: —

Star history, last 90 days+145 over 36 snapshots

2026-07-31 · 3332026-09-20 · 478

Star history, last 90 days
Date	Stars
2026-07-31	333
2026-08-02	337
2026-08-12	371
2026-08-18	393
2026-08-19	396
2026-08-20	399
2026-08-21	401
2026-08-22	405
2026-08-23	409
2026-08-24	414
2026-08-25	419
2026-08-26	424
2026-08-27	429
2026-08-28	431
2026-08-29	432
2026-08-30	435
2026-08-31	438
2026-09-01	446
2026-09-02	447
2026-09-03	451
2026-09-04	455
2026-09-05	454
2026-09-06	455
2026-09-07	455
2026-09-08	456
2026-09-09	457
2026-09-10	459
2026-09-11	462
2026-09-12	463
2026-09-13	464
2026-09-14	465
2026-09-15	469
2026-09-16	471
2026-09-17	474
2026-09-18	475
2026-09-20	478

Today

+3 stars today

This week

+14 stars this week

This month

+77 stars this month

Momentum

26.0

growth rate 3.02%/day

From the README

x64dbg MCP Server Plugin

English | 中文

Now supports both x64 and x86 architectures!

Features

Full MCP Specification Compliance: Implements all three core MCP building blocks
- Tools (79): AI-invokable debugging functions
- Resources (7 + 8 templates): Application-controlled context data sources
- Prompts (10): User-guided debugging workflow templates
JSON-RPC 2.0 Protocol: Standard, language-agnostic interface
Streamable HTTP transport (MCP 2025-03-26) on /mcp, plus legacy HTTP+SSE on /sse for older clients
Tools - AI-Controlled Debugging (79 functions):
- Execution control (init/run/pause/step/run_to/restart/stop)
- Memory read/write/search/allocate
- Register access (50+ registers including GPR, SSE, AVX)
- Breakpoint management (software, hardware, memory, conditional, logging)
- Disassembly and symbol resolution
- Thread management (list, switch, suspend, resume)
- Stack trace and analysis
- Dump & Analysis (module dump, memory dump, packer detection, OEP detection)
- Script execution (execute x64dbg/x32dbg commands, batch operations)
- Context snapshots (capture and compare debugging state)
Resources - Context Providers (7 direct + 8 templates):
- Direct resources: debugger state, registers, modules, threads, memory map, breakpoints, stack
- Resource templates: memory content, disassembly, module info, symbol resolution, function analysis
- Read-only, application-controlled access
Prompts - Workflow Templates (10 prompts):
- Crash analysis, vulnerability hunting, function tracing
- Binary unpacking, algorithm reversing, execution comparison
- String hunting, code patching, API monitoring
- Debug session initialization
Security: Permission-based access control
Extensible: Plugin architecture for custom methods, resources, and prompts

Prerequisites

Windows 10/11 (64-bit host; supports building both x64 and x86 plugins)
CMake 3.15 or higher
Visual Studio 2022 with C++ Desktop Development workload
vcpkg - Package manager for C++ libraries
Git - For cloning the repository

Quick Build

The easiest way to build is using the provided build script:

# Clone the repository
git clone https://github.com/SetsunaYukiOvO/x64dbg-mcp.git
cd x64dbg-mcp

# Build both x64 and x86 architectures (recommended)
.\build.bat

# Build only x64 architecture
.\build.bat --x64-only

# Build only x86 architecture
.\build.bat --x86-only

# Clean rebuild
.\build.bat --clean

# The script will:
# 1. Automatically detect vcpkg installation
# 2. Download dependencies (nlohmann_json)
# 3. Configure CMake for both architectures
# 4. Build using Visual Studio with parallel compilation
# 5. Copy output files to dist/ directory

Build script options:

.\build.bat               # Build both x64 and x86 (Release)
.\build.bat --clean       # Clean rebuild both architectures
.\build.bat --x64-only    # Build x64 only
.\build.bat --x86-only    # Build x86 only
.\build.bat --debug       # Debug build (future support)

Output files (in dist/ directory):

x64 plugin: dist\x64dbg_mcp.dp64 (~837 KB)
x86 plugin: dist\x32dbg_mcp.dp32 (~800 KB)

Manual Build Steps

If you prefer manual control:

Install vcpkg (if not already installed):

git clone https://github.com/Microsoft/vcpkg.git C:\vcpkg
C:\vcpkg\bootstrap-vcpkg.bat
setx VCPKG_ROOT "C:\vcpkg"

Clone the repository:

git clone https://github.com/SetsunaYukiOvO/x64dbg-mcp.git
cd x64dbg-mcp

Configure with CMake:

# For x64 build
cmake -B build_x64 -G "Visual Studio 17 2022" -A x64 ^
    -DCMAKE_TOOLCHAIN_FILE=C:/vcpkg/scripts/buildsystems/vcpkg.cmake ^
    -DVCPKG_TARGET_TRIPLET=x64-windows ^
    -DXDBG_ARCH=x64

# For x86 build
cmake -B build_x86 -G "Visual Studio 17 2022" -A Win32 ^
    -DCMAKE_TOOLCHAIN_FILE=C:/vcpkg/scripts/buildsystems/vcpkg.cmake ^
    -DVCPKG_TARGET_TRIPLET=x86-windows ^
    -DXDBG_ARCH=x86

Build:

cmake --build build_x64 --config Release
cmake --build build_x86 --config Release

Output:

x64 plugin: build_x64\bin\Release\x64dbg_mcp.dp64
x86 plugin: build_x86\bin\Release\x32dbg_mcp.dp32

Installation

Copy the compiled plugins to their respective debugger directories:

# For x64dbg (64-bit)
# Replace <x64dbg-path> with your actual x64dbg installation directory
copy dist\x64dbg_mcp.dp64 <x64dbg-path>\x64\plugins\

# For x32dbg (32-bit)
copy dist\x32dbg_mcp.dp32 <x64dbg-path>\x32\plugins\

# Example (if installed at C:\x64dbg):
# copy dist\x64dbg_mcp.dp64 C:\x64dbg\x64\plugins\
# copy dist\x32dbg_mcp.dp32 C:\x64dbg\x32\plugins\

(Optional) Copy the configuration file:

# For x64dbg
mkdir <x64dbg-path>\x64\plugins\x64dbg-mcp
copy config.json <x64dbg-path>\x64\plugins\x64dbg-mcp\

# For x32dbg
mkdir <x64dbg-path>\x32\plugins\x32dbg-mcp
copy config.json <x64dbg-path>\x32\plugins\x32dbg-mcp\

Restart x64dbg/x32dbg to load the plugin

Usage

Starting the Server

Open x64dbg for a 64-bit target or x32dbg for a 32-bit target
Navigate to Plugins → MCP Server → Start MCP HTTP Server
The server will start on the configured port (default: 3000)
Access the server at http://127.0.0.1:3000

Configuration

Edit config.json to customize settings:

{
  "version": "1.0.11",
  "server": {
    "address": "127.0.0.1",
    "port": 3000
  },
  "permissions": {
    "allow_memory_write": false,
    "allow_register_write": false,
    "allow_script_execution": false,
    "allow_breakpoint_modification": true,
    "allowed_methods": ["debug.*", "memory.*"]
  },
  "security": {
    "origin_allowlist": [],
    "host_allowlist": [],
    "auth_enabled": false,
    "auth_token": ""
  },
  "logging": {
    "enabled": true,
    "level": "info",
    "file": "x64dbg_mcp.log",
    "max_file_size_mb": 10,
    "console_output": true
  },
  "timeout": {
    "request_timeout_ms": 30000,
    "step_timeout_ms": 10000,
    "memory_read_timeout_ms": 5000
  },
  "features": {
    "enable_notifications": true,
    "enable_heartbeat": true,
    "heartbeat_interval_seconds": 30,
    "enable_batch_requests": true,
    "auto_start_mcp_on_plugin_load": false
  }
}

Configuration editor

Remote Access and Security

Local-only (recommended default)

Use 127.0.0.1:3000 and connect from the same Windows host. No firewall rule or port forwarding is required.

LAN or VM access

Only do this on a trusted network. Change the bind address and explicitly allow the address used by the client:

{
  "server": { "address": "0.0.0.0", "port": 3000 },
  "security": {
    "origin_allowlist": ["http://192.168.1.50:3000"],
    "host_allowlist": ["192.168.1.20", "debugger.example.test"]
  }
}

Endpoints:

Streamable HTTP clients: http://HOST:3000/mcp
Legacy HTTP+SSE clients: http://HOST:3000/sse
JSON-RPC compatibility endpoint: http://HOST:3000/rpc
Health check: GET http://HOST:3000/

Internet access

To enable built-in Bearer authentication, store a high-entropy secret in the plugin configuration and restart the plugin:

{
  "security": {
    "auth_enabled": true,
    "auth_token": "replace-with-a-long-random-secret"
  }
}

Common connection failures

Connection refused: verify the plugin server is started, the bind address/port, and VM NAT or firewall rules.
403 or rejected request: add the exact browser Origin to security.origin_allowlist and the proxy/client Hostname to security.host_allowlist.
MCP initialize succeeds but tools are missing: reconnect after initialize; clients discover capabilities from the response.
SSE hangs or returns 404: use /sse for legacy SSE clients and /mcp for Streamable HTTP clients.
Works through one proxy but not another: check that HTTP/1.1 streaming, long read timeouts, and SSE buffering are enabled.

For a first diagnostic, run curl http://127.0.0.1:3000/ on the debugger host, then test the same URL through each forwarding layer. Do not include debugger memory or credentials in issue logs.

Client Example

Python client example using HTTP:

import requests
import json

class MCPClient:
    def __init__(self, host='127.0.0.1', port=3000):
        self.base_url = f"http://{host}:{port}"
        self.request_id = 1
    
    def call(self, method, params=None):
        request = {
            "jsonrpc": "2.0",
            "id": self.request_id,
            "method": method,
            "params": params or {}
        }
        self.request_id += 1
        
        response = requests.post(
            f"{self.base_url}/rpc",
            json=request,
            headers={"Content-Type": "application/json"}
        )
        return response.json()
    
    def subscribe_events(self):
        """Subscribe to SSE events"""
        response = requests.get(
            f"{self.base_url}/sse",
            stream=True,
            headers={"Accept": "text/event-stream"}
        )
        for line in response.iter_lines():
            if line:
                yield line.decode('utf-8')

# Usage
client = MCPClient()
print(client.call("initialize"))
print(client.call("tools/list"))
print(client.call("resources/list"))
print(client.call("prompts/list"))

# Subscribe to debug events
for event in client.subscribe_events():
    print(f"Event: {event}")

VS Code Integration

Configure in VS Code settings or MCP client config. Recommended (Streamable HTTP, MCP 2025-03-26):

{
  "mcpServers": {
    "x64dbg": {
      "type": "http",
      "url": "http://127.0.0.1:3000/mcp"
    }
  }
}

Legacy HTTP+SSE clients (use the /sse path, not the root):

{
  "mcpServers": {
    "x64dbg": {
      "type": "sse",
      "url": "http://127.0.0.1:3000/sse"
    }
  }
}

Available Methods

System Methods

system.info - Get server information
system.ping - Test connection
system.methods - List all available methods

Debug Control

debug.run - Continue execution
debug.pause - Pause execution
debug.step_into - Step into instruction
debug.step_over - Step over instruction
debug.step_out - Step out of function
debug.get_state - Get current debug state
debug.run_to - Run to specific address
debug.restart - Restart debugging session
debug.stop - Stop debugging

Register Operations

register.get - Read single register
register.set - Write register value
register.list - List all registers
register.get_batch - Read multiple registers

Memory Operations

memory.read - Read memory region
memory.write - Write memory region
memory.search - Search memory pattern
memory.get_info - Get memory region info
memory.enumerate - List all memory regions
memory.allocate - Allocate memory
memory.free - Free allocated memory

Breakpoint Management

breakpoint.set - Set breakpoint
breakpoint.delete - Remove breakpoint
breakpoint.enable - Enable breakpoint
breakpoint.disable - Disable breakpoint
breakpoint.toggle - Toggle breakpoint state
breakpoint.list - List all breakpoints
breakpoint.get - Get breakpoint details
breakpoint.delete_all - Remove all breakpoints
breakpoint.set_condition - Set breakpoint condition
breakpoint.set_log - Set breakpoint log message
breakpoint.reset_hitcount - Reset breakpoint hit count

Disassembly

disassembly.at - Disassemble at address
disassembly.range - Disassemble address range
disassembly.function - Disassemble entire function

Symbol Resolution

symbol.resolve - Resolve symbol to address
symbol.from_address - Get symbol from address
symbol.search - Search symbols by pattern
symbol.list - List all symbols
symbol.modules - List loaded modules
symbol.set_label - Set symbol label
symbol.set_comment - Set symbol comment
symbol.get_comment - Get symbol comment

Module Operations

module.list - List all loaded modules
module.get - Get module information
module.get_main - Get main module

Thread Operations

thread.list - List all threads
thread.get_current - Get current thread
thread.get - Get thread information
thread.switch - Switch to thread
thread.suspend - Suspend thread
thread.resume - Resume thread
thread.get_count - Get thread count

Stack Operations

stack.get_trace - Get stack trace
stack.read_frame - Read stack frame
stack.get_pointers - Get stack pointers (RSP/RBP on x64, ESP/EBP on x86)
stack.is_on_stack - Check if address is on stack

For complete method signatures and examples, see the inline documentation in the source code or use the system.methods API call.

Architecture

The plugin is organized into four layers:

Communication Layer: HTTP server with SSE support for real-time events
Protocol Layer: JSON-RPC and MCP protocol parsing, validation, dispatching
Business Layer: Debugging operations, memory management, symbol resolution
Plugin Layer: x64dbg integration, event handling, callback management

Key Components

MCPHttpServer: HTTP server with SSE endpoint for event streaming
MethodDispatcher: Routes JSON-RPC calls to appropriate handlers
Business Managers: DebugController, MemoryManager, RegisterManager, etc.
Event System: Real-time debugging event notifications via SSE

Security Considerations

By default, memory and register write operations are disabled
Enable write permissions in config.json only if needed
Server listens on localhost (127.0.0.1) by default
Single client connection limit prevents resource exhaustion
All operations require the debugger to be in a paused state

Troubleshooting

Plugin not loading

Match the plugin to the debugger: x64dbg_mcp.dp64 in x64\plugins\ for x64dbg, or x32dbg_mcp.dp32 in x32\plugins\ for x32dbg
Do not load a .dp64 plugin in x32dbg or a .dp32 plugin in x64dbg
Check the corresponding x64dbg/x32dbg log for error messages
Verify debugger version compatibility (requires x64dbg/x32dbg build 2023+)

Server won't start

Check if port 3000 is already in use
Verify config.json is valid JSON
Check file permissions on the plugin directory
Review the corresponding x64dbg/x32dbg log file for detailed error messages

Connection refused

Ensure HTTP server is started via plugin menu ("Start MCP HTTP Server")
Check firewall settings for port 3000
Verify client is connecting to http://127.0.0.1:3000
Try accessing http://127.0.0.1:3000 in a web browser to test

Contributing

Contributions are welcome! Please:

Fork the repository
Create a feature branch
Make your changes with clear commit messages
Submit a pull request

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments

x64dbg - The debugger this plugin extends
nlohmann/json - JSON library
Model Context Protocol specification

Contact

GitHub Issues: For bug reports and feature requests

Note: This is experimental software. Use at your own risk. Always test in a safe environment before using with critical applications.

Rendered by GitHub from the current README

Read on GitHub

Top contributors

No contributor data yet — it is fetched during the contributor sync pass.

Quality score

Would you bet a product on this? Bounded 0–100 and slow moving.

72/10072

Maintenance: 70%; How recently the default branch was pushed to
Releases: 81%; Recency and cadence of tagged releases
Community: 20%; Contributor breadth and bus factor
Issue backlog: 100%; Open issues measured against the size of the audience
Documentation: 91%; README depth, plus a homepage and topics
Licensing: 100%; How freely the code can be adopted

What to know before adopting

Nothing flagged — maintained, documented and cleanly licensed.
Usable in commercial products with attribution.

Details

Created: 10 months ago
Last push: last month
Last release: last month
Release tag: v1.0.11
Releases in the last year: 11
Default branch: main
Size: 544 KB
Owner type: User
Owner location: China
Discovered via: phrase:mcp server
First indexed: 2 months ago
Last synced: 7 days ago

Top AI Repos — open-source AI, indexed and scored

Trend

From the README

x64dbg MCP Server Plugin

Features

Prerequisites

Quick Build

Manual Build Steps

Installation

Usage

Starting the Server

Configuration

Configuration editor

Remote Access and Security

Local-only (recommended default)

LAN or VM access

Internet access

Common connection failures

Client Example

VS Code Integration

Available Methods

System Methods

Debug Control

Register Operations

Memory Operations

Breakpoint Management

Disassembly

Symbol Resolution

Module Operations

Thread Operations

Stack Operations

Architecture

Key Components

Security Considerations

Troubleshooting

Plugin not loading

Server won't start

Connection refused

Contributing

License

Acknowledgments

Contact

Top contributors

Quality score

What to know before adopting

Categories

Details

Trend

From the README

x64dbg MCP Server Plugin

Features

Prerequisites

Quick Build

Manual Build Steps

Installation

Usage

Starting the Server

Configuration

Configuration editor

Remote Access and Security

Local-only (recommended default)

LAN or VM access

Internet access

Common connection failures

Client Example

VS Code Integration

Available Methods

System Methods

Debug Control

Register Operations

Memory Operations

Breakpoint Management

Disassembly

Symbol Resolution

Module Operations

Thread Operations

Stack Operations

Architecture

Key Components

Security Considerations