
As400 Bridge Mcp
io.github.CSOAI-ORGPublished by GitHub account CSOAI-ORGv0.1.3Updated Nov 5, 2026
IBM i / RPG / DB2 bridge — parse, map, govern (IBM i security / SOX).
Overview
Local MCP server that bridges IBM i / RPG / DB2 legacy code, letting an assistant parse RPG, identify files, map to modern targets and apply governance checks.
- What you can do
- Parse RPG source code
- Identify referenced files and data structures
- Map legacy assets to modern equivalents
- Apply IBM i security and SOX governance checks
- When to use it
- Useful when modernizing or auditing IBM i / AS400 systems: understanding RPG programs, cataloguing DB2 files, planning migration mappings, or checking governance and SOX-related concerns.
- Requirements
- Runs as a local Python process installed from the as400-bridge-mcp PyPI package (pip install, then run the server script). Desktop only; no authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open As400 Bridge Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
as400-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
Source: README.md at commit 5068a96
Tools
0Version history
1- v0.1.3LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.