That's not how I'd describe it- it's not meant to centralize servers, it's the idea: maybe you don't need to build and distribute a separate downloadable thing for users to interact with your service/product/whatever via agent, and instead they continue to use your website via an appropriate interface for agents.

(Here's another comment with an explanation https://news.ycombinator.com/item?id=45623782)

The npm package is only there as the browser doesn't natively support the behavior (yet). Similarly MCP clients don't have built in support. So it's a bridge/proxy to demonstrate what could be done.

I think the centralization aspect sounds potentially very useful so I didn't mean it like a deal-breaker. I've been thinking it's a matter of time before someone figures out a good way to centralize MCP tools. This kind of thing could be huge; like the Google of MCP tools.