Ghidra MCP exposes Ghidra reverse-engineering workflows to MCP clients. Start on the Ghidra MCP listing for the install command, transport, and source. This post covers client setup, headless notes, and safety—not a replacement for the listing.

If you searched for ghidra mcp or ghidra mcp headless, confirm the listing’s runtime (GUI vs headless) before you point an agent at a binary.

What Ghidra MCP is

Ghidra MCP is an MCP server. It is not a skill. Expect local or lab-only use: binaries, projects, and analysis tools the listing enumerates. Treat anything that can open a file as sensitive.

Install command

Copy the command from Ghidra MCP. Headless or JVM flags belong on that page or in the linked repository—do not invent extra arguments here.

Client setup

1. Install Ghidra (and Java) as the listing’s prerequisites require.
2. Register the MCP command in Cursor, Claude, VS Code, or Codex.
3. Point the server at a dedicated project directory—not your whole disk.
4. Restart MCP. Ask the agent to list tools, then open a sample binary you are allowed to analyze.

Caveats

• Only analyze binaries you have rights to inspect.
• Headless mode still needs a project path and enough RAM. Follow upstream docs linked from the listing.
• Do not enable write or export tools against production artifacts until you have seen a successful read-only listing.

When to choose something else

General coding tools: MCP servers list. Browser automation: Playwright MCP setup. Other setup posts: Figwright and Figma MCP Bridge.

Related: Ghidra MCP listing, Figwright MCP setup, MCP clients, and the MCP servers list.