{"id":495,"date":"2026-08-03T09:00:00","date_gmt":"2026-08-03T00:00:00","guid":{"rendered":"https:\/\/www.theagenticprotocol.com\/?p=495"},"modified":"2026-07-31T14:20:13","modified_gmt":"2026-07-31T05:20:13","slug":"mcp-2026-specification","status":"publish","type":"post","link":"https:\/\/www.theagenticprotocol.com\/index.php\/mcp-2026-specification\/","title":{"rendered":"MCP 2026 Specification: Critical Stateless Migration Guide"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">The MCP 2026 specification is the biggest change to the Model Context Protocol since launch \u2014 and the production migration window is this month. If you&#8217;re running MCP servers against the 2025-11-25 spec, August is when the work of updating them begins in earnest.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/www.theagenticprotocol.com\/wp-content\/uploads\/2026\/07\/grok-image-1a23f597-e09a-4bcd-b82a-8ced4f248276-1024x576.jpg\" alt=\"MCP 2026 specification stateless migration guide August 2026\" class=\"wp-image-496\" srcset=\"https:\/\/www.theagenticprotocol.com\/wp-content\/uploads\/2026\/07\/grok-image-1a23f597-e09a-4bcd-b82a-8ced4f248276-1024x576.jpg 1024w, https:\/\/www.theagenticprotocol.com\/wp-content\/uploads\/2026\/07\/grok-image-1a23f597-e09a-4bcd-b82a-8ced4f248276-300x169.jpg 300w, https:\/\/www.theagenticprotocol.com\/wp-content\/uploads\/2026\/07\/grok-image-1a23f597-e09a-4bcd-b82a-8ced4f248276-768x432.jpg 768w, https:\/\/www.theagenticprotocol.com\/wp-content\/uploads\/2026\/07\/grok-image-1a23f597-e09a-4bcd-b82a-8ced4f248276.jpg 1280w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The 2026-07-28 Model Context Protocol specification brings a stateless protocol core, Multi Round-Trip Requests, header-based routing, cacheable list results, authorization hardening, a formal extensions framework, and updated Tier 1 SDKs.  Half a billion downloads per month across Tier 1 SDKs, with TypeScript and Python each crossing 1 billion total downloads. MCP is now foundational infrastructure \u2014 and the 2026-07-28 spec tightens the contract between clients and servers so those connections are easier to operate, observe, and evolve.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This post breaks down what changed, what broke, and the exact migration steps for builders running the <a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/mcp-server-python\/\">MCP Server Python<\/a> pattern from this series against the previous spec.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_85 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/mcp-2026-specification\/#The_MCP_2026_Specifications_Biggest_Change_Stateless_Core\" >The MCP 2026 Specification&#8217;s Biggest Change: Stateless Core<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/mcp-2026-specification\/#What_the_MCP_2026_Specification_Adds_Tasks_MCP_Apps_Extensions\" >What the MCP 2026 Specification Adds: Tasks, MCP Apps, Extensions<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/mcp-2026-specification\/#Tasks_Extension_Long-Running_Async_Work\" >Tasks Extension: Long-Running Async Work<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/mcp-2026-specification\/#MCP_Apps_Server-Rendered_UIs_in_Clients\" >MCP Apps: Server-Rendered UIs in Clients<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/mcp-2026-specification\/#Extensions_Framework_Stable_Independent_Evolution\" >Extensions Framework: Stable Independent Evolution<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/mcp-2026-specification\/#What_the_MCP_2026_Specification_Deprecated_The_Breaking_Changes\" >What the MCP 2026 Specification Deprecated: The Breaking Changes<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/mcp-2026-specification\/#The_Migration_Checklist_for_August\" >The Migration Checklist for August<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/mcp-2026-specification\/#The_Open_Governance_Story_MCP_Under_the_Linux_Foundation\" >The Open Governance Story: MCP Under the Linux Foundation<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/mcp-2026-specification\/#The_Builders_Takeaway\" >The Builder&#8217;s Takeaway<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/mcp-2026-specification\/#Continue_in_This_Series\" >Continue in This Series<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"The_MCP_2026_Specifications_Biggest_Change_Stateless_Core\"><\/span>The MCP 2026 Specification&#8217;s Biggest Change: Stateless Core<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The headline change is that MCP no longer manages sessions at the protocol layer. Six Specification Enhancement Proposals work together to remove the session model that the 2025-11-25 spec was built on.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In the old spec, MCP servers maintained sessions: a client sent an <code>initialize<\/code> request, received a session ID via <code>Mcp-Session-Id<\/code>, and subsequent requests were pinned to that server instance. This created an immediate infrastructure problem at scale: load balancers required sticky routing or shared session stores, making horizontal scaling unnecessarily complex.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The 2026-07-28 spec removes this entirely. Every Streamable HTTP POST request must now include <code>Mcp-Method<\/code> (e.g. <code>tools\/call<\/code>) and <code>Mcp-Name<\/code> (tool or resource name) headers. Load balancers, API Gateways, and rate-limiters route without parsing the JSON-RPC body.  Standard round-robin load balancing works out of the box. Long-lived SSE connections that behaved like &#8220;ghost websockets&#8221; are gone.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The practical effect for builders: for teams running MCP servers behind enterprise identity providers \u2014 Okta, Azure AD, Google Workspace \u2014 the path from &#8220;unauthenticated MCP server&#8221; to &#8220;properly secured MCP server&#8221; is now defined at the spec level rather than left as an exercise.  Microsoft Foundry&#8217;s endorsement in the official release captures the production value: &#8220;With stateless operations, Tasks for long-running work, and enterprise-managed identity, the next generation of MCP makes it easier than ever to build secure, scalable, production-ready agent systems.&#8221;<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_the_MCP_2026_Specification_Adds_Tasks_MCP_Apps_Extensions\"><\/span>What the MCP 2026 Specification Adds: Tasks, MCP Apps, Extensions<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Tasks_Extension_Long-Running_Async_Work\"><\/span>Tasks Extension: Long-Running Async Work<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The Tasks extension is the MCP 2026 specification&#8217;s answer to the blocking problem: tool calls that take more than a few seconds were forced to either block the client or rely on custom polling patterns. Tasks introduces a first-class primitive for long-running, async operations with structured progress tracking.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A task-enabled MCP tool returns immediately with a task ID. The client polls for progress updates using the task ID, and the server pushes structured progress messages as the operation proceeds. For the agent orchestration patterns in the <a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/sub-agent-orchestration-python\/\">Sub-Agent Orchestration<\/a> post \u2014 where a sub-agent might run a complex analysis that takes minutes \u2014 Tasks replaces the custom async workarounds most builders have cobbled together with a spec-standardized pattern.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"MCP_Apps_Server-Rendered_UIs_in_Clients\"><\/span>MCP Apps: Server-Rendered UIs in Clients<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">MCP Apps let servers render interactive HTML UIs directly in the MCP client. The rendered UI communicates back with the server through the standard MCP protocol. For the <a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/micro-saas-ai-agent\/\">Micro-SaaS AI Agent<\/a> retainer model, this means an MCP server can expose a configuration dashboard, a results viewer, or an approval workflow UI that lives inside Claude Cowork or any MCP-native client \u2014 without requiring a separate web app.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Extensions_Framework_Stable_Independent_Evolution\"><\/span>Extensions Framework: Stable Independent Evolution<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Extensions get reverse-DNS identifiers, their own repositories, delegated maintainers, and versions that move independently from the main spec. Clients and servers negotiate extension support through an extensions map in their capabilities.  This means Tasks and MCP Apps can ship updates without waiting for a full spec revision \u2014 the same model that makes browser APIs stable while still evolving.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_the_MCP_2026_Specification_Deprecated_The_Breaking_Changes\"><\/span>What the MCP 2026 Specification Deprecated: The Breaking Changes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Three features from the 2025-11-25 spec are deprecated in 2026-07-28. They remain in the spec during the deprecation window (minimum 12 months), but new implementations should not use them:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Roots:<\/strong> deprecated in favour of passing filesystem context through tool parameters directly. If your MCP server exposes roots for file system navigation, migrate to explicit path parameters in tool schemas.<\/li>\n\n\n\n<li><strong>Sampling:<\/strong> deprecated in favour of calling the model provider&#8217;s API directly. The indirect sampling pattern was always awkward \u2014 the deprecation formalises what most production builders were doing anyway.<\/li>\n\n\n\n<li><strong>Logging:<\/strong> deprecated in favour of using your existing observability stack (OpenTelemetry, Datadog, CloudWatch) rather than routing logs through the MCP protocol layer. For the <a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/ai-agent-gateway\/\">AI Agent Gateway<\/a> audit trail pattern, this means MCP is no longer the log transport \u2014 your gateway&#8217;s existing logging infrastructure handles this directly.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"The_Migration_Checklist_for_August\"><\/span>The Migration Checklist for August<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code># MCP 2026-07-28 Migration Checklist\n# Run against every MCP server you operate this month\n\n# Step 1: Update your SDK to the 2026-07-28 Tier 1 release\npip install --upgrade mcp  # Python SDK\nnpm install @modelcontextprotocol\/sdk@latest  # TypeScript SDK\n\n# Step 2: Find and remove session dependencies\n# Search your codebase for these patterns \u2014 they break under stateless routing:\n# - Mcp-Session-Id header storage or forwarding\n# - initialize handshake result caching\n# - Per-session state stored in server memory\n\n# Step 3: Add required headers to all Streamable HTTP POST requests\n# OLD (2025-11-25): POST \/mcp with JSON-RPC body only\n# NEW (2026-07-28): POST \/mcp with headers + JSON-RPC body\n\n# Python server example \u2014 FastAPI\nfrom fastapi import FastAPI, Request, HTTPException\n\napp = FastAPI()\n\nVALID_MCP_METHODS = {\"tools\/call\", \"tools\/list\", \"resources\/read\"}\n\n@app.post(\"\/mcp\")\nasync def mcp_endpoint(request: Request):\n    mcp_method = request.headers.get(\"Mcp-Method\")\n    mcp_name = request.headers.get(\"Mcp-Name\")\n\n    if not mcp_method:\n        raise HTTPException(\n            status_code=400,\n            detail=\"Mcp-Method header required in 2026-07-28 spec\"\n        )\n\n    if mcp_method not in VALID_MCP_METHODS:\n        raise HTTPException(\n            status_code=400,\n            detail=f\"Unknown Mcp-Method: {mcp_method}\"\n        )\n\n    # Route by Mcp-Method header \u2014 no session state required\n    body = await request.json()\n    return await dispatch(mcp_method, mcp_name, body)\n\n\nasync def dispatch(method: str, name: str | None, body: dict) -&gt; dict:\n    \"\"\"\n    Stateless dispatch \u2014 each request is self-contained.\n    No Mcp-Session-Id, no initialize handshake state.\n    \"\"\"\n    if method == \"tools\/call\":\n        return await handle_tool_call(name, body.get(\"params\", {}))\n    elif method == \"tools\/list\":\n        return {\"tools\": get_tool_list()}  # Cacheable list result\n    elif method == \"resources\/read\":\n        return await handle_resource_read(name, body.get(\"params\", {}))\n    return {\"error\": {\"code\": -32601, \"message\": \"Method not found\"}}\n\n\n# Step 4: Migrate deprecated features\n# Roots \u2192 explicit path parameters in tool schemas\n# Sampling \u2192 call model provider API directly\n# Logging \u2192 route to your existing observability stack (OpenTelemetry etc.)\n\n# Step 5: Add Tasks extension support for long-running tools\n# Replace blocking tool calls &gt; 5 seconds with Task-returning tools\n# Client polls \/mcp with Mcp-Method: tasks\/get for progress<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"The_Open_Governance_Story_MCP_Under_the_Linux_Foundation\"><\/span>The Open Governance Story: MCP Under the Linux Foundation<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">One structural change in the MCP 2026 specification release is worth noting separately: MCP is now hosted by the Agentic AI Foundation under the Linux Foundation. This open governance model ensures neutral stewardship while retaining a focused specification enhancement process led by active maintainers.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For builders making infrastructure decisions, this matters. A protocol governed by a single company can be deprecated, forked, or strategically redirected to serve that company&#8217;s competitive interests. A protocol under Linux Foundation governance has an independent Standards Body behind it \u2014 the same structure that has kept HTTP, DNS, and TCP\/IP stable infrastructure for decades. The MCP 2026 specification formalises the deprecation policy (12-month minimum window, written rules) and the conformance suite that validates official SDKs. This is infrastructure-grade protocol governance, not a startup&#8217;s open-source project.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For the complete MCP 2026-07-28 specification and migration guide, see <a href=\"https:\/\/blog.modelcontextprotocol.io\/posts\/2026-07-28\/\" target=\"_blank\" rel=\"noopener\">the official MCP specification blog post<\/a>.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"The_Builders_Takeaway\"><\/span>The Builder&#8217;s Takeaway<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The MCP 2026 specification is the upgrade that makes MCP a first-class HTTP workload \u2014 no sessions, no sticky routing, no protocol-layer logging, no sampling indirection. For builders running MCP servers in production against the 2025-11-25 spec, the migration work is straightforward but not optional: deprecated features will be removed in a future spec revision, and session-dependent servers will break under stateless load balancers. August is the migration window. The checklist above covers the four concrete steps: SDK update, session dependency removal, header addition, and deprecated feature migration. Start Monday. The migration is mechanical, the benefit \u2014 horizontal scale on standard HTTP infrastructure \u2014 is structural.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Continue_in_This_Series\"><\/span>Continue in This Series<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/mcp-server-python\/\">MCP Server Python<\/a> \u2014 the 2025-11-25 spec implementation this migration post updates: stateless explicit-handle pattern now aligned with the new spec<\/li>\n\n\n\n<li><a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/ai-agent-framework-2026\/\">AI Agent Framework 2026<\/a> \u2014 LangGraph 1.0 treats MCP tools as first-class nodes: the framework integration built on the new spec<\/li>\n\n\n\n<li><a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/ai-agent-gateway\/\">AI Agent Gateway<\/a> \u2014 authorization hardening in the 2026 spec aligns with OAuth and OIDC: the gateway&#8217;s auth layer benefits directly<\/li>\n\n\n\n<li><a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/sub-agent-orchestration-python\/\">Sub-Agent Orchestration<\/a> \u2014 Tasks extension replaces custom async workarounds in long-running sub-agent pipelines<\/li>\n\n\n\n<li><a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/how-to-deploy-ai-agents\/\">How to Deploy AI Agents<\/a> \u2014 Layer 2 (Orchestration) update: MCP 2026-07-28 is the new production baseline for the framework selection checklist<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\"><em>This post is part of The Agentic Protocol&#8217;s Work series \u2014 the connective infrastructure layer beneath every autonomous pipeline. See also: <a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/mcp-server-python\/\">MCP Server Python<\/a>.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The MCP 2026 specification is the biggest change to the Model Context Protocol since launch \u2014 and the production migration window is this month. If you&#8217;re running MCP servers against the 2025-11-25 spec, August is when the work of updating them begins in earnest. The 2026-07-28 Model Context Protocol specification brings a stateless protocol core, &#8230; <a title=\"MCP 2026 Specification: Critical Stateless Migration Guide\" class=\"read-more\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/mcp-2026-specification\/\" aria-label=\"Read more about MCP 2026 Specification: Critical Stateless Migration Guide\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":496,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[611,613,610,612,249],"class_list":["post-495","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-work-agentic-ai","tag-mcp-2026-specification","tag-mcp-authorization-2026","tag-mcp-stateless-migration","tag-mcp-tasks-extension","tag-model-context-protocol-2026"],"_links":{"self":[{"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/posts\/495","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/comments?post=495"}],"version-history":[{"count":1,"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/posts\/495\/revisions"}],"predecessor-version":[{"id":497,"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/posts\/495\/revisions\/497"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/media\/496"}],"wp:attachment":[{"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/media?parent=495"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/categories?post=495"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/tags?post=495"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}