Chat turns backends into chat apps

This is the pragmatic side of MCP: instead of building a custom frontend for every workflow, teams can ship a polished chat surface on top of existing backend logic.

• –One external MCP server is enough to make the app useful, which lowers the bar for internal tools, vertical SaaS, and MVPs.
• –The project is more than a demo shell: it includes streaming responses, persistent chat history, authentication, image attachments, and locale support.
• –The tradeoff is obvious but acceptable for many teams: chat is great for guided workflows, but complex products will still need richer UI patterns.
• –The `MCP_URL` vs `MCP_APPS_URL` split shows this is aimed at teams already invested in MCP, not casual builders who just want a generic chatbot.