Model Context Protocol: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<div style="background-color: black; color: white;"> | <div style="background-color: black; color: white;"> | ||
<blockquote><h1>The Other MCP</h1><blockquote> | <blockquote><h1>The Other MCP</h1><blockquote> | ||
''[[:en:Model Context Protocol|<span style="color:lime;">Model Context Protocol</span>]]'' is an industry initiative for LLM infra standardization. Together with LangChain it provides a basis for substitution of different LLM services for DevOps users extending DCP.<br><br> | ''[[:en:Model Context Protocol|<span style="color:lime;">Model Context Protocol</span>]]'' is an industry initiative for LLM infra standardization. Together with LangChain it provides a basis for substitution of different LLM services for DevOps users extending DCP.<br> | ||
<br>The namestyle DCP/MCP is adopted for my OS construct and it will always outside 3rd party LLM service contexts be implicit and context should make which is referenced clear in regards to the commercial services, where "Anthropic MCP", "LSP MCP", or "LangChain MCP" may be used for clarity.<br><br> | |||
As a strategic direction, I am supporting MCP as the means making readers LLM services pluggable to the novel. The canonical external foundational models are Claude and Gemini but I am supporting them only in the sense of the prior sentence. Our approach is to leverage and not duplicate these expensive resources and pass thru the biz of our common clients. We dont anticipate ever constructing anything other than domain specific models albeit ofc in our overall approach which isn LLM centric. | As a strategic direction, I am supporting MCP as the means making readers LLM services pluggable to the novel. The canonical external foundational models are Claude and Gemini but I am supporting them only in the sense of the prior sentence. Our approach is to leverage and not duplicate these expensive resources and pass thru the biz of our common clients. We dont anticipate ever constructing anything other than domain specific models albeit ofc in our overall approach which isn LLM centric. | ||
</blockquote><br><br></blockquote> | </blockquote><br><br></blockquote> | ||
</div> | </div> | ||
Revision as of 05:01, 3 January 2026
The Other MCP
Model Context Protocol is an industry initiative for LLM infra standardization. Together with LangChain it provides a basis for substitution of different LLM services for DevOps users extending DCP.
The namestyle DCP/MCP is adopted for my OS construct and it will always outside 3rd party LLM service contexts be implicit and context should make which is referenced clear in regards to the commercial services, where "Anthropic MCP", "LSP MCP", or "LangChain MCP" may be used for clarity.
As a strategic direction, I am supporting MCP as the means making readers LLM services pluggable to the novel. The canonical external foundational models are Claude and Gemini but I am supporting them only in the sense of the prior sentence. Our approach is to leverage and not duplicate these expensive resources and pass thru the biz of our common clients. We dont anticipate ever constructing anything other than domain specific models albeit ofc in our overall approach which isn LLM centric.
