Skip to main content
Glama
ouonet

x64dbg MCP Server

by ouonet

load_executable

Load a PE executable into x64dbg and create a debugging session. Returns a sessionId required by all other tools. Automatically detects 32-bit or 64-bit binaries and launches the appropriate debugger. Optionally pause at entry point or run immediately.

Instructions

START HERE — load a PE executable into x64dbg and create a debugging session. Returns a sessionId that ALL other tools require as their first parameter. Auto-detects 32-bit vs 64-bit PE and launches x32dbg or x64dbg accordingly. With breakOnEntry=true (default): execution stops at the entry point and the session state becomes 'paused' — you can immediately call step_into, get_registers, or disassemble. With breakOnEntry=false: the debuggee starts running; use set_breakpoint then continue_execution to pause it later. Only one session can be active at a time. Call terminate_session first if one exists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
executablePathYesAbsolute path to the PE executable (.exe or .dll)
commandLineArgsNoOptional command-line arguments to pass to the executable
breakOnEntryNoPause at the entry point (default true)
autoAnalyzeNoRun initial analysis on load (default true)
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description fully discloses behavior: auto-detection of 32/64-bit PE, debugger selection, session state transitions, and the impact of breakOnEntry. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single well-structured paragraph with clear sentences, front-loading the purpose and progressively adding details. No redundant statements.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a debugger entry point, the description covers core functionality, parameter effects, session management, and next steps. Even without an output schema, it mentions the return value sessionId and state, making it sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. The description adds value by elaborating on breakOnEntry behavior (execution state, follow-up actions) and noting autoAnalyze default, though it could explain autoAnalyze consequences more. Overall, it enhances understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool loads a PE executable into x64dbg and creates a debugging session, returning a sessionId. It is positioned as 'START HERE', distinguishing it from sibling tools that require this sessionId.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance: use first, only one active session requires termination, and details when to use breakOnEntry=true vs false with post-load actions. Effectively tells the agent when and how to use the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

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/ouonet/x64dbg-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server