The Bridge Is Built. The Stack Is Named.
There is a version of this moment where the IBM i community spends the next three years watching AI happen to other platforms. That version is over.
IBM has built the bridge. The stack is named. The tools are available today. And the people best positioned to use them are the ones who already know the business the stack is built to run.
This issue is about the architecture. Not a roadmap. Not a beta. What exists right now, how the layers connect, and why this platform is not behind — it is ahead of where every other enterprise stack is trying to get.
MCP — The Bridge Has a Name. It's Live.
For years, the practical barrier to connecting IBM i to the modern AI ecosystem wasn't the data or the logic — it was the interface. Model Context Protocol changes that. MCP is the tool protocol — the layer that defines what an agent is authorized to access, execute, and observe. Anthropic designed it as a universal standard, a USB-C port for AI applications. One protocol. Any agent. Any framework.
IBM shipped the IBM i MCP Server under an Apache 2.0 open source license. SQL Services. CL Commands. System monitoring. Security auditing. All exposed as callable tools to any MCP-compatible agent. The supported client list: Claude Code, Claude Desktop, VSCode, Cursor, Windsurf, Roo Code, LM Studio, Gemini CLI, Cline. IBM is building for the whole ecosystem.
Mapepire — The Db2 You Already Have, Now Callable
The fear that stopped most IBM i modernization conversations was legitimate: you can't touch what's running. Mapepire is different. It sits above the Sovereign Core — RPG and Db2 stay exactly as they are. Mapepire makes them callable via WebSocket, optimized for the request-response patterns AI agents actually use.
Multiple agentic frameworks are confirmed working with IBM i via Mapepire: LangChain, Agno, and the MCP protocol itself. BeeAI and CrewAI are in progress. The ecosystem is not locked to a single vendor or approach. The IBM i MCP Server requires Mapepire as its foundation. They are not separate tools — they are the two layers of the same bridge.
The Four Layers — All of Them Exist Today
The Stack Is Still Expanding
IBM is developing an experimental SDK that would let developers call AI models directly from Db2 for i — and by extension from RPG via embedded SQL. The concept: a SQL function call connects existing business logic to any LLM endpoint. IBM watsonx, Ollama, any OpenAI-compatible solution, on-premise inference options — all reachable from inside the RPG codebase itself. No new language. No new architecture layer.
The SDK is currently documented as experimental. IBM's own GitHub describes it as "in bringup state." But the direction is clear: if this ships, existing RPG code participates in AI workflows without a rewrite. The 30 years of business logic encoded in that codebase doesn't have to be migrated, translated, or replaced to become part of an agentic system. It calls the agent. The agent calls it back.
Four signals. One conclusion. The IBM i MCP Server is live and in active development. Mapepire is the foundation multiple frameworks already run on. The four-layer stack is specified and deployable today. And IBM is building the next layer — native AI calls from RPG — with production readiness on the horizon.
What's missing is not technology. It is not the platform. It is not the people. What's missing is the posture. The organizational decision to treat this as the moment it is — and to move before someone else names what you have and builds on top of it without you.