gorfc-mcp-server

A Model Context Protocol (MCP) server that connects LLMs to SAP systems via RFC (Remote Function Call). It exposes SAP RFC operations as MCP tools over stdio transport, allowing AI agents to ping SAP systems, describe function modules, invoke BAPIs/RFCs, and retrieve call metrics.

Prerequisites

• Go 1.24+
• SAP NW RFC SDK installed at /usr/local/sap/nwrfcsdk/ (headers in include/, libraries in lib/)
• A SAP connection configured either via a sapnwrfc.ini file or environment variables (see Configuration)

SAP NetWeaver RFC SDK Proprietary Notice

The SAP NetWeaver RFC SDK is proprietary software owned by SAP SE. It is not open-source and is subject to specific licensing terms.

Licensing & Access

• No Redistribution: You are not permitted to redistribute the SDK binaries (.dll, .so, .dylib) in your own applications or repositories.
• Customer Access: Access requires a valid SAP license and an S-User ID for the SAP Support Portal.
• Legal Source: Binaries must only be downloaded from the official SAP Software Download Center.

Official Resources

• Product Page: SAP Support Portal - Connectors
• Master Note: SAP Note 2573790 (Installation and Availability for version 7.50).
• Technical Guide: Detailed programming guides are provided within the doc folder of the downloaded SDK package.

Build

make build           # compiles to ./gorfc-mcp-server
make build-windows   # cross-compiles to ./gorfc-mcp-server.exe (Windows x86_64)
make clean           # removes built binaries

The build uses CGO with flags pointing to the SAP NW RFC SDK:

CGO_CFLAGS="-I/usr/local/sap/nwrfcsdk/include"
CGO_LDFLAGS="-L/usr/local/sap/nwrfcsdk/lib"

Cross-compiling for Windows

The build-windows target cross-compiles for Windows x86_64 using MinGW. It requires a Windows build of the SAP NW RFC SDK with headers and libraries available at the configured SDK path and the MinGW-w64 cross-compiler (x86_64-w64-mingw32-gcc).

Install on Debian/Ubuntu:

sudo apt install gcc-mingw-w64-x86-64

Configuration

Two connection modes are supported.

Mode 1 — ini-based (SAP_DEST)

Create a sapnwrfc.ini file (standard SAP NW RFC SDK format) in the working directory and reference the destination by name:

DEST=SID
TYPE=A
ASHOST=sap.example.com
SYSNR=00
CLIENT=100
USER=rfcuser
PASSWD=secret
LANG=EN

Note: sapnwrfc.ini contains plaintext credentials and is gitignored. Never commit this file.

Mode 2 — direct environment variables

Skip the ini file and supply connection parameters directly via environment variables.

Direct application-server connection:

| Variable | Required | Description | | :--- | :--- | :--- | | SAP_ASHOST | Yes | Application server hostname | | SAP_SYSNR | No | System number (default 00) | | SAP_CLIENT | Yes | SAP client / mandant | | SAP_USER | Yes | Logon user | | SAP_PASSWD | Yes | Logon password | | SAP_LANG | No | Logon language (e.g. EN) |

Load-balancing / message-server connection:

| Variable | Required | Description | | :--- | :--- | :--- | | SAP_MSHOST | Yes | Message server hostname | | SAP_MSSERV | No | Message server service / port | | SAP_SYSID | No | SAP System ID | | SAP_GROUP | No | Logon group | | SAP_CLIENT | Yes | SAP client / mandant | | SAP_USER | Yes | Logon user | | SAP_PASSWD | Yes | Logon password | | SAP_LANG | No | Logon language |

Running

ini-based

Pass the destination name via SAP_DEST or as the first CLI argument:

SAP_DEST=SID ./gorfc-mcp-server
./gorfc-mcp-server SID

The SID is the unique, three-character alphanumeric identifier for the SAP system as defined in sapnwrfc.ini:

| SID | Description | | :--- | :-

... View full README on GitHub