Skip to content
Kitbay
Submit
MCP server

GhidraMCP

Runs locallyMITUpdated on Sep 23, 202693GitHub starsCan change data

This GhidraMCP, by themixednuts, runs the MCP server inside Ghidra itself as an extension, with no separate bridge: clients connect to a local HTTP endpoint (127.0.0.1:8080/mcp by default, port set in Ghidra's tool options).

What it does

This GhidraMCP, by themixednuts, runs the MCP server inside Ghidra itself as an extension, with no separate bridge: clients connect to a local HTTP endpoint (127.0.0.1:8080/mcp by default, port set in Ghidra's tool options). It offers 14 grouped tools for analysis, inspection, annotation, functions, symbols, data types, memory, debugging through Trace RMI, project workflows and Version Tracking, plus resources for program views such as imports, strings and decompiled code, and prompts for common reversing jobs. Actions can move the user's open CodeBrowser to the relevant address. It is installed from a release zip through Install Extensions, requires Ghidra 12.1.4, and credits LaurieWired's GhidraMCP as its starting point.

Capabilities

  • Inspect and decompile functions in an open Ghidra program
  • Annotate code and edit symbols, data types and memory
  • Control Ghidra's debugger through Trace RMI
  • Run Version Tracking sessions
  • Rebase program image bases