[felixrieseberg]

Disclosure: I work at Anthropic, have worked on MCP

I also think this is pretty big. I think a problem we collectively have right now is that getting MCP closer to real user flows is pretty hard and requires a lot of handholding. Ideally, most users of MCP wouldn't even know that MCP is a thing - the same way your average user of the web has no idea about DNS/HTTP/WebSockets. They just know that the browser helps them look at puppy pictures, connect with friends, or get some work done.

I think this is a meaningful step in the direction of getting more people who'll never know or care about MCP to get value out of MCP.

[CuriouslyC]

I want to try and understand what you guys see as the win from MCP. It's objectively inferior to code/clis across a ton of dimensions. The main value I see from it is as a single point to "sandbox" what your agents can do, but it seems a little awkward for that use case.

[c-hendricks]

LLMs are used outside of programming though. It's much easier to hook up a HTTP MCP than it is to install and update a CLI on the execs machines.

[bradgessler]

I built https://terminalwire.com around the idea that CLIs are a great way to interact with web applications.

Turns out the approach works well for integrating web apps with LLMs. I have a payroll company using it in their stack to replace MCP and they’re reporting lower token usage and a better end result.

[somnium_sn]

I want to also highlight that this is an optional "extension" to MCP, not a required part of specification. If you are a terminal application, only care about tool calling, etc, you are free to skip this. If you want to enable rich clients, then it might be something to consider implementing.

[pylotlight]

Can you potentially review utcp.io for seeing what MCP should have been to avoid context overloading? The dynamic tool search option and codemode to avoid loading all tools/servers into context seems like a better method imo.

[iLoveOncall]

I wonder how long it'll take you to figure out that you're trying to reinvent deterministic APIs.

[troupo]

Or just APIs in general.

MCP is incredibly vibe-coded. We know how to make APIs. We know how to make two-way communications. And yet "let's invent new terminology that makes little sense and awkward workarounds on top of unidirectional protocols and call it the best thing since sliced cheese".

[stingraycharles]

What is indeterministic about MCP servers? Most of them follow fairly simple rules, eg an MCP server to interact with Slack gives pretty deterministic responses to requests.

Or are you confusing the LLM / MCP client invoking the tools being non-deterministic?

[neoden]

MCP is already deterministic. What's huge about it is that it has automatic API discovery and integration built-in. It's a bit rough yet but I think we will only see how it's getting improved more and more.