Hopper's MCP in something like Codex is *killer*. I can ask it things like, 'what private API could I use to make a UIKit window dockable on visionOS', and it will just figure it out from the disassembly, same way I would — just a lot faster.

Its solution matches the one I reverse-engineered myself a while back (https://github.com/steventroughtonsmith/VisionImmersiveDockableUIKit/blob/main/VisionImmersiveDockableUIKit/Source/Application/VVUDockableWindowScene.swift)

@stroughtonsmith Is that this one? https://github.com/MxIris-Reverse-Engineering/HopperMCP

Or did Hopper gain one recently directly?

GitHub - MxIris-Reverse-Engineering/HopperMCP: A Model Context Protocol server for Hopper Disassembler

A Model Context Protocol server for Hopper Disassembler - MxIris-Reverse-Engineering/HopperMCP

GitHub
@mikeymikey it's just built-in, instructions in Hopper's Help
@stroughtonsmith Thanks! I had a license and have let it lapse, wasn't following in the latest
@stroughtonsmith I can’t believe the plagiarism robot trained on public GitHub repos managed to replicate something you published on a public GitHub repo
@LucasCMoore that's not how MCPs work. It's tool-calling, and you can watch it do it step by step. And it went deep beyond it when I started asking for more-complicated details
@stroughtonsmith Been using this for a few weeks, I will say that you have to definitely tame your LLM client as far as parallel tool-calling (mine gets very enthusiastic) because I have dead-locked macOS several times with the dreaded "You have run out of application memory" 😬