11 ms·
New MCP Roadmap
- svyatoslavpavl 25d ago[flagged]
- hnub7akvk6 25d ago[flagged]
- skinfaxi 25d ago> We’re starting a progressive discovery effort so a server can offer a small entry point and reveal more of its catalog as the conversation narrows. Kind of late to the party. I've had to implement lazy loading of mcps in a couple of harnesses now but am moving to implement everything as code mode instead.
- rixed 25d agoWhat do you mean "as code mode"?
- skinfaxi 25d agoBasically https://blog.cloudflare.com/code-mode/ https://blog.cloudflare.com/code-mode/ I was getting fed up with AWS mcp telling me it is eol.
- rixed 25d agoInteresting, thank you. Are you aware of any quantitative data to back up the claim that llms are more performant in code mode than mcp mode? Not that i doubt it, but I'm curious about how big of a difference it can make.
- wilj 25d ago+1 for code mode. It's a game changer for runtime performance, flexibility of orchestrating lots of tool calls with complex logic, and all sorts of other goodies. I'm in the process of switching all my personal stuff to a self-hosted fork of cloudflare-os right now. It's taking a lot of rearchitecting how my stuff works to fit within the cloudflare "no local files" paradigm, but for now I've got a container gatekeeper they can drive and they can check repos out in it.
- debarshri 25d agoThis reminds me of the actor model[1] [1] https://doc.akka.io/libraries/akka-core/current/typed/actors.html https://doc.akka.io/libraries/akka-core/current/typed/actors...
- izend 25d agoI am very curious how many MCP servers will actually implement all of this: "MCP authorization today is built around a person approving access in a browser. That works well for interactive clients, but more and more of the callers are agents running as cloud workloads with their own identity, acting on behalf of a user who isn’t present, or delegating narrower authority to sub-agents. We want MCP servers to have a standardized way to recognize and trust those agent identities, built on existing standards rather than pasted API keys and long-lived tokens. The work here covers finalizing Demonstrating Proof of Possession (DPoP) and driving its adoption, and defining an opinionated path for agent identity and delegation through Workload Identity Federation, the ID-JAG grant behind Enterprise-Managed Authorization, and standard token exchange. We will also continue to grow our engagement with the OAuth standards bodies, including the IETF OAuth and WIMSE working groups, to help the underlying standards evolve with the building blocks that agent identity needs."
- bandofthehawk 25d agoEven now, the mcp server itself doesn't have to implement all of the possible security options. You can use something like agentgateway to act as an auth proxy for your mcp servers.
- alasano 25d agoHopefully quite a few. I really love the idea of fully enabled agents and being able to cut down on human in the loop moments. Things like https://projects.dev/ https://projects.dev/ for example. A ton of security problems and others to solve but it's still where I want the future of all this to go.
- huksley 25d agoSuch an example of overengineering, why not just use OAuth?
- brookst 25d agoOauth assumes interactivity
- rco8786 25d ago> With the 2026-07-28 release, a remote MCP server is now no different from any other HTTP workload Good. Introducing a bespoke new protocol was one of the more bone-headed things MCP did on initial release.
- Jhater 25d ago[dead]
- colingauvin 25d agoIt's unreal how bad the initial rollout was between HTTP/streaming and stdio, bearer auth and OAuth. Virtually every client/MCP server pair had a different portion of that matrix implemented.
- ihuman 25d agoIs stdio being deprecated? I couldn't tell from this page
- amluto 25d agoThe prose on the page is very unclear. My best interpretation is that they want to continue supporting stdio but that they don’t want it to be its own special protocol. The obvious way to do that would be to speak ordinary HTTP (version 1.1? 2?) over stdio and to use the MCP-over-HTTP protocol over the resulting HTTP transport. This would be more complex to implement for a simple server, but it’s not exactly difficult.
- Gormo 25d agoNot everyone is on board with the idea of HTTP being the exclusive universal IPC bus.
- intrasight 25d agoCount me as not on board
- LowTechHN 25d ago[flagged]
- willio58 25d agoSo I’ve been working on a personal finance app, and I added an MCP to it. Connected my Claude to it, mainly for testing purposes. The other day I was heading to Home Depot to buy some gardening stuff and I was asking some some questions around what I could plant at this time and still harvest before winter. It answers me, then brings up how my home improvement budget is nearing its limit for the month. I then ask it how I’m doing on my wider retirement plan and it mentions I’m a few thousand dollars ahead of schedule for the plan. So I decided it’s okay to go over budget on that category this month. This type of emergent behavior of agents you work with having more context about you, it’s very useful in ways I didn’t expect.
- nozzlegear 25d agoIs that really much different from building an API for your app though? Claude can use those just as easily.
- dcrazy 25d agoMCP is essentially just a convention for APIs that standardizes the concept of a “resource”. It spares the LLM a lot of work figuring out what the “things” are in a problem domain, and how various endpoints relate to those “things”.
- rolisz 25d agoWith authentication and on mobile? I agree that on desktop it's not particularly relevant. Or through openclaw. But for most people who use it through mobile, MCP solves some problems.
- nozzlegear 25d ago> With authentication and on mobile? It's been a long time since I've used Claude, but is it not able to just use curl and an API key that it keeps in its "memory" on mobile? Or can it only use curl on the desktop?
- jdw64 25d agoSometimes I really respect senior developers. When specs change, you obviously have to update existing work too. Looking at this MCP change, it seems like it's becoming stateless—I'm already wondering how to adapt. Senior programmers always advised me to only use things that have been around for at least three years. Now I finally understand why.
- chrisweekly 25d ago> "only use things that have been around for at least three years" Yikes. I can understand the desire to mitigate churn, but following this advice would be career suicide. Trying new things is essential.
- beepbooptheory 25d agoJust curious, what kind of work have you done where this conceit feels valid in your mind? My career, at least, feels like an exception to this, but I guess its conceivable to me that it could be otherwise. You have had a lot managers push newer frameworks/technologies on you? Is this more VC startup land, or something else? Maybe I'm old, but at least in web dev it doesn't feel that long ago that someone had to argue for, e.g., Vite over webpack, Svelte over React, etc..
- chrisweekly 23d agoWhat kind of work have I done? All kinds of webdev and SWE-adjacent roles since the late 90s. Startups, scale-ups, SMBs, huge enterprises. FT and contract / consulting roles (w/ titles containing words like "Principal", "Architect", "Director" and "VP"). In a world where everyone followed rigid advice to stick to 3yo+ tech, Vite wouldn't exist, let alone have people to argue for it. Nor would the web, for that matter. I'm _not_ saying "chase the new-and-shiny for its own sake", and I don't recommend introducing immature or untested dependencies in production. But it's essential to learn how to gauge the quality of a mature solution -- and IME the only way to do that is to have something to compare it to (ideally, something newer and better). Develop an instinct for separating the signal from the (considerable) noise by trying things. Newer isn't always better, but the arc does trend towards improvement. Dev tooling is rife with examples, and a great place to start. As for "You have had a lot managers push newer frameworks/technologies on you?" On the contrary -- I've had managers wedded to outdated cruft that threatened to drag the whole enterprise down. Resistance to change is sometimes fear masquerading as wisdom. Finally, note this whole thread is in the context of an update to the MCP spec. In the world of AI, 3 years might as well be 3 centuries.
- hnrprtlpdb 25d agoHalf the battle is just knowing this exists
- huksley 25d agoIn v.1 making MCP stateful was such a deployment-unfriendly way to do it - you need a complicated persistence layer for it to work. All while it is just a fancy way make your OpenSchema PAI visible to AI.
- mikeegg1 25d agoWhen I see "MCP" I still translate that to Master Control Program.
- dingaling911 25d agoAnd here I thought I was old.
- cube00 25d agoI still struggle to see how a MCP endpoint is easier for agents to work with compared with a REST endpoint and a skills.md file.
- hyveops 11d ago[flagged]
- peterlk 25d agoYep. I’ve found that having an endpoint that serves a well, documented openapi.yaml is very effective for agentic usage. The biggest difference is that you can break down a REST API into RPC-like chunks and save on some tokens if you break up the tools well. But pragmatically, I think saying “tell your agent to hit /api/v3/openapi.yaml” is quite useful
- ulrikrasmussen 25d agoWe did a prototype to integrate an agent into our application and basically just gave it a tool to discover the OpenAPI spec and call endpoints. It worked surprisingly well! One caveat was that some responses were too big and would poison the context, but then I gave the agent a GraalJS engine and allowed it to save responses and post-process them using JS. For the little amount of work required this gives the agent a lot of power without having to give it full CLI and without having to create bespoke tools.
- pianopatrick 25d agoor a CLI
- cjg007 25d ago[dead]
- mmaunder 25d agoMy dream was for MCP to allow services like ours (cybersecurity) to provide a self documenting endpoint with authentication, and we just give users a URL and it just frikkin works. Instead from day 1 it’s been multiple standards as they pivoted, a context hungry feature, and feels like a kludge. That burned the idea of MCP for me and I’ve had such success with local tools and APIs that it’ll take a lot for me to go back.
- brap 25d agoI mean… so just HTTP + OpenAPI spec?
- mmaunder 25d agoIt actually doesn’t matter. Pick your favorite way of giving a dev access to capability on a remote server.
- dmix 25d agoPlus You're likely building an API already if you have an MCP. Not everyone using MCP is a dev, we have random corporate workers using our MCP. They don't know what an API is but they can add a plugin from an agent marketplace (which can also contain skills) and MCP is a bit narrower with a clear authorization system, tool discovery, and annotations (agents ask "confirm you want you want to write this"). Just give your end-users flexible options. If they have Claude Code then build more around the API side if needed.
- firatsarlar 25d agoTruth doesn't move much. It moves slowly, so that those holding onto it don't fall. Keep up.
- simianwords 25d agoIs there a way in MCP where I can "approve" certain privileged actions? Like imagine an MCP for buying stuff in Amazon but it can do everything including payment but is behind a gate that the human needs to approve
- somnium_sn 25d agoYes use MCP elicitations
- entity002 20d ago[flagged]
- luciana1u 25d ago[flagged]
- vkaku 25d agoI think MCP is jumping some sharks here. Nobody needs to have every functionality of HTTP offloaded to MCP at all, at this point. I'll stick to the bare minimum that works.
- sjeno 25d agoAgree 100%, the elegance of JSON-RPC is a virtue.
- madmecodes 25d ago[flagged]
- usxr1515 25d ago[flagged]
- rglover 25d agoThe degree to which this idea has been overcomplicated is confusing. This could have been solved with some relatively simple patterns wrapped around HTTP and WebSockets (and if absolutely necessary, SSE).
- castroneto 25d ago[flagged]
- vatsachak 25d agoWhy not just give the model a prompt? Every gain in LLMs is either through increases in compute efficiency, Architecture or Harnesses... The rest seems like bells and whistles
- threecheese 25d agoI wish the “sampling” feature - which is being removed - had found more use. BYO Inference could be really useful in a walled garden like Claude Code, where you are unable to leverage inference outside of that garden without paying per token. Maybe that feature was just more interesting than it was useful.
- kevinbaiv 25d ago[dead]
- youre-wrong3 25d agoPeople seem to ignore the fact that with MCP you can serve up the tools the user wants and has access to instead of a rest api doc specifying every endpoint and bloating the context.
- gf000 25d agoAll those tools still get into context. Also, it's not hard to filter a rest api doc - like with a special tool for that the harness itself could pre-filter it and add only the relevant ones as tools to be even more leaner than what an MCP returns.
- hobofan 24d ago> All those tools still get into context. 100% up to the harness. Most harnesses either fixed (or dymanically depending on size) nowadays add a "search_tool" tool to prevent spamming the context with all tools.
- felixlu2026 25d ago[dead]
- bhavikagarwal20 25d agosupport for media is really needed in mcp now
- futurist_hp 25d ago[flagged]
- mendidou 24d ago[dead]
- DarmokTanagra 24d agoThe entire premise of MCP is misguided and completely counter to the core value proposition of ai agents. Its insane to me how quickly people flocked to the idea of building a parallel web to maintain for non humans. I shouldnt be surprised seeing how low priority human accessibility and ux has been on the web when compared to the needs of the all consuming parasite that is ad tech.
- edgyquant 24d agoMCP is at its simplest just a way to describe what the different api endpoints do to an llm and we need some protocol for this. MCP works and is a fine protocol for this
- ricardobeat 24d agoIt was actually a welcome change for 'web access'. There were very few open APIs left, MCP forced everyone to actually build public APIs again.
- qingcharles 24d agoThis. It's amazing how long humans have screamed for good APIs, cheaply accessible for lots of web sites and all we got were crickets. LLMs come along and the same sites are falling over themselves to build extensive APIs. It's the golden age of APIs finally.
- paidx 24d ago[flagged]
- macrolime 24d agoI've tried many MCPs, but have yet to find any that are actually useful. It seems it's generally better to just have the agent run CLI commands and maybe use some skills. From what I can find, MCPs are nothing but bloat. Is anyone aware of any truly useful MCPs that doesn't work better and less bloaty by skipping the MCP part?
- sajithdilshan 24d agoDepends on what tool you use. As an example for github gh is way more efficient than using the github MCP because the training data of LLM actually contains gh documentation and how to use it. However, if you have a very niche command tool or a work related internal tool, LLM has no idea on how to use it and it could waste a lot of tokens by trying to figure out what works and what doesn't and how to use it in every session. That's where MCP comes in handy. LLMs are trained to use the MCP protocol and it can efficiently figure out which tool to be called and how to process the output when a niche command tool is exposed via an MCP.
- manganate06 24d ago[flagged]
- 1saadcodes 24d agoI like that this roadmap spends so much time on things like HTTP, auth, result formats and SDKs. It's a nice step up from the rough initial release and will just make the overall experience building it easier
- ventrovadev 24d ago[flagged]
- xducn1 24d ago[flagged]
- tercelyi 23d ago[flagged]
- beyondscale-yes 21d ago[dead]
- tickerlayer 20d ago[dead]
- placeroot 18d ago[dead]