Live data from Hacker News

Model Context Protocol

anthropic.com

31–40 of 283 posts

Re: Model Context Protocol

#31
Hmm I like the idea of providing a unified interface to all LLMs to interact with outside data. But I don't really understand why this is local only. It would be a lot more interesting if I could connect this to my github in the web app and claude automatically has access to my code repositories.

I guess I can do this for my local file system now?

I also wonder if I build an LLM powered app, and currently simply to RAG and then inject the retrieved data into my prompts, should this replace it? Can I integrate this in a useful way even?

The use case of on your machine with your specific data, seems very narrow to me right now, considering how many different context sources and use cases there are.

Re: Model Context Protocol

#32
post #16

i am curious: why this instead of feeding your LLM an OpenAPI spec?

It's not about the interface to make a request to a server, it's about how the client and server can interact. For example: When and how should notifications be sent and how should they be handled? --- It's a lot more like LSP.

makes sense, thanks for the explanation!

Re: Model Context Protocol

#33

Hmm I like the idea of providing a unified interface to all LLMs to interact with outside data. But I don't really understand why this is local only. It would be a lot more interesting if I could connect this to my github in the web app and claude automatically has access to my code repositories. I guess I can do this for my local file system now? I also wonder if I build an LLM powered app, and currently simply to R…

> It would be a lot more interesting if I could connect this to my github in the web app and claude automatically has access to my code repositories.

From the link:

> To help developers start exploring, we’re sharing pre-built MCP servers for popular enterprise systems like Google Drive, Slack, GitHub, Git, Postgres, and Puppeteer.

Re: Model Context Protocol

#34

Earlier quoted context omitted.

Are there any resources for building the LLM side of MCP so we can use the servers with our own integration? Is there a specific schema for exposing MCP information to tool or computer use?

Both Python and Typescript SDK can be used to build a client. https://github.com/modelcontextprotocol/typescript-sdk/tree/... and https://github.com/modelcontextprotocol/python-sdk/tree/main... . The TypeScript client is widely used, while the Python side is more experimental. In addition, I recommend looking at the specification documentation at https://spec.modelcontextprotocol.io . This should give you a good over…

Thanks! Do Anthropic models get extra training/RLHF/fine-tuning for MCP use or is it an extension of tool use?

Re: Model Context Protocol

#35
post #33

Hmm I like the idea of providing a unified interface to all LLMs to interact with outside data. But I don't really understand why this is local only. It would be a lot more interesting if I could connect this to my github in the web app and claude automatically has access to my code repositories. I guess I can do this for my local file system now? I also wonder if I build an LLM powered app, and currently simply to R…

> It would be a lot more interesting if I could connect this to my github in the web app and claude automatically has access to my code repositories. From the link: > To help developers start exploring, we’re sharing pre-built MCP servers for popular enterprise systems like Google Drive, Slack, GitHub, Git, Postgres, and Puppeteer.

Yes but you need to run those servers locally on your own machine. And use the desktop client. That just seems... weird?

I guess the reason for this local focus is, that it's otherwise hard to provide access to local files. Which is a decently large use-case.

Still it feels a bit complicated to me.

Re: Model Context Protocol

#37
I don't understand the value of this abstraction.

I can see the value of something like DSPy where there is some higher level abstractions in wiring together a system of llms.

But this seems like an abstraction that doesn't really offer much besides "function calling but you use our python code".

I see the value of language server protocol but I don't see the mapping to this piece of code.

That's actually negative value if you are integrating into an existing software system or just you know... exposing functions that you've defined vs remapping functions you've defined into this intermediate abstraction.

Re: Model Context Protocol

#40

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

Is it at least somewhat in sync with plans from Microsoft , OpenAI and Meta? And is it compatible with the current tool use API and computer use API that you’ve released?

From what I’ve seen, OpenAI attempted to solve the problem by partnering with an existing company that API-fys everything. This feels looks a more viable approach, if compared to effectively starting from scratch.

Post reply on HN