Skip to main content
Glama
SH4RKKK

ibm-i-5250-mcp

by SH4RKKK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ibm-i-5250-mcp

No user-submitted related servers found.

    Related Servers

    • ibmi-mcp-server

      nemu90
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    • ibmi-mcp

      WhitehornLtd
      A
      license
      A
      quality
      C
      maintenance
      Give 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.
      8
      14
      BSD 2-Clause "Simplified"

    • winagent

      ZYYDI1959
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible AI platforms to see the screen and operate any desktop software through real mouse clicks, text input, key presses, and scripted scenario execution.
      MIT

    • IBM i MCP Server

      Programmersio-IBMi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    • Browser[X]MCP

      rnd-pro
      A
      license
      B
      quality
      D
      maintenance
      Enables AI-driven browser automation with advanced form testing, batch operations, and intelligent element extraction for MCP-compatible applications.
      14
      45 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool owns a distinct responsibility: session lifecycle (open/close), passive inspection (screen_snapshot), active interaction (screen_do), regression testing (run_tests), and configuration (list_servers). Even though screen_snapshot and screen_do both return screens, one is inspect-only and the other is action-driven, so there is no real ambiguity.

    Naming Consistency3/5

    The resource-prefixed names like session_open, session_close, and screen_do are readablearke, but the convention is not uniform: screen_snapshot is a noun phrase while run_tests and list_servers use verb_noun order. All names share lowercase snake_case, but an agent cannot consistently predict whether the verb appears first or last.

    Tool Count5/5

    Six tools is well-scoped for a 5250 automation server: session lifecycle, inspection, action, testing, and server discovery each get one clear tool. There is no redundancy or bloat, and each tool earns its place.

    Completeness5/5

    The surface covers the full session lifecycle and interaction loop: open, snapshot, act, close, plus regression testing and server discovery. screen_do's combined action syntax handles typing, cursor movement, and keys in one exchange, so there are no obvious dead ends for the intended domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources