<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Gateway on innFactory AI Consulting - AI Strategy &amp; Consulting</title><link>https://innfactory.ai/en/tags/ai-gateway/</link><description>Recent content in AI Gateway on innFactory AI Consulting - AI Strategy &amp; Consulting</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026</copyright><lastBuildDate>Sat, 22 Aug 2026 19:11:17 +0200</lastBuildDate><atom:link href="https://innfactory.ai/en/tags/ai-gateway/index.xml" rel="self" type="application/rss+xml"/><item><title>Agent Plugins: Why Packaging Is the Next Step After MCP</title><link>https://innfactory.ai/en/blog/agent-plugins-standard-portable-ai-building-blocks/</link><pubDate>Sat, 22 Aug 2026 00:00:00 +0000</pubDate><guid>https://innfactory.ai/en/blog/agent-plugins-standard-portable-ai-building-blocks/</guid><description>&lt;p&gt;Ask your IT department how many MCP servers are currently running in your organisation. In most companies the honest answer is: unknown. The Model Context Protocol solved something that had been open for years – an assistant can reach the ticket system, the file share and the line-of-business application without a bespoke connector for every model. What MCP never addressed: how that access is distributed, versioned and withdrawn as a unit.&lt;/p&gt;</description></item></channel></rss>