x64dbg_mcp_server_pro

Created By
kenanhakmana year ago
Overview

what is x64dbg_mcp_server_pro?

x64dbg_mcp_server_pro is a powerful MCP (Message Command Protocol) server that enables remote debugging of Windows executables via x64dbg directly from Visual Studio Code using extensions like CLine and RooCode.

how to use x64dbg_mcp_server_pro?

To use x64dbg_mcp_server_pro, clone the repository, unzip the downloaded archive, and configure your VSCode settings to connect to the MCP server.

key features of x64dbg_mcp_server_pro?

  • Full control over debug session lifecycle (start, stop, attach, detach)
  • Seamless execution control with step-by-step navigation
  • Memory inspection and manipulation capabilities
  • Advanced breakpoint handling
  • Register and symbol management
  • Utility commands for server status and help

use cases of x64dbg_mcp_server_pro?

  1. Debugging Windows applications remotely from Visual Studio Code.
  2. Inspecting and manipulating memory during debugging sessions.
  3. Automating analysis of executables with integrated tools.

FAQ from x64dbg_mcp_server_pro?

  • Can I use x64dbg_mcp_server_pro with any Windows executable?

Yes! It is designed to work with any Windows executable that can be debugged with x64dbg.

  • Is there a specific setup required for Visual Studio Code?

Yes! You need to configure the RooCode or CLine extension with the appropriate MCP server settings.

  • What programming language is x64dbg_mcp_server_pro written in?

It is written in Python and is open-source under the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kenanhakman
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago