<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Model Context Protocol (MCP) - News</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Model Context Protocol (MCP) News feed</description>
    <item>
      <title>MCP Goes Stateless, and Developers Ask Whether That Just Makes It an API Again</title>
      <link>https://www.infoq.com/news/2026/08/mcp-stateless-gateway/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Model+Context+Protocol+%28MCP%29-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/mcp-stateless-gateway/en/headerimage/generatedHeaderImage-1786118533592.jpg"/&gt;&lt;p&gt;The MCP 2026-07-28 specification removes the initialize handshake and session header, and adds required method and tool-name headers so gateways can route agent traffic without parsing JSON. Reaction split between developers calling it a rediscovery of REST and those arguing the standard itself was always the point.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>API Gateway</category>
      <category>Cloudflare</category>
      <category>Cloud</category>
      <category>Serverless</category>
      <category>Standardization</category>
      <category>AI Architecture</category>
      <category>Model Context Protocol (MCP)</category>
      <category>Development</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Wed, 12 Aug 2026 09:48:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/mcp-stateless-gateway/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Model+Context+Protocol+%28MCP%29-news</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-08-12T09:48:00Z</dc:date>
      <dc:identifier>/news/2026/08/mcp-stateless-gateway/en</dc:identifier>
    </item>
    <item>
      <title>Instacart Builds Blueberry, an AI-Powered Assistant to Help On-Call Engineers Investigate Incidents</title>
      <link>https://www.infoq.com/news/2026/08/instacart-blueberry-sre-ai/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Model+Context+Protocol+%28MCP%29-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/instacart-blueberry-sre-ai/en/headerimage/generatedHeaderImage-1785721280661.jpg"/&gt;&lt;p&gt;Instacart introduced Blueberry, an AI-assisted incident response system that helps on-call engineers investigate production issues faster. It combines AI agents, operational data, and historical incident knowledge to generate grounded root cause hypotheses in Slack. It uses parallel subagents, MCP integrations, and incident history to reduce investigation time while keeping engineers in control.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Distributed Systems</category>
      <category>Reliability</category>
      <category>Large language models</category>
      <category>Artificial Intelligence</category>
      <category>Site Reliability Engineering</category>
      <category>Model Context Protocol (MCP)</category>
      <category>Operational Intelligence</category>
      <category>Developer Experience</category>
      <category>Slack</category>
      <category>Incident Response</category>
      <category>Platform Engineering</category>
      <category>Observability</category>
      <category>Development</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Fri, 07 Aug 2026 14:34:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/instacart-blueberry-sre-ai/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Model+Context+Protocol+%28MCP%29-news</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-08-07T14:34:00Z</dc:date>
      <dc:identifier>/news/2026/08/instacart-blueberry-sre-ai/en</dc:identifier>
    </item>
    <item>
      <title>Azure API Management Adds Dedicated AI Gateway Tier, Governing Models and MCP Tools</title>
      <link>https://www.infoq.com/news/2026/08/azure-apim-ai-gateway-tier/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Model+Context+Protocol+%28MCP%29-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/azure-apim-ai-gateway-tier/en/headerimage/generatedHeaderImage-1785739180016.jpg"/&gt;&lt;p&gt;Microsoft released a dedicated AI Gateway tier of Azure API Management in public preview, with a control plane built around models, MCP servers and tools rather than APIs. It fronts Foundry, Bedrock, Vertex AI and OpenAI behind one endpoint, with policy cards instead of XML. Architects welcomed the consolidation while questioning where the governance boundary sits.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Generative AI</category>
      <category>Azure</category>
      <category>API Gateway</category>
      <category>Cloud</category>
      <category>Model Context Protocol (MCP)</category>
      <category>Microsoft Azure</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Fri, 07 Aug 2026 06:35:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/azure-apim-ai-gateway-tier/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Model+Context+Protocol+%28MCP%29-news</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-08-07T06:35:00Z</dc:date>
      <dc:identifier>/news/2026/08/azure-apim-ai-gateway-tier/en</dc:identifier>
    </item>
  </channel>
</rss>
