Earlier quoted context omitted.
So it is, I stand corrected. I googled mcp host and the lmstudio link was the first result. Some more discussion on the confusion here https://github.com/modelcontextprotocol/modelcontextprotocol... where they acknowledge that most people call it a client and that that's ok unless the distinction is important. I think host is a bad term for it though as it makes more intuitive sense for the host to host the server an…
I'm with you on the confusion, it makes no sense at all to call it a host. MCP host should host the MCP server (yes, I know - that is yet a separate term). The MCP standard seems a mess, e.g take this paragraph from here[1] > In the Streamable HTTP transport, the server operates as an independent process that can handle multiple client connections. Yes, obviously, that is what servers do. Also, what is "Streamable HT…
As far as I can tell, unsurprisingly, the MCP specification was written with the help of LLMs, and seemingly hasn't been carefully reviewed because as you say, a bunch of the terms have straight up wrong definitions.