x64dbg MCP server

Created By
CaptainNoxa year ago
An MCP server for the x64dbg debugger
Overview

what is x64dbg MCP server?

The x64dbg MCP server is a simple server designed to connect the x64dbg debugger to various AI agents, enhancing the debugging experience with automation capabilities.

how to use x64dbg MCP server?

To use the x64dbg MCP server, set it up alongside the x64dbg debugger and configure it to connect with your preferred AI agents for automated debugging tasks.

key features of x64dbg MCP server?

  • Seamless integration with x64dbg debugger
  • Ability to connect to multiple AI agents
  • Automation of debugging tasks

use cases of x64dbg MCP server?

  1. Automating repetitive debugging tasks with AI assistance.
  2. Enhancing debugging efficiency by leveraging AI insights.
  3. Connecting to various AI tools for improved debugging workflows.

FAQ from x64dbg MCP server?

  • Can I use x64dbg MCP server with any AI agent?

Yes! The server is designed to connect with various AI agents to enhance your debugging process.

  • Is x64dbg MCP server free to use?

Yes! The x64dbg MCP server is open-source and free to use under the MIT license.

  • What programming language is x64dbg MCP server written in?

The server is written in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
CaptainNox
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