View state persistence #417
Description
Views may need to persist private state locally.
Currently, the protocol doesn't provide a native mechanism for it. Many apps opt for browser API patterns (e.g., localStorage). This solution is brittle because it assumes these APIs are available and consistent across environments, even though their availability depends on unspecified runtime constraints (e.g., user agent, origin management).
MCP Apps should either document the runtime constraints or define a reliable API.
Related to #213