IBM AS/400 ISeries

Customizable MCP server that executes RTE protocol flows against IBM AS/400 iSeries environments via YAML-defined configs.

java

15

GitHub Stars

java

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "abstracta-ibm-as-400-iseries-mcp-server": {
      "command": "java",
      "args": [
        "-jar",
        "-Dspring.ai.mcp.server.stdio=true",
        "rte-mcp-server-0.0.1-SNAPSHOT.jar"
      ]
    }
  }
}

You run a customizable MCP server that executes RTE protocol flows against IBM AS/400 iSeries systems. It lets you define how to connect to an RTE host, specify the steps to perform on the screen, and run those steps through a lightweight MCP interface so you can automate legacy terminal interactions.

How to use

You will run the MCP server in stdio mode to interact with RTE terminals locally, or in SSE mode for standard server execution. Start the server with the provided Java command, then connect an MCP client that can discover or be configured to call this MCP server as a local tool.

How to install

Prerequisites you need before you begin:

Install a Java 21+ runtime or JDK.
Ensure your environment has access to run Java applications.

Additional configuration and usage notes

The server is designed to execute RTE flows defined in YAML and to expose tools that interact with the RTE server. You start the server in stdio mode for local use, or SSE mode for standard server operation. The YAML flow describes connection parameters and a sequence of actions to perform on the RTE terminal screen.

java -jar -Dspring.ai.mcp.server.stdio=true rte-mcp-server-0.0.1-SNAPSHOT.jar

Example run commands

Start the MCP server in standard SSE mode (without STDIO) using the built-in jar.

java -jar target/rte-mcp-server-0.0.1-SNAPSHOT.jar

Using RTE tools and flows

The server relies on RteUtils to connect to the RTE server and to execute a defined sequence of steps. You define a YAML file that includes the RTE connection parameters and the steps to perform. Your MCP tool should call RteYamlLoader to load the flow, create a client with the connection config, and then execute the steps to obtain the resulting screen content.

Testing and debugging tips

When validating tool behavior, you can generate a dump of the RTE flow and mock it to test the tool logic. Use integration tests to verify the list of tools and their execution against the MCP client.

Available tools

rte_login_tool

Executes an RTE transaction on a given server by loading an RTE flow from YAML, connecting to the RTE server, and running the defined steps.

rte_connect

Connects to the RTE server using the YAML-defined configuration to establish a protocol session.

rte_execute_steps

Executes a sequence of steps on the RTE server and returns the resulting screen content.