Mainframe MCP Server
Related Servers
Alternatives to Mainframe MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA standalone MCP server for TD/OMS change management that connects directly to TD/OMS REST APIs and enables workflow planning, execution, and monitoring for IBM i development tools.15 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to interact with IBM i AS/400 source members for source code management, compilation, and development workflows.7MIT
- AlicenseAqualityCmaintenanceAn MCP server that exposes RS232 serial port connectivity, enabling listing, opening, reading, and writing to serial ports via tools and resources.6MIT
- AlicenseBqualityDmaintenanceMCP server for Redmine project management, enabling tools for managing projects, issues, users, time entries, groups, memberships, versions, wiki, news, attachments, search, and Agile sprints via the Redmine REST API.893 npm1MIT
- FlicenseNot gradedqualityCmaintenanceMulti-system MCP server for reading and writing ABAP source via SAP ADT, with write safety controls and a local web admin.2-
- AlicenseNot gradedqualityAmaintenanceA full-featured secure MCP server for local file system operations, with built-in image processing, OCR and media tools.Apache 2.0
TDQS
Scored across 30 tools
Many tools follow a clear get_<artifact> pattern (COBOL, copybook, CT1, JCL, PROC), and the job-status/spool tools are distinct. However, generic get_content overlaps heavily with the specialized getters, and get_jcl vs get_job_jcl plus upload_member vs modify_module create potential confusion.
Tool names overwhelmingly use snake_case verb_noun, with clear verbs like get, submit, create, delete. Minor inconsistencies exist (get_cobol vs get_content, search_seq_datasets uses an abbreviation, create_dataset_like) but the pattern is predictable.
At 30 tools, the server is over-scoped for a coherent set. Many specialized getters could be consolidated into get_content, and the job-spool area has four overlapping tools. A more focused set of 15-20 would be stronger.
The set covers dataset lifecycle (create, delete, rename, recall, copy, modify), source retrieval, and full job submission/status/spool flow. Missing member-level deletion and a direct list-members operation are minor gaps.