A
licenseB
qualityC
maintenanceAI-assisted COBOL to modern stack bridge that parses COBOL programs, maps to Python/Java/Go, generates test harnesses, and plans migration for legacy mainframe modernization.
5
83 PyPI
MIT
mcp-migration-tools
by simeptk
Related Servers
Alternatives to mcp-migration-tools
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAutomatically crawl and analyze legacy web applications to generate documentation and modernization plans.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceConnects legacy COBOL mainframe systems to modern AI governance via MCP, with tools for parsing copybooks, assessing CICS, scanning JCL, mapping VSAM, and translating EBCDIC.1MIT
- FlicenseNot gradedqualityDmaintenanceA universal bridge that turns legacy backend services and modern APIs into AI-accessible tools without requiring code rewrites. It dynamically generates tool definitions from WSDL, OpenAPI, or custom JSON specs to enable AI assistants to interact with systems like SAP, IBMi, and SOAP services.-
- AlicenseCqualityDmaintenanceProvides an enterprise-grade AI-powered pipeline with 33 professional tools for code analysis, migration, testing, and more, integrated with modern IDEs like Cursor and VS Code.213844 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI agents to analyze legacy code, plan and execute software migrations, generate modern source code, and validate production-ready artifacts through a multi-agent pipeline.MIT
TDQS
A3.5/5.0
Scored across 4 tools
Disambiguation5/5
Each tool targets a unique aspect of migration: API extraction, SQL conversion, stack detection, and effort estimation. No two tools perform similar or overlapping functions, making selection unambiguous.
Naming Consistency4/5
The naming style is consistent with lowercase snake_case and mostly follows a verb_noun pattern (extract_api_contract, detect_stack, estimate_migration_effort). One tool (sql_to_flyway) uses a noun_to_noun pattern, which is a minor deviation but still clear and readable.
Tool Count4/5
With 4 tools, the set is within the ideal 3-15 range and feels appropriately scoped for a focused migration utility. It is slightly sparse but each tool serves a distinct purpose.
Completeness3/5
The tools cover analysis, conversion, and estimation, but lack any migration execution or validation operations. There are notable gaps in the end-to-end migration workflow, though the existing tools are sound.
Maintenance
ActivitySlowing
ResponsivenessNo issues