Ghostmcp MCP Server

Ghost-MCP is an injectable MCP (Model Context Protocol) server for vibe reverse engineering assistant on Windows. It combines memory inspection

Local serverstdio

What is the Ghostmcp MCP server?

Ghostmcp MCP server exists for a simple reason — assistants are far more useful when they can act on Ghostmcp directly instead of describing what you should do. Ghost-MCP is an injectable MCP (Model Context Protocol) server for vibe reverse engineering assistant on Windows. It combines memory inspection, disassembly, debugging, and code injection into a single tool that any MCP-compatible AI.

What the assistant can call

Once Ghostmcp is connected, these are the calls the assistant has available:

  • Server — side filtering** to include/exclude by API name, module, thread, return value
  • safety_status — View current mode, stats, and pending approvals
  • safety_set_mode — Switch between educational/standard/expert
  • safety_approve — Approve a pending dangerous operation
  • patch_history — View all patches applied this session
  • patch_undo — Restore original bytes for any patch
  • patch_preview — Dry-run preview before applying patches

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Ghostmcp's toolset — Server, safety_status, safety_set_mode and 4 more — is a fair guide to whether it matches your workflow. It is maintained by mq1n; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the ghostmcp mcp server does with a few real requests.

Available tools

ToolWhat it does
Serverside filtering** to include/exclude by API name, module, thread, return value
safety_statusView current mode, stats, and pending approvals
safety_set_modeSwitch between educational/standard/expert
safety_approveApprove a pending dangerous operation
patch_historyView all patches applied this session
patch_undoRestore original bytes for any patch
patch_previewDry-run preview before applying patches

How to install the Ghostmcp MCP server

{
  "mcpServers": {
    "ghost-core": {
      "command": "path/to/ghost-core-mcp.exe",
      "args": ["--transport", "stdio"]
    },
    "ghost-analysis": {
      "command": "path/to/ghost-analysis-mcp.exe",
      "args": ["--port", "13341"]
    },
    "ghost-static": {
      "command": "path/to/ghost-static-mcp.exe",
      "args": ["--port", "13342"]
    },
    "ghost-extended": {
      "command": "path/to/ghost-extended-mcp.exe",
      "args": ["--port", "13343"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Ghostmcp to Server.
  • Use Ghostmcp to safety status.
  • Use Ghostmcp to safety set mode.

Frequently asked questions

It connects Ghostmcp to MCP-compatible AI assistants such as Claude and Cursor, exposing 7 tools (Server, safety_status, safety_set_mode, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Ghostmcp directly.