# 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. ## Install Merge the JSON below into your `.mcp.json`: ## Quick Use 1. Install the verified entrypoint: ```bash Download the latest release zip and install the extension via Ghidra (File → Install Extensions) ``` 2. Run a first local check: ```bash Add MCP config pointing to bridge_mcp_ghidra.py and your Ghidra server URL ``` 3. Add a repeatable verification step: ```bash python bridge_mcp_ghidra.py --transport sse --mcp-host 127.0.0.1 --mcp-port 8081 --ghidra-server http://127.0.0.1:8080/ ``` --- ## 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 - Default Ghidra server URL http://127.0.0.1:8080/ (repo) - Example MCP port 8081 (repo) --- ## 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 --- # GhidraMCP——逆向工程的 MCP Server > GhidraMCP 是“Ghidra 插件 + MCP Server”组合,让 LLM 在 Ghidra 中自动做反编译、重命名与分析。下载 release 安装扩展并重启 Ghidra,再运行 bridge 脚本接入客户端。 ## 快速使用 1. 安装(以仓库为准): ```bash Download the latest release zip and install the extension via Ghidra (File → Install Extensions) ``` 2. 首次运行/检查: ```bash Add MCP config pointing to bridge_mcp_ghidra.py and your Ghidra server URL ``` 3. 可重复验证: ```bash python bridge_mcp_ghidra.py --transport sse --mcp-host 127.0.0.1 --mcp-port 8081 --ghidra-server http://127.0.0.1:8080/ ``` --- ## 简介 GhidraMCP 已核验来源于 `LaurieWired/GhidraMCP`(8,828 stars,许可证 Apache-2.0)。适合:希望把 Ghidra 的反编译/分析能力暴露给支持 MCP 的助手、进行结构化探索的逆向工程师。兼容:Ghidra、Python 3、Claude Desktop/Cline 等 MCP client(仓库示例)。装机时间:20 分钟。 ### 量化信息 - 默认 Ghidra server: http://127.0.0.1:8080/(仓库) - 示例 MCP 端口 8081(仓库) --- ## 深度说明 ### 解决什么问题 把“找到项目 → 安装 → 首次验证 → 回滚/升级”变成可复用流程,避免只靠一次性提示词或截图操作。 ### 最小心智模型 - GitHub 仓库是事实来源:安装、配置、升级、已知问题都以它为准。 - 第一次只做最小闭环:一个命令安装、一个命令验证、一个可回滚方案。 - 记录基线:装机耗时、首次成功输出、完成 1 个真实任务的证据。 ### 安全推广清单 1. **核验来源**:确认仓库 URL / stars / license 与预期一致。 2. 按“快速使用”完成安装与首次检查。 3. 跑通“验证命令”,把输出留档。 4. 标注 owner,并写清升级/回滚步骤。 ### 常见排障 - **装了但看不到效果** - 常见原因:需要重启 CLI/IDE 或配置文件路径不对。 - 处理:重启后再跑一遍“验证命令”。 - **一台机器能跑,另一台不行** - 常见原因:Node/Python/Docker 版本差异或缺少系统依赖。 - 处理:固定版本,并拷贝最小可用配置。 - **token 成本/延迟超预期** - 常见原因:工具 schema 或输出过长被塞进上下文。 - 处理:拆小步骤、缓存结果、尽量让工具输出更短。 --- ### FAQ **Q: 需要从源码编译吗?** A: 不需要;先用 release zip 安装插件与 Python bridge,只有需要定制时再考虑源码构建。 **Q: 新二进制第一步做什么?** A: 先让 Ghidra 完成分析,再通过 MCP 让助手列出函数/导出等结构信息,然后再做重命名或深入追踪。 **Q: 怎么更安全?** A: 默认只用 localhost;逆向属于高风险工作流,不要在敏感机器上跑不可信二进制。 --- ## 来源与感谢 > GitHub:https://github.com/LaurieWired/GhidraMCP > Owner avatar:https://avatars.githubusercontent.com/u/123765654?v=4 > 许可证(SPDX):Apache-2.0 > GitHub stars(已通过 `api.github.com/repos/LaurieWired/GhidraMCP` 核验):8,828 --- Source: https://tokrepo.com/en/workflows/ghidramcp-reverse-engineering-mcp-server Author: MCP Hub