Some decisions are strategic. Some are philosophical. Infobip’s membership in the Agentic AI Foundation (AAIF) is a bit of both.
The AAIF is a directed fund under the Linux Foundation, the organization that stewards Linux, Kubernetes, Node.js, and PyTorch. Its mandate is to ensure that the infrastructure powering agentic AI evolves openly, predictably, and in the public interest. MCP (Model Context Protocol) is one of its founding projects, alongside goose by Block and AGENTS.md by OpenAI. As a Gold Member, Infobip is now part of the group shaping what that infrastructure looks like going forward.
Here’s why that matters for us at Infobip and for developers building with MCP.
The problem with closed standards
Protocols only work if everyone can trust them. And trust in a protocol has a specific meaning: you need to know that the thing you’re building on won’t be quietly redirected by whoever originally controlled it.
MCP being donated to the Linux Foundation, and governed through the AAIF, is a direct answer to that concern. The governance model stays unchanged, existing maintainers continue leading the project, community input drives decisions, and everything happens in the open.
What changes is the institutional layer: no single company owns the roadmap. That’s the same model that made Kubernetes the default for container orchestration, and PyTorch the default for deep learning research. It’s how infrastructure standards earn long-term trust.
For developers, that stability has a significant practical value. When they invest in building MCP-based tooling, they’re making a bet on the protocol’s longevity. The AAIF membership, 146 organizations including American Express, JPMorgan Chase, Red Hat, ServiceNow, and now Infobip as well, is essentially the industry placing that bet collectively.
Why Infobip is here
Infobip builds communication infrastructure: SMS, RCS, WhatsApp, Viber, email, voice, basically the channels that businesses use to reach people and interact with them. Historically, integrating those capabilities into a new platform meant custom API work, documentation, SDKs, authentication flows. Each integration was its own project.
MCP changes that calculus. Infobip MCP servers expose Infobip’s communication APIs as capabilities that AI agents can discover and use through a shared language, and no custom integration is required. An agent that can access MCP tools doesn’t need to “know how to use Infobip.” It needs to understand what actions are available, and MCP provides the vocabulary. That means developers building agentic workflows get messaging capabilities that are composable by default, not bolted on later.
Earlier this year, Infobip open-sourced the infobip-openapi-mcp framework — a tool that automatically generates MCP servers directly from OpenAPI specifications. Rather than hand-crafting individual integrations, developers can take any OpenAPI-described API and make it instantly accessible to AI agents through MCP. It’s a practical bet on the idea that MCP-based tooling should be easy to build, not just easy to use.
Joining the AAIF is the natural extension of that commitment. Open-sourcing the OpenAPI MCP framework Infobip used to create their MCP tools was about making the integration layer accessible to everybody. AAIF membership is about making sure the standard those servers are built on stays open, stable, and shaped by real-world use cases, including the use cases that come from connecting AI agents to communication infrastructure at scale.
As our Chief Product Officer Adrian Benić put it:
MCP fundamentally transforms how platforms integrate with AI agents by eliminating manual API integration work. Our communication APIs are machine-readable, allowing AI agents to independently discover capabilities and execute actions (…) through simple shared language. This dramatically reduces integration overhead, accelerates development, and lets developers focus on building innovative customer experiences.
Agentic AI Foundation press release
What developers gain long term
The practical benefits of AAIF membership aren’t abstract. Here’s what it means if you’re building with MCP:
Stability you can plan around. Linux Foundation stewardship means MCP follows a governance model with a proven track record. Breaking changes go through community review. The spec evolves predictably. You’re not building on a standard that could fork or deprecate on someone else’s timeline.
Interoperability as a first principle. The AAIF’s core purpose is reducing fragmentation. That means MCP-compatible tools, including Infobip’s, are designed to work together across platforms, not just within a single vendor’s ecosystem. An agent workflow that uses Infobip for messaging should be able to compose naturally with whatever other MCP-compatible tools a developer is using.
Influence over what comes next. The AAIF shapes the specification, the best practices, and the direction of agentic AI infrastructure. Infobip’s presence means that communication use cases, such as real-time notifications, authentication, omnichannel messaging, etc., have representation in those conversations. That’s relevant for any developer who wants messaging to be a first-class capability in agentic workflows, not an afterthought.
The MCP Dev Summit in New York (April 2–3) will bring the AAIF community together to work through the protocol’s next phase. It’s a reasonable place to see where this is all heading.
