tn5250-mcp
Related Servers
Alternatives to tn5250-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI tools to operate IBM i 5250 green screens, driving and testing interactive RPG programs by seeing screens, typing into fields, and pressing keys.626 npm1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to drive 5250 screens, read, search, edit, and compile IBM i source members over SSH, and learn enterprise data structures and workflows from knowledge packs.Apache 2.0
- 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 gradedqualityCmaintenanceEnables AI assistants to securely interact with IBM i (AS/400) systems via ODBC, supporting SQL queries, CL commands, source code reading, compilation, and spoolfile analysis.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with IBM i systems through the Model Context Protocol, providing secure SQL-based access to Db2 for i databases for querying, monitoring, and executing operations.Apache 2.0
- AlicenseAqualityCmaintenanceGive your AI Agent terminal access to your IBM i system via TN5250. ibmi-mcp is an MCP server that lets AI Agents like Claude interact with IBM i the same way a human would through a 5250 green-screen terminal.815BSD 2-Clause "Simplified"
TDQS
Scored across 14 tools
Most tools target distinct actions: connect/disconnect, list_sessions/list_profiles, get_screen/get_session_log all have clear boundaries aided by descriptions. The closest overlap is fill vs press, but fill explicitly types without sending while press sends to host, so they remain distinguishable.
A partial verb_noun convention appears in get_session_log, forget_password, list_profiles, list_sessions, get_screen, record_start, record_stop, but it is broken by bare verbs (connect, fill, press, wait) and bare nouns (viewer, keys). Readable but mixed conventions.
14 tools is well-scoped for a 5250 terminal automation server, covering connection lifecycle, screen interaction, recording, and support tools without excess.
Core terminal workflow is covered: connect, navigate (get_screen, fill, press, wait), session/profile management, recording, and logging. Minor gaps exist around profile creation/editing and recording management (delete/list recordings).