Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Model Context Protocol

anthropic.com

Post reply on HN
Print view View original

231–240 of 283 posts

Re: Model Context Protocol

#231

Post by xyc »

Just tried out the puppeteer server example if anyone is interested in seeing a demo: https://x.com/chxy/status/1861302909402861905. (Todo: add tool use - prompt would be like "go to this website and screenshot")

I appreciate the design which left the implementation of servers to the community which doesn't lock you into any particular implementation, as the protocol seems to be aiming to primarily solve the RPC layer.

One major value add of MCP I think is a capability extension to a vast amount of AI apps.

Re: Model Context Protocol

#234

Post by xyc »

xyc wrote: post #231

Just tried out the puppeteer server example if anyone is interested in seeing a demo: https://x.com/chxy/status/1861302909402861905 . (Todo: add tool use - prompt would be like "go to this website and screenshot") I appreciate the design which left the implementation of servers to the community which doesn't lock you into any particular implementation, as the protocol seems to be aiming to primarily solve the RPC lay…

sharing the messy code here just for funsies: https://gist.github.com/xyc/274394031b41ac7e8d7d3aa7f4f7bed9

Re: Model Context Protocol

#235

Post by Palmik »

thund wrote: post #104
melvinmelih wrote: post #100

This is great but will be DOA if OpenAI (80% market share) decides to support something else. The industry trend is that everything seems to converge to OpenAI API standard (see also the recent Gemini SDK support for OpenAI API).

"OpenAI API" is not a "standard" though. They have no interest in making it a standard, otherwise they would make it too easy to switch AI provider. Anthropic is playing the "open standard" card because they want to win over some developers. (and that's good from that pov)

OpenAI API is natively supported by several providers (Google, Mistral, to name a few).

Re: Model Context Protocol

#236

Post by [deleted] »

ed wrote: post #119
wolframhempel wrote: post #96

I'm surprised that there doesn't seem to be a concept of payments or monetization baked into the protocol. I believe there are some major companies to be built around making data and API actions available to AI Models, either as an intermediary or marketplace or for service providers or data owners directly- and they'd all benefit from a standardised payment model on a per transaction level.

I’ve gone looking for services like this but couldn’t find much, any chance you can link to a few platforms?

[deleted]

Re: Model Context Protocol

#237

Post by rsong_ »

ed wrote: post #119
wolframhempel wrote: post #96

I'm surprised that there doesn't seem to be a concept of payments or monetization baked into the protocol. I believe there are some major companies to be built around making data and API actions available to AI Models, either as an intermediary or marketplace or for service providers or data owners directly- and they'd all benefit from a standardised payment model on a per transaction level.

I’ve gone looking for services like this but couldn’t find much, any chance you can link to a few platforms?

I'm working on Exfunc [1], which is an API for AI to fetch data and take action on the web. Sent you an email, would love to chat.

[1] https://www.exfunc.com

Re: Model Context Protocol

#238

Post by thoughtlede »

If function calling is sync, is MCP its async counterpart? Is that the gist of what MCP is?

Open API (aka swagger) based function calling is standard already for sync calls, and it solves the NxM problem. I'm wondering if the proposed value is that MCP is async.

Re: Model Context Protocol

#239

Post by delegate »

I appreciate the effort, but after spending more than one hour on it, I still don't understand how and why I'd use this.

The Core architecture [1] documentation is given in terms of TypeScript or Python abstractions, adding a lot of unnecessary syntactic noise for someone who doesn't use these languages. Very thin on actual conceptual explanation and full of irrelevant implementation details.

The 'Your first server'[2] tutorial is given in terms of big chunks of python code, with no explanation whatsoever, eg:

    Add these tool-related handlers:
    ...100 lines of undocumented code...
The code doesn't even compile. I don't think this is ready for prime time yet so I'll move along for now.

[1] https://modelcontextprotocol.io/docs/concepts/architecture [2] https://modelcontextprotocol.io/docs/first-server/python

Re: Model Context Protocol

#240

Post by bsenftner »

somnium_sn wrote: post #3

@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.

You guys need a professional documentation person on your team, one that specializes in only writing documentation. I say this because the existing documentation is a confusing mess. This is going to cause all kinds of problems purely because it is weakly explained, and I see incorrect usage of words all over. Even the very beginning definitions of client, host and server are nonstandard.
Post reply on HN