F
licenseNot graded
qualityB
maintenanceEnables LLMs to explore legacy COBOL mainframe codebases through MCP tools for call graphs, copybook usage, DB2 tables, and impact analysis.
-
ISPW MCP Server
by markbsigler
Related Servers
Alternatives to ISPW MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with IBM i (AS/400) systems for RPA automation via 37 tools for 5250 navigation, CL commands, DB2 queries, and system management.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with IBM Engineering Lifecycle Management (ELM), including DOORS Next Generation, EWM, and ETM, for managing requirements, work items, tests, and project builds through natural language.MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLM agents to manage projects, track issues, log work, and integrate with Git. Provides 23 MCP tools for full project management capabilities.15-
- FlicenseNot gradedqualityFmaintenanceEnables LLMs and AI applications to interact with Azure DevOps Work Items, supporting queries, filtering, status updates, date management, effort tracking, descriptions, and comments through natural language.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Azure DevOps APIs for managing projects, work items, repositories, pull requests, pipelines, and more through natural language.21,494 npmMIT
TDQS
A3.9/5.0
Scored across 13 tools
Disambiguation4/5
Most tools pair a distinct resource with a distinct action (list/get/create assignment, release, package), so an agent can select correctly. Minor overlap remains: ispw_list_assignments can filter by assignment_id like ispw_get_assignment, ispw_deploy accepts assignment/release/set targets that overlap conceptually with ispw_promote_assignment, and sets vs packages are both described as 'collections of components for deployment'.
Naming Consistency5/5
Every tool uses the same ispw_ prefix followed by a verb_noun pattern in snake_case (ispw_list_tasks, ispw_create_release, ispw_promote_assignment). No camelCase or style mixing, and verbs are used consistently for the same semantic actions.
Tool Count5/5
13 tools is squarely in the well-scoped range and each one maps to a distinct ISPW lifecycle step (list/get/create containers, generate, promote, deploy). No obviously redundant or filler tools.
Completeness3/5
The generate/promote/deploy lifecycle and read paths are covered, but there is no update or delete for assignments, releases, or packages, and lists (tasks, sets) have no corresponding get/detail operations. Agents also cannot add/remove components or assignments from a release/set, which are common workflow steps in this domain.
Maintenance
ActivityMaintained
ResponsivenessNo issues