You can use MCP with Sourcegraph's Cody as well
https://sourcegraph.com/blog/cody-supports-anthropic-model-c...
Model Context Protocol
21–30 of 283 posts
Re: Model Context Protocol
#22@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.
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 overview of how to implement a client. If you are looking to see an implemented open source client, Zed implements an MCP client: https://github.com/zed-industries/zed/tree/main/crates/conte...
If you have specific questions, please feel free to start a discussion on the respective https://github.com/modelcontextprotocol discussion, and we are happy to help you with integrating MCP.
Re: Model Context Protocol
#23@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.
Do you have a roadmap for the future of the protocol?
Is it versioned? ie. does this release constitute an immutable protocol for the time being?
Re: Model Context Protocol
#24I’m glad they're pushing for standards here, literally everyone has been writing their own integrations and the level of fragmentation (as they also mention) and repetition going into building the infra around agents is super high. We’re building an in terminal coding agent and our next step was to connect to external services like sentry and github where we would also be making a bespoke integration or using a close…
I've been implementing a lot of this exact stuff over the past month, and couldn't agree more. And they even typed the python SDK -- with pydantic!! An exciting day to be an LLM dev, that's for sure. Will be immediately switching all my stuff to this (assuming it's easy to use without their starlette `server` component...)
Re: Model Context Protocol
#25@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.
Do you have a roadmap for the future of the protocol? Is it versioned? ie. does this release constitute an immutable protocol for the time being?
Followup: is this a protocol yet, or just a set of libraries? This page is empty: https://spec.modelcontextprotocol.io/
Re: Model Context Protocol
#26Earlier quoted context omitted.
Do you have a roadmap for the future of the protocol? Is it versioned? ie. does this release constitute an immutable protocol for the time being?
Followup: is this a protocol yet, or just a set of libraries? This page is empty: https://spec.modelcontextprotocol.io/
Sorry, I think that's just the nav on those docs being confusing (particularly on mobile). You can see the spec here: https://spec.modelcontextprotocol.io/specification/
Re: Model Context Protocol
#27@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.
Do you have a roadmap for the future of the protocol? Is it versioned? ie. does this release constitute an immutable protocol for the time being?
You can read how we're implementing versioning here: https://spec.modelcontextprotocol.io/specification/basic/ver...
It's not exactly immutable, but any backwards incompatible changes would require a version bump.
We don't have a roadmap in one particular place, but we'll be populating GitHub Issues, etc. with all the stuff we want to get to! We want to develop this in the open, with the community.
Re: Model Context Protocol
#28i 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.
Re: Model Context Protocol
#29i am curious: why this instead of feeding your LLM an OpenAPI spec?
I think OpenAI spec function calls are to this like what raw bytes are to unix file descriptors
Re: Model Context Protocol
#30i am curious: why this instead of feeding your LLM an OpenAPI spec?
Same reason in Emacs we use lsp-mode and eglot these days instead of ad-hoc flymake and comint integrations. Plug and play.