[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-7-mcp-changes-for-agent-builders-en":3,"article-related-7-mcp-changes-for-agent-builders-en":34,"series-industry-5c6043b6-c003-4f22-8538-07b553e47269":86},{"id":4,"slug":5,"title":6,"content":7,"summary":8,"source":9,"source_url":10,"author":11,"image_url":12,"cover_image":12,"category":13,"language":14,"translated_content":11,"related_article_id":15,"keywords":16,"key_takeaways":26,"views":30,"created_at":31,"published_at":32,"topic_cluster_id":33},"5c6043b6-c003-4f22-8538-07b553e47269","7-mcp-changes-for-agent-builders-en","7 MCP changes for agent builders","\u003Cp data-speakable=\"summary\">This release candidate makes \u003Ca href=\"\u002Ftag\u002Fmcp\">MCP\u003C\u002Fa> easier to run, inspect, secure, and extend for \u003Ca href=\"\u002Ftag\u002Fagent\">agent\u003C\u002Fa> builders.\u003C\u002Fp>\n\u003Cp>The 2026-07-28 MCP release candidate adds clearer state, tighter auth, and more structured extensions, giving teams a better base for agentic systems.\u003C\u002Fp>\n\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Item\u003C\u002Fth>\u003Cth>What changed\u003C\u002Fth>\u003Cth>Why it matters\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>Stateless protocol\u003C\u002Ftd>\u003Ctd>Request carries version, client info, capabilities\u003C\u002Ftd>\u003Ctd>Better routing and scaling\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Explicit state handles\u003C\u002Ftd>\u003Ctd>Handles like basket_id move into tool outputs\u003C\u002Ftd>\u003Ctd>More visible workflow state\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Extensions\u003C\u002Ftd>\u003Ctd>Reverse-DNS IDs, versioned repos, negotiation\u003C\u002Ftd>\u003Ctd>Cleaner feature growth\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Tasks\u003C\u002Ftd>\u003Ctd>task\u002Fget, task\u002Fupdate, task\u002Fcancel\u003C\u002Ftd>\u003Ctd>Long jobs fit the protocol\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Auth updates\u003C\u002Ftd>\u003Ctd>Sharper OAuth\u002FOIDC rules\u003C\u002Ftd>\u003Ctd>Safer multi-server deployments\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>JSON Schema 2020-12\u003C\u002Ftd>\u003Ctd>Composition, conditionals, references\u003C\u002Ftd>\u003Ctd>More accurate tool contracts\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Governance policy\u003C\u002Ftd>\u003Ctd>Active, Deprecated, Removed states\u003C\u002Ftd>\u003Ctd>Less churn, clearer upgrades\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003Ch2>1. Stateless protocol requests\u003C\u002Fh2>\n\u003Cp>MCP is moving the protocol layer toward stateless requests, which makes it easier to run behind load balancers, gateways, and rate limiters. Instead of depending on a session that has to be preserved across calls, a request can carry the information the server needs right away.\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780093088363-9ms0.png\" alt=\"7 MCP changes for agent builders\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\n\u003Cp>That shift matters because it makes MCP behave more like ordinary HTTP services. Teams can route, scale, and debug remote servers without special session plumbing getting in the way. The release candidate even uses headers such as \u003Ccode>Mcp-Method\u003C\u002Fcode> and \u003Ccode>Mcp-Name\u003C\u002Fcode> so infrastructure can make routing decisions without inspecting the body.\u003C\u002Fp>\n\u003Cul>\u003Cli>Self-contained calls such as \u003Ccode>tools\u002Fcall\u003C\u002Fcode>\u003C\u002Fli>\u003Cli>No sticky-session requirement at the protocol layer\u003C\u002Fli>\u003Cli>Better fit for distributed infrastructure\u003C\u002Fli>\u003C\u002Ful>\n\u003Ch2>2. Explicit state handles\u003C\u002Fh2>\n\u003Cp>Stateless protocol design does not remove application state, it just moves it into a place the agent can see. A tool can return a handle, such as \u003Ccode>basket_id\u003C\u002Fcode> or \u003Ccode>browser_id\u003C\u002Fcode>, and later calls can reuse that value directly.\u003C\u002Fp>\n\u003Cp>That makes workflows easier to reason about because the model can carry the handle from step to step instead of relying on hidden session metadata. It also improves logging and orchestration, since the client and server can record the same visible identifier across the whole flow.\u003C\u002Fp>\n\u003Cul>\u003Cli>Visible identifiers like \u003Ccode>basket_id\u003C\u002Fcode>\u003C\u002Fli>\u003Cli>Tool outputs can feed later tool calls\u003C\u002Fli>\u003Cli>Handles still need scoping, validation, and expiry\u003C\u002Fli>\u003C\u002Ful>\n\u003Ch2>3. Structured extensions\u003C\u002Fh2>\n\u003Cp>Extensions now have a more formal home in MCP, with reverse-DNS identifiers, versioned extension repositories, delegated maintainers, and capability negotiation. That gives implementers a cleaner path for features that are useful, but not ready to sit in the core spec forever.\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780093079284-8jop.png\" alt=\"7 MCP changes for agent builders\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\n\u003Cp>The \u003Ca href=\"\u002Fnews\u002Fkubernetes-cncf-project-page-en\">first big\u003C\u002Fa> examples are MCP Apps and Tasks. MCP Apps can ship interactive HTML that hosts render in sandboxed iframes, while Tasks lets servers turn long-running work into handles that clients can query, update, or cancel later.\u003C\u002Fp>\n\u003Cul>\u003Cli>Extension IDs use reverse-DNS naming\u003C\u002Fli>\u003Cli>Clients and servers advertise support through capability maps\u003C\u002Fli>\u003Cli>Tasks supports \u003Ccode>tasks\u002Fget\u003C\u002Fcode>, \u003Ccode>tasks\u002Fupdate\u003C\u002Fcode>, and \u003Ccode>tasks\u002Fcancel\u003C\u002Fcode>\u003C\u002Fli>\u003C\u002Ful>\n\u003Ch2>4. Deprecations with a policy\u003C\u002Fh2>\n\u003Cp>Roots, Sampling, and Logging are deprecated under the new feature lifecycle policy, which is a strong signal about where MCP wants to focus. The spec is narrowing its scope to the client-server contract and leaving adjacent concerns to systems that already handle them well.\u003C\u002Fp>\n\u003Cp>That means workspace boundaries can often move into tool inputs, resource URIs, or server config, while observability can go to stderr or OpenTelemetry. The deprecations are annotation-only for now, and removal needs a separate SEP, so teams get time to adapt instead of being forced into a fast rewrite.\u003C\u002Fp>\n\u003Cul>\u003Cli>Roots shifts toward tool parameters or resource URIs\u003C\u002Fli>\u003Cli>Sampling shifts toward provider APIs\u003C\u002Fli>\u003Cli>Logging shifts toward stderr and OpenTelemetry\u003C\u002Fli>\u003C\u002Ful>\n\u003Ch2>5. Stronger authorization rules\u003C\u002Fh2>\n\u003Cp>The release candidate tightens OAuth and OpenID Connect details for the common case where one client talks to many MCP servers. That includes clearer rules for issuer validation, credential binding, localhost redirect support, and how desktop or CLI clients should register.\u003C\u002Fp>\n\u003Cp>These changes sound small, but they help prevent confusing failures and unsafe auth behavior in real deployments. For agent systems that touch private data, paid services, or user-specific workflows, clearer authorization is not optional housekeeping, it is part of the product.\u003C\u002Fp>\n\u003Ccode>Client -> Authorization Server -> MCP Server\nvalidate issuer\nbind credentials to issuing server\nsupport localhost redirects for desktop and CLI apps\u003C\u002Fcode>\n\u003Ch2>6. Full JSON Schema support\u003C\u002Fh2>\n\u003Cp>MCP tool schemas now support full JSON Schema 2020-12, which makes tool contracts more accurate. Inputs still require an object root, but authors can use composition, conditionals, and references to describe real-world shapes more precisely.\u003C\u002Fp>\n\u003Cp>That helps when a tool has optional paths, conditional fields, or outputs that do not fit neatly into one static object. The spec also warns implementers not to follow external references blindly and to limit validation work, which is the right caution for a more expressive schema system.\u003C\u002Fp>\n\u003Cul>\u003Cli>Composition and conditionals are allowed\u003C\u002Fli>\u003Cli>Output schemas are unrestricted\u003C\u002Fli>\u003Cli>Validation needs guardrails for performance and safety\u003C\u002Fli>\u003C\u002Ful>\n\u003Ch2>7. Governance that can absorb change\u003C\u002Fh2>\n\u003Cp>The release candidate adds governance pieces that make future changes easier to manage. The feature lifecycle policy defines Active, Deprecated, and Removed states, with at least 12 months between deprecation and the earliest removal.\u003C\u002Fp>\n\u003Cp>It also asks Standards Track SEPs to have matching scenarios in the conformance suite before Final status. That gives SDKs, servers, and clients a shared target, which reduces interpretation drift and keeps the spec more usable as it grows.\u003C\u002Fp>\n\u003Ch2>What to pick\u003C\u002Fh2>\n\u003Cp>If you run MCP infrastructure, start with the stateless protocol changes and the auth updates. If you build tools or agent workflows, focus on explicit state handles, Tasks, and JSON Schema support. If you maintain a platform or SDK, the extension framework and governance policy are the parts that will shape your roadmap.\u003C\u002Fp>\n\u003Cp>For most teams, the best next step is to treat this release candidate as a prompt to simplify hidden state, tighten authorization, and move long-running or optional features into explicit extensions.\u003C\u002Fp>","7 MCP updates make agent systems easier to run, inspect, secure, and extend, with the 2026-07-28 release candidate leading the way.","aaif.io","https:\u002F\u002Faaif.io\u002Fblog\u002Fmcp-is-growing-up\u002F",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780093088363-9ms0.png","industry","en","9c5dcb37-b70e-40dd-8ec3-8f557005de77",[17,18,19,20,21,22,23,24,25],"MCP","Model Context Protocol","agentic AI","extensions","OAuth","OpenID Connect","JSON Schema","Tasks","stateless protocol",[27,28,29],"MCP is shifting state out of the protocol and into explicit handles that agents can reason about.","Extensions and Tasks now have a clearer lifecycle, which makes new capabilities easier to ship safely.","Authorization, schema validation, and governance are getting stricter so MCP can scale across real deployments.",2,"2026-05-29T22:17:36.144591+00:00","2026-05-29T22:17:36.137+00:00","ce87db71-c19b-4734-b1f6-4a9eebe5de85",{"tags":35,"relatedLang":45,"relatedPosts":49},[36,38,39,41,43],{"name":21,"slug":37},"oauth",{"name":20,"slug":20},{"name":18,"slug":40},"model-context-protocol",{"name":17,"slug":42},"mcp",{"name":19,"slug":44},"agentic-ai",{"id":15,"slug":46,"title":47,"language":48},"7-mcp-changes-for-agent-builders-zh","7 個 MCP 變更，幫助代理建構者上手","zh",[50,56,62,68,74,80],{"id":51,"slug":52,"title":53,"cover_image":54,"image_url":54,"created_at":55,"category":13},"72823fc3-fb0c-41fa-ba83-83eb7cc3880b","openai-should-not-rush-its-ipo-en","OpenAI should not rush its IPO just to win the AI race","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781053364904-2rcp.png","2026-06-10T01:02:20.320813+00:00",{"id":57,"slug":58,"title":59,"cover_image":60,"image_url":60,"created_at":61,"category":13},"73c81054-d5b7-4fb9-8487-c93d603ff85b","openai-europe-privacy-policy-en","OpenAI updates its Europe privacy policy","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781052478315-n5wv.png","2026-06-10T00:47:31.644415+00:00",{"id":63,"slug":64,"title":65,"cover_image":66,"image_url":66,"created_at":67,"category":13},"60f9f257-29a3-42fc-94a0-e781cae297a0","openai-ads-sensitive-chats-policy-en","OpenAI is right to keep ads out of sensitive chats","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781051570830-gx73.png","2026-06-10T00:32:23.894911+00:00",{"id":69,"slug":70,"title":71,"cover_image":72,"image_url":72,"created_at":73,"category":13},"4410b717-f1b6-4a96-854b-60dd47cc933e","ai-bootlegs-streaming-royalties-stick-figure-en","AI bootlegs are already draining streaming royalties","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781050678990-9idm.png","2026-06-10T00:17:31.471242+00:00",{"id":75,"slug":76,"title":77,"cover_image":78,"image_url":78,"created_at":79,"category":13},"317dc8b9-9ab1-4d29-8741-a50d795f7727","amd-microsoft-windows-ml-acceleration-en","AMD and Microsoft push Windows ML on GPU and NPU","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781047979576-a01a.png","2026-06-09T23:32:31.891479+00:00",{"id":81,"slug":82,"title":83,"cover_image":84,"image_url":84,"created_at":85,"category":13},"47702da7-3093-408a-90aa-9f5f461ccce9","openai-ipo-filing-turns-hype-into-scrutiny-en","OpenAI’s IPO filing turns hype into scrutiny","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781042611120-ynji.png","2026-06-09T22:03:05.09084+00:00",[87,92,97,102,107,112,117,122,127,132],{"id":88,"slug":89,"title":90,"created_at":91},"d35a1bd9-e709-412e-a2df-392df1dc572a","ai-impact-2026-developments-market-en","AI's Impact in 2026: Key Developments and Market Shifts","2026-03-25T16:20:33.205823+00:00",{"id":93,"slug":94,"title":95,"created_at":96},"5ed27921-5fd6-492e-8c59-78393bf37710","trumps-ai-legislative-framework-en","Trump's AI Legislative Framework: What's Inside?","2026-03-25T16:22:20.005325+00:00",{"id":98,"slug":99,"title":100,"created_at":101},"e454a642-f03c-4794-b185-5f651aebbaca","nvidia-gtc-2026-key-highlights-innovations-en","NVIDIA GTC 2026: Key Highlights and Innovations","2026-03-25T16:22:47.882615+00:00",{"id":103,"slug":104,"title":105,"created_at":106},"0ebb5b16-774a-4922-945d-5f2ce1df5a6d","claude-usage-diversifies-learning-curves-en","Claude Usage Diversifies, Learning Curves Emerge","2026-03-25T16:25:50.770376+00:00",{"id":108,"slug":109,"title":110,"created_at":111},"69934e86-2fc5-4280-8223-7b917a48ace8","openclaw-ai-commoditization-concerns-en","OpenClaw's Rise Raises Concerns of AI Model Commoditization","2026-03-25T16:26:30.582047+00:00",{"id":113,"slug":114,"title":115,"created_at":116},"b4b2575b-2ac8-46b2-b90e-ab1d7c060797","google-gemini-ai-rollout-2026-en","Google's Gemini AI Rollout Extended to 2026","2026-03-25T16:28:14.808842+00:00",{"id":118,"slug":119,"title":120,"created_at":121},"6e18bc65-42ae-4ad0-b564-67d7f66b979e","meta-llama4-fabricated-results-scandal-en","Meta's Llama 4 Scandal: Fabricated AI Test Results Unveiled","2026-03-25T16:29:15.482836+00:00",{"id":123,"slug":124,"title":125,"created_at":126},"bf888e9d-08be-4f47-996c-7b24b5ab3500","accenture-mistral-ai-deployment-en","Accenture and Mistral AI Team Up for AI Deployment","2026-03-25T16:31:01.894655+00:00",{"id":128,"slug":129,"title":130,"created_at":131},"5382b536-fad2-49c6-ac85-9eb2bae49f35","mistral-ai-high-stakes-2026-en","Mistral AI: Facing High Stakes in 2026","2026-03-25T16:31:39.941974+00:00",{"id":133,"slug":134,"title":135,"created_at":136},"9da3d2d6-b669-4971-ba1d-17fdb3548ed5","cursors-meteoric-rise-pressures-en","Cursor's Meteoric Rise Faces Industry Pressures","2026-03-25T16:32:21.899217+00:00"]