MCP UI as the web's next form — rendering HTML from tool calls¶
Insight: MCP UI represents a potential paradigm shift where web interfaces are rendered from MCP tool calls rather than traditional server-rendered pages. Key challenges include context bloat (MCP responses consuming too much context window), the distinction between MCP and Skills (MCP for external tools, Skills for project-local context), and whether chat-first interfaces will replace traditional browser navigation. The practical question is when to return HTML from tool calls vs. when to keep responses as data.