About as400-bridge-mcp
An MCP server for bridging IBM i, RPG, and DB2 legacy systems to ONE OS. It provides tools for parsing, mapping, and governing legacy assets, including IBM i security and SOX considerations.
Key features
- 01Parse RPG code
- 02Identify files
- 03Map legacy systems to modern targets
- 04Govern IBM i
Use cases
- 01Parse RPG code
- 02Locate relevant legacy files
- 03Map legacy systems for modernization
- 04Review IBM i security and SOX governance
MCP support
Exposes `parse_rpg`, `identify_files`, `map_to_modern`, and `govern_ibmi` tools to MCP clients.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEas400-bridge-mcp
mcp-name: io.github.CSOAI-ORG/as400-bridge-mcp
Part of the CSOAI Layer-0 legacy-bridge family (sibling of cobol-bridge-mcp). Bridge IBM i / RPG / DB2 legacy to ONE OS — parse, map, govern (IBM i security / SOX).
Tools: parse_rpg · identify_files · map_to_modern · govern_ibmi
pip install -e .
python server.py
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.