1. Home
  2. ghidraMCP
  3. ghidraMCP for Cursor: Setup & Config

Data as of

ghidraMCP for Cursor: Setup & Config

ghidraMCP connects Cursor to core Ghidra analysis features through a plugin and Python bridge.

What you can do with ghidraMCP in Cursor

Choose it to bring Ghidra decompilation and renaming into an assistant workflow through a plugin bridge.

  • Browse program methods, classes, imports, and exports.
  • Connect a running Ghidra instance to Claude Desktop or Cline.

Before you start: ghidraMCP in Cursor

  • Ghidra
  • Python 3
  • MCP Python SDK
  • The installed and enabled GhidraMCP plugin
  • The Python bridge from a project release

Replace the README’s absolute-path placeholder with the bridge location. The HTTP URL is the bridge’s Ghidra backend, not a remote MCP endpoint. Cline can instead use the documented SSE bridge mode.

ghidraMCP Cursor configuration

  1. Choose Cursor configuration scope

    For ghidraMCP, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add ghidraMCP to Cursor

    Use the GhidraMCP entry below in mcpServers. Keep ghidraMCP's documented stdio connection fields and your other Cursor entries.

  3. Check ghidraMCP in Cursor

    ghidraMCP: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

JSON
{
  "mcpServers": {
    "GhidraMCP": {
      "command": "python",
      "args": [
        "/ABSOLUTE_PATH_TO/bridge_mcp_ghidra.py",
        "--ghidra-server",
        "http://127.0.0.1:8080/"
      ],
      "env": {}
    }
  }
}

Troubleshooting ghidraMCP in Cursor

  • Cursor must find python (Python) for ghidraMCP. Enable the project/user entry in MCP settings and inspect its tools.
  • ghidraMCP uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Requires Ghidra extension installation, restart, and plugin enablement.
  • Known limitation: Building from source requires Ghidra JAR files and Maven packaging.
  • Known limitation: Individual MCP tool identifiers are Not stated in the README.
  • General Cursor troubleshooting lives in the /clients/cursor guide.

ghidraMCP — details. Cursor guide

Frequently asked questions

Cursor's ghidraMCP entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's GhidraMCP example uses stdio.

ghidraMCP's Cursor configuration invokes python (Python).

The documented default is localhost on port 8080, and the target address and port can be changed.

Yes. The Cline example manually starts the Python bridge with SSE transport and connects to its /sse endpoint.