GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
MCP server for x64dbg debugger - 23 mega-tools for AI-powered reverse engineering and debugging
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
X64DBG_MCP_HOST, X64DBG_MCP_PORTYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"x64dbg": {
"command": "npx",
"args": [
"-y",
"x64dbg-mcp-server"
],
"env": {
"X64DBG_MCP_HOST": "your-value",
"X64DBG_MCP_PORT": "your-value"
}
}
}
}Run this in your terminal
claude mcp add x64dbg --env X64DBG_MCP_HOST=your-value --env X64DBG_MCP_PORT=your-value -- npx -y x64dbg-mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"x64dbg": {
"command": "npx",
"args": [
"-y",
"x64dbg-mcp-server"
],
"env": {
"X64DBG_MCP_HOST": "your-value",
"X64DBG_MCP_PORT": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"x64dbg": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"x64dbg-mcp-server"
],
"env": {
"X64DBG_MCP_HOST": "your-value",
"X64DBG_MCP_PORT": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
X64DBG_MCP_HOST envX64DBG_MCP_PORT envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account bromoket, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (2.3.0) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Drive [x64dbg](https://x64dbg.com/) with your AI. Talk to Claude, Cursor, Windsurf, Cline, or any MCP client in plain English and it sets breakpoints, reads memory, disassembles, traces, dumps PEs, and bypasses anti-debug — live, inside the debugger.
23 mega-tools over 153 REST endpoints, fully typed with Zod. A C++ plugin runs inside x64dbg; a tiny TypeScript server bridges it to your client over stdio. Everything stays on 127.0.0.1 — nothing leaves your machine.
Latest — v2.3.0
- Hardened & crash-proof. A malformed HTTP request can no longer crash x64dbg; the plugin
server drains connections cleanly on stop and ships an optional auth token (CORS is
locked down).
- Real data from more tools.
imports/exports,symbolssearch/list,patcheslist,
and
stringsnow return actual parsed results instead of pointing you at a GUI view.
- Live trace status. New
/api/trace/status(+tracing status) reports whether a trace
is running, and the exception/trace tools now honor every parameter they accept.
- Plus the v2.2.x fixes: x32dbg loads on current snapshots, and requests no longer time out
on long operations.
"Set a breakpoint on CreateFileW and run the program"
"Disassemble the current function and explain what it does" "Search for 48 8B ?? 48 85 C0 in the main module and disassemble the hits" "Hide the debugger and bypass the anti-debug checks" "Trace into the VM dispatcher and log every instruction to a file" "Dump the main module to disk and fix the import table"
Real use: tracing VMProtect'd code, finding anti-cheat scanner threads, decoding XOR'd class names, mapping detection logic — all by asking, no manual scripting.
Download x64dbg_mcp.dp64 / .dp32 from the latest release and drop them in:
x64dbg/x64/plugins/x64dbg_mcp.dp64 ← 64-bit targets
x64dbg/x32/plugins/x64dbg_mcp.dp32 ← 32-bit targets
…or build + install it yourself (auto-detects your x64dbg — no path editing):
.\build.ps1 -Install
Start x64dbg; the log shows [MCP] x64dbg MCP Server started on 127.0.0.1:27042.
No install — just point your client at npx. Claude Code:
{
"mcpServers": { "x64dbg": { "type": "stdio", "command": "cmd", "args": ["/c", "npx", "-y", "x64dbg-mcp-server"] } } }
Claude Desktop / Cursor / Windsurf / Cline use the same block without the cmd /c wrapper: { "command": "npx", "args": ["-y", "x64dbg-mcp-server"] }. Full per-client paths are in the reference.
Open a target in x64dbg and start talking to your assistant.
23 action-based tools spanning the whole debugger:
Every tool, action, and endpoint is documented in [docs/REFERENCE.md](docs/REFERENCE.md).
The plugin binds to 127.0.0.1 only; the server talks pure stdio. All traffic stays on localhost — no remote access, no telemetry, no data leaves your machine. For defense against other local processes, set a token in the plugin's Settings and pass it via X64DBG_MCP_TOKEN — every request must then carry it.
bromo — GitHub. Built with Claude Code. MIT.