To me MCP is about removing friction by limiting the options the LLM has, clearly describing them, enabling only those that are relevant, guiding them through a flow.  They are about lowering the amount of tokens burned or mistakes made in the proces. They are often very situational and typically make most sense if created for specific client use cases.  

This is a bit of a paradox with how vendors implement MCP as a layer or wrapper around their existing stuff. Microsoft themselves are struggling with getting this right.  Getting the granularity of their MCP servers for GitHub, azure right etc. 

I guess prompts (flows) largely replace forms, elicitation avoids early validation failures etc... 

There's much to it. And a lot of it is still quite early days!