While fun this game-like interface is too casual and it certainly has lower bit rate which impacts communicate exchange between an AI and the human operator.
It will be a fine abstraction if the goal is to have high-level overview though.
Using coding agent is great btw, but at least learn how to double check their work cuz they are also quite terrible.
The other issue is that you cannot think of MCP servers as universal pluggable systems that can fit into every use-case with minimal wrapping. Real world scenarios require pulling a lot of tricks. Caching can be done at higher or lower level depending on the use-case. Communication of different information from the MCP server also is different depending on the use-case (should we replace these long IDs for shorter IDs that are automatically translated to longer ones). Should we automatically tinyurl all the links to reduce hallucination? Which operations can be effectively solved with pure algorithms (compress 2-3 operations into one) because doing this with LLMs is not only error-prone but also not optimal (imagine using LLM to grep for strings in many files one by one using tool calls rather than using grep to search for strings - not the same)
There are so many things to consider. MCP is nice abstraction but it is not a silver bullet.
Speaking from experience with actual customers and real use-case.
As a result, we've opted not to list our product on marketplaces in general. Instead, we support custom integrations directly with our customers.
I've also been burned in the past by Apple, Chrome, and Mozilla.
I understand that all of these companies run business and I understand that there are legitimate security and privacy concerns (I used to lead security teams, so this issue is close to my heart), but even so, these platforms often fall short of being truly developer-friendly, especially toward legitimate builders trying to create value - especially when this value is created outside of the said marketplaces.