The protocol felt unnecessarily complicated till I saw this https://modelcontextprotocol.io/docs/concepts/sampling It's crazy. Sadly not yet implemented in Claude Desktop client.
What's use case for this?
Model Context Protocol
211–220 of 283 posts
Re: Model Context Protocol
#212It's great! I quickly reorganised my custom gpt repo to build a shell agent using MCP.
https://github.com/rusiaaman/wcgw/blob/main/src/wcgw/client/...
Already getting value out of it.
Re: Model Context Protocol
#213I took time to read everything on Twitter/Reddit/Documentation about this. I think I have a complete picture. Here is a quickstart for anyone who is just getting into it. https://glama.ai/blog/2024-11-25-model-context-protocol-quic...
fine. Examples, what can I use this for?
Re: Model Context Protocol
#214I took time to read everything on Twitter/Reddit/Documentation about this. I think I have a complete picture. Here is a quickstart for anyone who is just getting into it. https://glama.ai/blog/2024-11-25-model-context-protocol-quic...
fine. Examples, what can I use this for?
have you read either TFA or their blog post? There are plenty of examples.
Re: Model Context Protocol
#215Earlier quoted context omitted.
Will this be partially available from the Claude website for connections to other web services? E.g. could the GitHub server be called from https://claude.ai ?
At the moment only Claude Desktop supports MCP. Claude.ai itself does not.
Any idea on timelines? I’d love to be able to have generation and tool use contained within a customer’s AWS account using bedrock. Ie I pass a single cdk that can interface with an exposed internet MCP service and an in-VPC service for sensitive data.
Re: Model Context Protocol
#216The default transport should have accommodated binary data. Whether it’s tensors of image data, audio waveforms, or pre-tokenized NLP workloads it’s just going to hit a wall where JSON-RPC can’t express it uniquely and efficiently.
Re: Model Context Protocol
#217Something is telling me this _might_ turn out to be a huge deal; I can't quite put a finger on what is that makes me feel that, but opening private data and tools via an open protocol to AI apps just feels like a game changer.
It's just function calling with a new name and a big push from the LLM provider, but this time it's in the right direction . Contrast with OpenAI's "GPTs", which are just function calling by another name, but pushed in the wrong direction - towards creating a "marketplace" controlled by OpenAI. I'd say that thing you're feeling comes from witnessing an LLM vendor, for the first time in history, actually being serious…
But either way the interface is just providing a json schema of functions along with your chat completion request, and a server with ability to parse and execute the response. I’m not really seeing where a new layer of abstraction helps here (much less a new “protocol”, as though we need a new transport layer?
It smells like the thinking is that you (the developer) can grab from a collection of very broad data connectors, and the agent will be able to figure out what to do with them without much custom logic in between. Maybe I’m missing something
Re: Model Context Protocol
#218Re: Model Context Protocol
#219The protocol felt unnecessarily complicated till I saw this https://modelcontextprotocol.io/docs/concepts/sampling It's crazy. Sadly not yet implemented in Claude Desktop client.
what’s crazy about it?
Re: Model Context Protocol
#220@jspahrsummers and I have been working on this for the last few months at Anthropic. I am happy to answer any questions people might have.
Why not use GraphQL instead of inventing a whole new protocol?
I agree. GraphQL is highly suitable for this. Anyway, I think just a simple adapter could make it work with this MCP thing.