I did something similar using ghidramcp for digging around this keyboard firmware, repo contains the ghidra project, linux driver and even patches to the original stock fw. https://github.com/echtzeit-solutions/monsgeek-akko-linux
yes, but it requires some nudging if you don't want to waste tokens. it will happily grep and sed through massive javascript bundles but if you tell it to first create tooling like babel scripts to format, it will be much quicker.
I can tell you from first hand experience that claude+ghidra mcp is very good at understanding firmware, labeling functions, finding buffer overflows, patching in custom functionality
That one, sadly, does not have USB-C output, so it's fine for something you're wiring up custom but isn't a generic solution (which, to be fair, is the quite niche overlap of wanting to power something with USB-C without a battery and wanting battery backup).
So you're saying they could just make the driver compliant without advertising compliance under the hdmi logo? similar to how e.g. oneplus shipped phones without advertising their higher IPX rating because certification would have cost too much, or chinese electronics supporting "tf card" instead of "micro sd card" but being compatible anyways
I made a mcp that would use a pty lib to allow claude to debug a TUI app I was writing with ok-ish results. ultimately I wanted to see what was happening myself so when I need interactive I just tell it to use tmux-cli to capture the neighboring pane. https://github.com/pchalasani/claude-code-tools/blob/main/do...
maybe turning that into a mcp with more guardrails and integrated guide to the agent would make it more popwerful
I'm not actually sure about that (that turning it into an MCP would help). I've seen more momentum building around having better cli tool integration with ClaudeCode than MCP reliance.