onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
Outside the atlasOutside the atlastypeA thing outside the atlas that something inside it depends on or talks to. It is named here so that the dependency or the connection can be an edge; it is not rated, not covered and never an artifact.See every one →

SAP NetWeaver RFC SDK

SAP's native library for calling ABAP functionality and for being called from ABAP. Downloaded from SAP under its own terms rather than from a package registry, so anything built on it carries that prerequisite per platform.

Open support.sap.comchecked

Where it sits

Kind
Software

Used by2

fr0ster/mcp-abap-adtindependently maintained

Optionally used: RFC or SNC connection type selected compiling and running the RFC module needed for RFC and SNC connections to the ABAP system

Functional boundary

Two licences, by which package you install: the standalone server, `@mcp-abap-adt/core`, is AGPL-3.0-only, a licence to read before shipping anything built around it; the library, `@mcp-abap-adt/lib`, is Apache-2.0. The destination model also expects service keys sitting in a local directory, which is a secrets decision to make deliberately.

pyrfc-mcpindependently maintained

Optionally used: a real SAP system is called; demo mode replaces the SAP transport with a synthetic backend the native library PyRFC binds to, and the prerequisite the README sends a reader to its setup document for before any live call

Functional boundary

Real SAP calls need the proprietary [SAP NetWeaver RFC SDK](external:sap-nw-rfc-sdk) and the `pyrfc==3.3.1` release the README calls archived and yanked, on Python 3.11, so without those only the demo backend answers. Not over HTTP as it stands: credentials are read from the environment for stdio, and the README says not to expose the server over HTTP without implementing the MCP authorization specification and deployment-level rate limiting. Multi-tenant auth and RBAC beyond the one server-wide policy, rate limiting, metrics and tracing, and deployment packaging are listed as not built. The result limits protect the client and not the system, since the README states they cannot reduce work already performed inside SAP, and the MCP tool annotations that describe read and write risk are advisory metadata rather than an authorisation boundary, so the service account's `S_RFC` and table authorisations are still what decides.

Details

Graph2
← POINTS HERE
optionally used byfr0ster/mcp-abap-adt
optionally used bypyrfc-mcp
POINTS OUT →
nothing yet
For your agent
Ref
external:sap-nw-rfc-sdk
JSON
/externals/sap-nw-rfc-sdk.json
MCP
Connecting an agent