
Cics Bridge Mcp
io.github.CSOAI-ORGPublished by GitHub account CSOAI-ORGv0.1.2Updated Oct 30, 2026
Bridge IBM CICS mainframe transactions to ONE OS — parse, map, govern (SOX / PCI-DSS / DORA).
Overview
Local MCP server that parses IBM CICS mainframe transactions, identifies them, maps them to modern systems, and applies SOX, PCI-DSS and DORA governance.
- What you can do
- Parse CICS transaction definitions and source artifacts
- Identify and classify CICS transactions
- Map legacy CICS transactions to modern equivalents
- Apply governance checks aligned with SOX, PCI-DSS and DORA
- When to use it
- Useful when modernizing or auditing IBM CICS mainframe workloads and you want an assistant to help parse transaction definitions, plan mappings to modern systems, and check compliance-oriented governance rules.
- Requirements
- Runs as a local stdio process installed from the PyPI package cics-bridge-mcp and started with Python (pip install, then run the server script). No authentication, environment variables or headers are declared. Desktop-only; not available as a web executable.
Installation
In SourceWeft
- Open Cics 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
cics-bridge-mcp
mcp-name: io.github.CSOAI-ORG/cics-bridge-mcp
Part of the CSOAI Layer-0 legacy-bridge family. Bridge IBM CICS mainframe transactions to ONE OS — parse, map, govern (SOX / PCI-DSS / DORA).
Tools: parse_cics · identify_transactions · map_to_modern · govern_cics
Source: README.md at commit 218f49c
Tools
0Version history
1- v0.1.2LatestSep 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.