MCP: An in-depth introduction
speakeasy.com
MCP: An in-depth introduction
1–10 of 96 posts
Re: MCP: An in-depth introduction
#2I feel like I need the opposite, a cursory view, or at least a definition.
Most of the material on MCP is either too specific or too in depth.
WTF is it?! (Other than a dependency by Anthropic)
Re: MCP: An in-depth introduction
#3I feel like I need the opposite, a cursory view, or at least a definition. Most of the material on MCP is either too specific or too in depth. WTF is it?! (Other than a dependency by Anthropic)
This is a VFAQ https://hn.algolia.com/?q=what+is+mcp
But to save you the click & read: it's OpenAPI for LLMs
Re: MCP: An in-depth introduction
#4"“MCP is an open protocol that standardizes how applications provide context to LLMs, what’s the problem?”"
We are already off to a wrong start, context has a meaning specific to LLMs, everyone who works with LLMs knows what it means: the context is the text that is fed as input at runtime to LLM, including the current message (user prompt) as well as the previous messages and responses by the LLM.
So we don't need to read any further and we can ignore this article, and MCPs by extension, YAGNI
Re: MCP: An in-depth introduction
#5I feel like I need the opposite, a cursory view, or at least a definition. Most of the material on MCP is either too specific or too in depth. WTF is it?! (Other than a dependency by Anthropic)
It's an API to expose tools to LLMs.
Re: MCP: An in-depth introduction
#6"“MCP is an open protocol that standardizes how applications provide context to LLMs, what’s the problem?”" We are already off to a wrong start, context has a meaning specific to LLMs, everyone who works with LLMs knows what it means: the context is the text that is fed as input at runtime to LLM, including the current message (user prompt) as well as the previous messages and responses by the LLM. So we don't need t…
This is a really shallow dismissal, and I say that as someone who is outspokenly critical of MCP [0].
As you yourself say, the context is the text that is fed as input at runtime to an LLM. This text could just always come from the user as a prompt, but that's a pretty lousy interface to try to cram everything that you might want the model to know about, and it puts the onus entirely on the user to figure out what might be relevant context. The premise of the Model Context Protocol (MCP) is overall sound: how do we give the "Model" access to load arbitrary details into "Context" from many different sources?
This is a real problem worth solving and it has everything to do with the technical meaning of the word "context" in this context. I'm not sure why you dismiss it so abruptly.
Re: MCP: An in-depth introduction
#7For anyone confused, you can play with mcp for free on usetexture.com
Re: MCP: An in-depth introduction
#8I feel like I need the opposite, a cursory view, or at least a definition. Most of the material on MCP is either too specific or too in depth. WTF is it?! (Other than a dependency by Anthropic)
This is a VFAQ https://hn.algolia.com/?q=what+is+mcp But to save you the click & read: it's OpenAPI for LLMs
OpenAPI for LLMs is such a good way to describe it!
Re: MCP: An in-depth introduction
#9I feel like I need the opposite, a cursory view, or at least a definition. Most of the material on MCP is either too specific or too in depth. WTF is it?! (Other than a dependency by Anthropic)
https://youtu.be/74c1ByGvFPE?si=S-5oBO8ptL_7WmQ9
I like this succinct explanation.