Skip to content
AgentRetrofit

Connect AI Agents to Legacy Systems with Python & MCP

Bridge the gap between AI Agents and Legacy Iron.

Stop building fragile scrapers. Use our production-ready MCP servers to connect CrewAI or LangGraph to SAP, Oracle, and Mainframes.

Start Building View SAP Guide

Why AgentRetrofit?

Section titled “Why AgentRetrofit?”

Battle-Tested Patterns

Stop guessing how to structure your MCP servers. Our guides provide copy-paste architectures for SAP RFC, Oracle TNS, and IBM CICS.

Docker Ready

Every guide comes with a production-ready Dockerfile. We handle the complex dependency chains (like SAP NWRFC SDKs) so you don’t have to.

Type-Safe Schemas

LLMs hate messy data. We automatically convert legacy binary outputs into clean, validated JSON that your Agents can reliably parse.

Framework Agnostic

Whether you use CrewAI, LangGraph, AutoGen, or OpenAI Swarm, our MCP servers speak the universal language of tools.

High-Level Architecture

Section titled “High-Level Architecture”

We act as the Translation Layer between modern AI frameworks (which speak JSON) and legacy enterprise systems (which speak binary protocols like RFC, TNS, or SOAP).

graph LR
    subgraph Modern [Modern AI Stack]
        direction TB
        A[CrewAI Agent]
        B[LangGraph Workflow]
    end
    
    subgraph Bridge [The AgentRetrofit Layer]
        C(MCP Server Container)
    end
    
    subgraph Legacy [Enterprise Systems]
        direction TB
        D[(SAP ECC)]
        E[(Oracle DB)]
        F[(Mainframe)]
    end

    A <-->|JSON Protocol| C
    B <-->|JSON Protocol| C
    C <-->|Binary RFC| D
    C <-->|TNS / JDBC| E
    C <-->|TN3270| F

    style Modern fill:#f0fdf4,stroke:#166534,stroke-width:2px,stroke-dasharray: 5 5
    style Bridge fill:#fff7ed,stroke:#c2410c,stroke-width:2px
    style Legacy fill:#f1f5f9,stroke:#334155,stroke-width:2px

Integration Workflow

Section titled “Integration Workflow”

How you go from “Zero” to “Connected Agent” in 3 steps.

flowchart TD
    Step1(1. Clone the Pattern)
    Step2(2. Configure Credentials)
    Step3(3. Connect Agent)

    Step1 --> Step2 --> Step3
    
    Step3 -->|Ready| Result([Agent can Read/Write Data])

    style Step1 fill:#eff6ff,stroke:#1d4ed8,stroke-width:2px
    style Step2 fill:#eff6ff,stroke:#1d4ed8,stroke-width:2px
    style Step3 fill:#eff6ff,stroke:#1d4ed8,stroke-width:2px
    style Result fill:#dcfce7,stroke:#166534,stroke-width:2px

How It Works

Section titled “How It Works”

1. Choose Your Legacy Target

Section titled “1. Choose Your Legacy Target”

Find the system you need to unlock (e.g., SAP ECC, Oracle EBS, SOAP Web Services).

2. Copy the MCP Server

Section titled “2. Copy the MCP Server”

Grab our verified server.py and Dockerfile. These act as the “Translation Layer” between your modern agent and the binary legacy protocol.

3. Deploy & Connect

Section titled “3. Deploy & Connect”

Deploy the container to your cloud (Railway/DigitalOcean) or local network. Your agents can now “see” the legacy system as a simple tool.