How to support non-HTML-based surfaces?

[lrosenthol]

Many non-browser-based clients also interact with MCP, but by forcing all UI to text/html it is not possible for those clients to present reasonable experiences without being forced to introduce insecure and non-native experiences to their users.

I would like to see support for either (a) fallback provisions or (b) a declarative model instead of explicit HTML/CSS/etc. or (c) both.

[idosal]

This is definitely in the roadmap