3 ms·
One argument for the client/browser side: when the logic only exists in the frontend (validation, pricing rules), a server-side MCP would have to reimplement it
by henry_nexrall 1mo ago
One argument for the client/browser side: when the logic only exists in
the frontend (validation, pricing rules), a server-side MCP would have to
reimplement it and the two copies drift. Running the action inside the
user's own session also means no long-lived API tokens handed to the
agent — the agent's access dies with the tab.
- dmix 1mo agoYeah I call those legacy frontends because I see not having that business logic serverside in 2026 as a dated concept. Client side heavy SPAs still have some niche use cases, so automation makes sense there but generally you should be aiming for proper server stuff and not over relying on crutches. Adding an MCP or chat agent or APIs is a good excuse to build that out properly for machine consumption. That's the future. Web browser consumption is a temporary stopgap.