somnium_sn

Yes use MCP elicitations

One of my favorite parks and much lesser knows is Westpark in Munich. Similarly built around usage and still unique since it was originally built for a national garden exhibition it features a rich set of small little areas from around the world, a Japanese party, a Chinese part, French areas, English areas. It has outdoor theaters, playgrounds, a lake, a communial area and much more . It’s worth a visit when you are in Munich

Hey I am the one Lead maintainer of the MCP protocol.

I agree and hear you that file uploads are a pain. As the core maintainer group we have deferred the work on this for this release and hope to pick it up soon.

Now is the moment to engage with the respective working group to make your case heard so we can ensure it’s on the roadmap.

It is fine to have corners of the internet that run in a particular way.

My issue however, is that this is changing the rules on people. Codeberg initially was a FLOSS alternative to big company Github. Now it's more narrow, an alternative to Github and only for people who don't want to use AI. What's the next step? This is the problem, you either a platform and be, within legal reasons, agnostic, or you are trying to be a specific community. It is unclear to me if the specific community that Codeberg wants to be today will be the one it wants to be in a year from now, because clearly it's changing.

I cannot rely on a service provider that does change that quickly.

I am still a bit surprised that this is not more widely used. Normal inference + tool calls is effectively composition via serialized natural language, whereas Code Mode / Programmatic Tool Calling is using purpose built languages (aka programming languages) for composition and concurrency. It somewhat feels obvious to me that the latter is way more token and latency efficient.

Little historic sidenote: Zed was the first MCP client next to Claude Desktop

Give the model an interpreter like mlua and let it write code to compose MCP calls together. This is a well established method.

It’s the equivalent to calling CLIs in bash, except mlua is a sandboxes runtime while bash is not.

Give the model a REPL and let it compose MCP calls either by using tool calls structured output, doing string processing or piping it to a fast cheap model to provide structured output.

This is the same as a CLI. Bash is nothing but a programming language and you can do the same approach by giving the model JavaScript and have it call MCP tools and compose them. If you do that you can even throw in composing it with CLis as well

Tools like Claude Code have improved here. They won’t load all tools but instead rely on tool search. Context bloat of MCP servers was a thing if badly written clients but it’s certainly getting better

It has little to do with financing. In addition to the development cost there is now also a membership fee.

What a donation to the Linux foundation offers is ensuring that the trademarks are owned by a neutral entity, that the code for the SDKs and ownership of the organization is now under a neutral entity. For big corporations these are real concerns and that’s what the LF offers.

I appreciate the take. I can certainly see your position.

In my mind what we are doing is building a common place to evolve the pattern. I wouldn’t really call it “standardize”, since in the end in this space adoption matters. (Writing a standard is worth nothing if nobody is using it). I expect MCP apps to evolve and iterate independent from the main spec for a while. You are right, it’s early and premature to say “this is done”. That’s the goal with extensions.

I do believe that I rather have commonalities between a Claude.ai and a ChatGPT as a developer (not sure that’s true if I was mostly looking at it from a product perspective). I also think you will see chat providers iterate on top of it, and mcp apps is more a common core than the full thing one can use on every platform.

All it means that there is a common place and a recommendation that if you care as a client implementor (e.g. postman, chatgpt and others do), there is a spot to look for a generally accepted way of how to do that instead of increasing amount of proprietary extensions on top of MCP.

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.