I'm really unexcited about bolting HTML/CSS/JS and the entire webstack into MCP so that a full-featured MCP client has to carry a full web browser, too.
I expect there's a pretty wide divide between what people who write local MCP servers want, versus what people who write cloud webstack MCP webapps want.
Personally, I've been adding local native UI to my MCP servers, but I realize that's probably a losing battle, and if I want to integrate with newer tooling, I'm going to be stuck in web hell.
I expect there's a pretty wide divide between what people who write local MCP servers want, versus what people who write cloud webstack MCP webapps want.
Personally, I've been adding local native UI to my MCP servers, but I realize that's probably a losing battle, and if I want to integrate with newer tooling, I'm going to be stuck in web hell.