Is this similar to what Sourcegraph's OpenCtx tries to do?
Has OpenCtx ever gained much traction?
Model Context Protocol
191–200 of 283 posts
Re: Model Context Protocol
#192Is this similar to what Sourcegraph's OpenCtx tries to do? Has OpenCtx ever gained much traction?
Yeah, we’re using it a lot at Sourcegraph. There are some extra APIs it offers beyond what MCP offers, such as annotations (as you can see on the homepage of https://openctx.org). We worked with Anthropic on MCP because this kind of layer benefits everyone, and we’ve already shipped interoperability.
Re: Model Context Protocol
#193Earlier quoted context omitted.
Thank you. That’s good feedback. The gist of it is: you have an llm application such as Claude desktop. You want to have it interact (read or write) with some system you have. MCP solves this. For example you can give the application the database schema as a “resource”, effectively saying; here is a bunch of text, do whatever you want with it during my chat with the llm. Or you can give the application a tool such as…
Or, in short: it's (an attempt to create) a standard protocol to plug tools to LLM app via the good ol' tools/function calling mechanism. It's not introducing new capabilities, just solving the NxM problem, hopefully leading to more tools being written. (At least that's how I understand this. Am I far off?)
We definitely hope this will solve the NxM problem.
On tools specifically, we went back and forth about whether the other primitives of MCP ultimately just reduce to tool use, but ultimately concluded that separate concepts of "prompts" and "resources" are extremely useful to express different _intentions_ for server functionality. They all have a part to play!
Re: Model Context Protocol
#194@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.
The result that MCP server returned will be transfer to MCP host(Claude, IDEs, Tools), there are some privacy issues because the process is automatic after one-time permission provided. For instance, when there is something wrong for MCP host, it query all data from database and transfer it to host, all data will be leaked. It's hard to totally prevent this kind of problem when interacting with local data, But, Is th…
Your concerns are very valid. This is partly why right now, in Claude Desktop, it's not possible to grant permission permanently. The most you can do is "Allow for this chat," which applies to one tool from one server at a time.
Re: Model Context Protocol
#195Is there any plans to add Well-known URI[1] as a standard? It would be awesome if we can add services just by inputting domain names of the services.
Re: Model Context Protocol
#196Earlier quoted context omitted.
Already available in the latest at https://claude.ai/download !
I'm on the latest Claude desktop for mac (0.7.1, pro plan). Can't see the mcp icon neither in the app nor in the web. How to troubleshoot?
There's a debugging guide here that may be helpful: https://modelcontextprotocol.io/docs/tools/debugging
Re: Model Context Protocol
#197Earlier quoted context omitted.
I'm on the latest Claude desktop for mac (0.7.1, pro plan). Can't see the mcp icon neither in the app nor in the web. How to troubleshoot?
Same issue here. Is it geolocked maybe?
Definitely not geolocked! Please try the debugging guide here: https://modelcontextprotocol.io/docs/tools/debugging
Re: Model Context Protocol
#198Earlier quoted context omitted.
> This is huge, as long as there's a single standard and other LLM providers don't try to release their own protocol Yes, very much this; I'm mildly worried because the competition in this space is huge and there is no shortage of money and crazy people who could go against this.
They will go against this. I don’t want to be that guy, but this moment in time is literally the opening scene of a movie where everyone agrees to work together in the bandit group. But, it’s a bandit group.
Not necessarily. There’s huge demand to simplify the integration process between frontier models and consumers. If specs like this wind up saving companies weeks or months of developer time, then the MCP-compatible models are going to win over the more complex alternatives. This unlocks value for the community, and therefore the AI companies
Re: Model Context Protocol
#199Is there any plans to add Well-known URI[1] as a standard? It would be awesome if we can add services just by inputting domain names of the services. [1]: https://en.wikipedia.org/wiki/Well-known_URI
We're still in the process of thinking through and fleshing out full details for remote MCP connections. This is definitely a good idea to include in the mix!
Re: Model Context Protocol
#200I 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...
It would appear the HN hug knocked your host offline, given the 525 TLS Is Bogus and its 502 Bad Gateway friend I managed to get it to load: https://archive.ph/7DALF
It's actually due to fly.io outage https://news.ycombinator.com/item?id=42241851