MCP + AI for IBM i Teams (with a MongoDB example)
The Model Context Protocol (MCP) standard defines how AI tools connect to systems such as databases, services, and internal utilities. Instead of every AI product inventing its own custom connector, MCP provides a standard interface.
A good example comes from Seiden Group’s Jack Woehr in his article A Simple MongoDB MCP Server Agent. Jack was also just named MongoDB Creator of the Month. (MongoDb is a flexible NoSQL database that can manage large amounts of unstructured or semi-structured data.)
If you’re attending conferences this year, Jack will be talking about AI at NEUGC (April 7–9, 2026) and at COMMON POWERUp 2026 (April 27–30), where his sessions include “Using Large Language Models” and “AI on Power.”
Why IBM i teams should care
Most IBM i shops already live in a hybrid world: RPG + Db2 + CL alongside open source, APIs, web apps, and, increasingly, AI. MCP matters because it points toward a future where:
- you don’t need a one-off integration for every AI experiment
- you can put governance and guardrails around what AI can touch
- you can modernize incrementally, bridging systems instead of rewriting them
MCP fits for IBM i because it helps make AI integration projects more standardized and repeatable.
How Seiden Group can help
At Seiden Group, we’re focused on practical modernization and development. If you’re exploring any mix of:
- AI enablement (use cases, architecture, guardrails)
- MongoDB in a hybrid IBM i environment
- IBM i development and modernization (RPG, COBOL, SQL, APIs, open source)
We can help you evaluate options, build proof-of-concept projects, and implement production-ready solutions.
Get in touch to chat with us about your options.