COBOL Bridge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_cobol_programB | Parse a COBOL source file. Extract divisions, paragraphs, file IO, SQL/CICS, copybooks, complexity. |
| identify_business_rulesC | Extract IF/EVALUATE business rules from COBOL PROCEDURE DIVISION. |
| estimate_migration_complexityC | Estimate migration effort to target stack (python/java/go/rust/dotnet). |
| plan_migration_phasesB | Generate a 4-phase migration plan based on LOC + complexity. |
| generate_test_harnessC | Generate skeleton test harness for parallel-run equivalence testing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
With 5 tools, the server is well-scoped for its purpose of COBOL migration analysis and planning. Each tool earns its place without redundancy.
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.