MCP ConfigsMay 11, 2026·3 min read

GhidraMCP — Reverse Engineering MCP Server

GhidraMCP is an MCP server + Ghidra plugin for autonomous reverse engineering. Install the extension from releases, then run the bridge script.

Agent ready

Safe staging for this asset

This asset is staged first. The copied prompt tells the agent to inspect the staged files and ask before activating scripts, MCP config, or global config.

Stage only · 17/100Policy: stage
Agent surface
Any MCP/CLI agent
Kind
Mcp Config
Install
Stage only
Trust
Trust: Established
Entrypoint
Asset
Safe staging command
npx -y tokrepo@latest install c05c76f2-6e85-48c4-9b80-0115dff62a65 --target codex

Stages files first; activation requires review of the staged README and plan.

Intro

GhidraMCP is a verified GitHub-backed asset sourced from LaurieWired/GhidraMCP with 8,828 stars and a Apache-2.0 license snapshot. Best for: reverse engineers who want to expose Ghidra decompiler analysis to an MCP-capable assistant for structured exploration. Works with: Ghidra, Python 3, MCP clients such as Claude Desktop/Cline (per repo examples). Setup time: 20 minutes.

Quantitative notes


Deep Dive

What it solves

Use this when you need a repeatable, team-shareable workflow instead of one-off agent prompts. The goal is to make installation, first-run validation, and rollback predictable.

Minimal mental model

  • Treat the GitHub repo as the source of truth: install instructions, configs, and upgrade paths live there.
  • Keep your first run small: one command, one verification, one rollback plan.
  • Capture a baseline: setup time, first successful run, and one real task completed end-to-end.

Safe rollout checklist

  1. Verify source: confirm repo URL, stars, and license match what you expect.
  2. Install using the Quick Use commands above.
  3. Prove it works with the verification command; save the output in a note or issue.
  4. Operationalize: document owner, upgrade command, and rollback command.

Troubleshooting (common)

  • Install succeeds but nothing shows up

    • Likely cause: the tool needs a restart/reload (CLI/IDE) or a config file in the right path.
    • Fix: restart the client, then re-run the verification step.
  • Works on one machine, fails on another

    • Likely cause: Node/Python/Docker versions differ or missing system dependencies.
    • Fix: pin versions (Node/Python), and copy a minimal known-good config.
  • Token cost or latency is worse than expected

    • Likely cause: tool schemas or verbose outputs get injected into context.
    • Fix: prefer smaller steps, cache results, and keep tool responses concise when possible.

FAQ

Q: Do I need to build from source? A: No—start from the repo releases zip which includes the plugin and Python bridge, then build later only if you need customization.

Q: What should I do first in a new binary? A: Open it in Ghidra, let analysis finish, then ask your MCP client to list functions/exports before renaming or patching.

Q: How do I keep it safe? A: Use localhost defaults, and never run untrusted binaries on a sensitive machine—treat reverse engineering as a high-risk workflow.


🙏

Source & Thanks

GitHub: https://github.com/LaurieWired/GhidraMCP Owner avatar: https://avatars.githubusercontent.com/u/123765654?v=4 License (SPDX): Apache-2.0 Stars (verified via api.github.com/repos/LaurieWired/GhidraMCP): 8,828

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets