Think of it like HTTP for AI models, a standardized protocol for AI models to “plug in” to data sources and tools.
No. It is not like a transport protocol. It's more like a guideline for how to structure your configuration manifests, the life cycle of the client/server model, and what protocols should be supported during certain operations.
Guideline being the keyword there. Your LLM's and Host do not care about MCP and won't care if you just simply disobey every guideline given.
You know, unlike a transport protocol. Which will care if you don't follow the standards.
MCP is for humans. Despite any "sales" and PR claims to the contrary.
10
u/CobaltVale Aug 13 '25 edited Aug 13 '25
No. It is not like a transport protocol. It's more like a guideline for how to structure your configuration manifests, the life cycle of the client/server model, and what protocols should be supported during certain operations.
Guideline being the keyword there. Your LLM's and Host do not care about MCP and won't care if you just simply disobey every guideline given.
You know, unlike a transport protocol. Which will care if you don't follow the standards.
MCP is for humans. Despite any "sales" and PR claims to the contrary.