Comment by bbkane
7 hours ago
Interesting, but I'm not sure how it's different from Observable Framework ( https://observablehq.github.io/framework/ ) for dashboards as code. I like that one because it's Markdown and JS instead of a language defined in YAML + templates
The use case that immediately came to mind for me was to use dbt charts as a rendering method for an MCP App.
You don't really want to give a LLM client code execution environment like Observable Framework does. dbt charts appear to validate the entire yaml input including the SQL being sent to the data source.
So I'm getting: a data vis layer that can be dynamically defined and rendered via LLM/MCP client without the headache of sandboxing a JS Runtime environment.
I like the observable framework too - very flexible, you can nail very specific visualization details by dropping down to JS/html.
Maybe this is targeted to pure SQL folks that can get lost in UI details.
PS: one issue that I have with observable framework is authentication and authorization , it requires some system to be built on top of it to handle authn.