COBOL Bridge MCP
by CSOAI-ORG
README.md
# COBOL Bridge MCP — read-only sidecar (SPEC)
**SPEC, not a live product.** See [`SPEC.md`](SPEC.md).
- Read-only sidecar. Never writes core / ledger / CICS.
- `cobolbridge.ai` HTTP **522** sits. This README does not attach the domain.
- No Starter / Pro / Enterprise pricing on this measurement surface.
- Not certified. Not partnered. Not a second GSPC board.
- Living board: `GET https://councilof.ai/api/gspc` (22 axis · 15 measured · 7 empty).
mcp-name: io.github.CSOAI-ORG/cobol-bridge-mcp
[](LICENSE)
[](https://pypi.org/project/cobol-bridge-mcp/)
MIT parser: COBOL source text in, heuristic metrics out. Optional MCP next to a workstation. Never an inside-bank install.
## Install (local / stdio)
```bash
pip install cobol-bridge-mcp
# or
uvx cobol-bridge-mcp
```
```json
{
"mcpServers": {
"cobol-bridge-mcp": {
"command": "uvx",
"args": ["cobol-bridge-mcp"]
}
}
}
```
Tools (read the source you already hold; they do not write production):
- `parse_cobol_program`
- `identify_business_rules`
- `estimate_migration_complexity`
- `plan_migration_phases`
- `generate_test_harness`
## Contract
Full contract: [`SPEC.md`](SPEC.md). Measurement, never certification. Do not stamp MEASURED. Do not claim 17 banks are clients.
## License
MIT © [CSOAI-ORG](https://github.com/CSOAI-ORG) / CSOAI Ltd (GB, Companies House 16939677)
<!-- mcp-name: io.github.CSOAI-ORG/cobol-bridge-mcp -->
TDQS
B3.4/5.0
Scored across 5 tools
Disambiguation5/5
Each tool targets a distinct aspect of COBOL migration: parsing, complexity estimation, business rule extraction, test harness generation, and phase planning. No overlap in functionality.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern (e.g., parse_cobol_program, generate_test_harness) making the set predictable and easy to navigate.
Tool Count5/5
With 5 tools, the server is well-scoped for its purpose of COBOL migration analysis and planning. Each tool earns its place without redundancy.
Completeness4/5
The tool surface covers core migration steps (parsing, complexity, rules, testing, planning). Minor gaps like direct code transformation are absent but acceptable given the server's advisory role.
Maintenance
ActivityMaintained
ResponsivenessNo issues