What dependencies does the server require?
The server requires **Java 21+** and a Maven build system (`./mvnw clean package`). No other runtime dependencies are mentioned.
@abstracta
Basic information
This project implements a customizable MCP server to execute RTE protocol.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"executeRteTransaction": {
"command": "{java_path}",
"args": [
"-jar",
"-Dspring.ai.mcp.server.stdio=true",
"{jar_path}"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
It is an MCP (Model Context Protocol) server that executes RTE (Remote Terminal Emulation) protocol transactions on IBM AS/400 iSeries systems. It uses customizable YAML-based flows to define connection parameters and interaction steps, and it supports multiple terminal protocols (TN5250, TN3270, VT420). The server is intended for developers who need to automate terminal interactions with legacy IBM midrange systems.
You need Java 21+. Compile the project with ./mvnw clean package. Then run the server in SSE mode with java -jar target/rte-mcp-server-0.0.1-SNAPSHOT.jar or in STDIO mode by adding -Dspring.ai.mcp.server.stdio=true. Configure connection parameters and RTE flow steps in a YAML file (e.g., flow.yaml). The YAML defines server, port, protocol, terminalType, sslType, and a list of steps with actions (label/input pairs) and an attentionKey.
RteUtils class and @Tool/@Service annotations.The server requires **Java 21+** and a Maven build system (`./mvnw clean package`). No other runtime dependencies are mentioned.
Define a YAML file with a `config` section (server, port, protocol, terminalType, sslType) and a `steps` section. Each step contains a list of `actions` (label/input pairs) and an `attentionKey` (e.g., ENTER, F1). Place the file in the classpath (e.g., `/flow.yaml`).
Supported protocols: **TN5250**, **TN3270**, and **VT420**. Terminal types vary per protocol; for example, TN5250 supports `IBM-3477-FC: 27x132` and `IBM-3179-2: 24x80`. See the README table for full list.
Yes. Add `-Dspring.ai.mcp.server.stdio=true` to the Java command. Otherwise, the server runs in SSE mode by default.
Extend the server by creating a `@Service` class that implements `RteTool`. Use `RteUtils.connect()` and `RteUtils.executeSteps()` inside a `@Tool`‑annotated method. Load your YAML flow inside the method.
🚀 The fast, Pythonic way to build MCP servers and clients.

A good sequence diagram can solve almost any communication problem in engineering. Volley lets your agent write them as plain text, with the real request and response payloads on every arrow. It checks its own syntax wi

A free remote MCP server for The Living Bread. Bible passages read word for word from a stored public domain text with an evidence label, keyword search and cross references, real churches, gatherings and prayer groups w
Open-source MCP to use Blender with any LLM

LoadOptimizer plans truck, container and pallet loads with a real optimization engine, straight from your AI assistant. Describe the order in plain language, for example "plan 36 Euro pallets on a standard 13.6 m trailer
Comments