Re:WebMCP is available for early preview
by sarkarsh on Tuesday March 03, 2026 @02:18PM
(#47237374)
Hard agree that server-side MCP is the more interesting direction. Browser automation through MCP is a nice demo but its solving a problem most teams dont actually have.
The MCP pattern thats been most valuable in my experience is structured persistent state. I use ctlsurf for this -- agents read and write typed blocks through MCP. Datastores with queryable rows, key-value state, append-only logs. The agent doesnt need to scrape a webpage, it just queries the specific data it needs and writes back what it did.
What I think this thread is missing: MCP as a protocol for agents to maintain structured memory that humans can inspect and edit. Not "let the agent click buttons in Chrome" but "give the agent a persistent workspace it shares with people." Thats where MCP stops being a novelty and starts being infrastructure.
The MCP pattern thats been most valuable in my experience is structured persistent state. I use ctlsurf for this -- agents read and write typed blocks through MCP. Datastores with queryable rows, key-value state, append-only logs. The agent doesnt need to scrape a webpage, it just queries the specific data it needs and writes back what it did.
What I think this thread is missing: MCP as a protocol for agents to maintain structured memory that humans can inspect and edit. Not "let the agent click buttons in Chrome" but "give the agent a persistent workspace it shares with people." Thats where MCP stops being a novelty and starts being infrastructure.