@HISEnberg haha yes that is some funky stuff, my favorite part is how I replicated the module tree in ASCII art:
105ab78b-2dcc-424e-ac6d-a7d6cc7b2de5-image.png
I've also pulled in the entire setup.hise.dev stuff into this app - this bypasses some of the quirks of the website approach - now people just have to download this self-contained binary TUI app and type in /setup and it will perform all the steps from the setup workflow.
It also acts as logger for monitoring what the LLM does - if you have the TUI open and the LLM calls
hise-cli -builder add Sampler
then this shows up in the chat history with an "LLM" tag.
I'm probably moving all the runtime functionality out of the MCP server as soon as the hise_cli is ready so the MCP becomes a read-only documentation / explorer tool that sits on the HISE doc server - currently it needs to be run locally so it can connect to the HISE Rest server, but since the Hise-cli is doing the same thing too it's easier to separate these tasks.
The MCP server also integrates with the new doc website and uses a small embedding model and a vector database for looking up docs & code examples - I evaluated different approaches, but that gives me the advantage of checking the quality of the MCP search.
