01 · Product name
GhidraMCP
An MCP server that exposes a running Ghidra to an AI client.
Published by LaurieWired.
In short
GhidraMCP is an open-source Model Context Protocol server that exposes a running Ghidra to an AI client. The canonical repository is LaurieWired/GhidraMCP. Its README describes a Ghidra plugin plus an MCP server that can decompile, list methods and imports, and rename methods and data inside the project. It is free under Apache 2.0. You still need Ghidra. A rename writes the Ghidra project. It is not a second opinion about whether the file is malicious.
Product pricing strategy
02
Free
GhidraMCP is free. The repository ships under the Apache License 2.0. There is no pricing page and no paid tier in the README. You still install Ghidra, which is also free, at the version the GhidraMCP README requires. This listing does not invent a hosted plan. The license file and the README are the sources.
Utility and features
03
The LaurieWired/GhidraMCP README describes ghidraMCP as a Model Context Protocol server that lets a language model use core Ghidra functions. The features it lists are a Ghidra plugin and an MCP server: decompile and analyze binaries in Ghidra, automatically rename methods and data, and list methods, classes, imports, and exports. The license file is Apache 2.0. Prerequisites in that README are Ghidra 12.1.4 from ghidra-sre.org, and uv or Python 3.10 or newer.
- Plugin plus MCP server. The README's feature list is an MCP server and a Ghidra plugin that decompiles, lists methods and imports, and renames methods and data.
- Ghidra 12.1.4. The prerequisites name Ghidra 12.1.4 from ghidra-sre.org, plus uv or Python 3.10 or newer.
- Other Ghidra MCP servers. On 15 October 2026, bethington/ghidra-mcp was the next starred repository described as a Ghidra MCP server. It is a different codebase. This page is LaurieWired/GhidraMCP.
On 15 October 2026, a GitHub repository search for "ghidra mcp", sorted by stars, placed LaurieWired/GhidraMCP first among results described as an MCP server for Ghidra, at 11,285 stars. bethington/ghidra-mcp was the next result with that kind of description, at 5,648 stars, and it is a separate project. The top result overall was morluto/rea, at 265,977 stars, whose description is a general reverse-engineering agent rather than a Ghidra MCP server, so it is not this page.
Installation, as the README writes it, is a release zip imported with File, Install Extensions, then the GhidraMCPPlugin enabled under File, Configure, Developer. The optional port setting is Edit, Tool Options, GhidraMCP HTTP Server. The sample client config points the MCP server at http://127.0.0.1:8080/ unless you change it. A rename from the client writes the open Ghidra project.
- 1
Install Ghidra 12.1.4, the version the GhidraMCP README requires.
- 2
Download the GhidraMCP release and install the extension zip from File, Install Extensions, then enable GhidraMCPPlugin.
- 3
Point an MCP client at the Ghidra server. The README's sample config uses http://127.0.0.1:8080/.
- 4
Treat a rename as a write to that Ghidra project. Work from a copy if the project is evidence.
Caveats
04
The README pins the extension to Ghidra 12.1.4 and names the release zip ghidra_12.1.4_PUBLIC_<date>_GhidraMCP.zip. A different Ghidra build may not match that extension.
Automatic rename writes the Ghidra project. Keep a copy before you let a client rename methods or data. The sample config uses a local address. Opening an untrusted binary is still a lab task. This page does not describe unpacking or vulnerability reproduction.
Screenshots
05
Potential use cases
06
- You already have a Ghidra project open on a binary you are allowed to analyze, and you want an MCP client to list methods, classes, imports, and exports. Install the extension version the README names for the Ghidra build it names. The output is those lists inside the client, which you then check in Ghidra. A different Ghidra build may not match the extension. The sample config uses a local address. Do not expose it.
- You ask the client to decompile one function and you read the result in Ghidra, not only in the chat. The output is a decompiler view of that function, with the same limits as Ghidra itself. It is not a verdict and not an unpacking guide. This page does not describe vulnerability reproduction.
- Rename tools write the program. Before you let a client rename methods or data, copy the project. The output you want from a first session is a listing, not a mutated database. If a rename already happened, the hard part is knowing the project is no longer the file you imported. Keep the copy. The README is the source for the zip name and the Ghidra version pin.
Hard cases
The case where the first result is easy to over-read.
The client renames the case project
An automatic rename feels like progress and it writes the Ghidra database. If you did not keep a copy, you cannot show the pre-rename state. Stop the client, restore the copy, and use the MCP tools that list and decompile until you have decided a rename is worth keeping. The local socket in the sample config stays on that machine. Opening an untrusted binary is still a lab task, with or without the extension.
Questions
Is GhidraMCP free?
Yes. LaurieWired/GhidraMCP is Apache License 2.0. Ghidra is a separate free install. The README does not list a paid tier.
Does GhidraMCP replace Ghidra?
No. It is a plugin and an MCP server for a Ghidra you already run. The README requires Ghidra 12.1.4.
Citations
07
Titled sources. These public pages are what the quotes on this listing come from.
Product
GhidraMCP repository
https://github.com/LaurieWired/GhidraMCPDocumentation
GhidraMCP README
https://github.com/LaurieWired/GhidraMCP/blob/main/README.mdDocumentation
GhidraMCP releases
https://github.com/LaurieWired/GhidraMCP/releasesDocumentation
bethington ghidra-mcp repository
https://github.com/bethington/ghidra-mcpDocumentation
morluto rea repository
https://github.com/morluto/rea