Neptune DXP - SAP Integration Hub 1.1.0 framework release notes
June 24, 2026
Enhancements
MCP server runtime implementation
A new MCP server runtime has been added to the SAP Integration Hub framework. The SAP Integration Hub system now exposes an HTTP endpoint implementing the Model Context Protocol (MCP), through which any MCP-compatible client, routed via a Neptune DXP - Open Edition system, can invoke custom ABAP business logic running in the SAP back end.
The runtime is responsible for:
-
Delivering tool metadata to client agents according to the MCP protocol
-
Executing tool requests as triggered by the agent runtime
-
Evaluating tool configurations stored in the SAP back end at request time
JSON-RPC runtime handling
Underlying protocol-level handling for JSON-RPC — the transport layer of MCP — has been implemented, covering the full HTTP request/response cycle. This underpins all MCP server interactions between the SAP back end and consuming agents.
Design-time artifacts & CRUD API
New MCP server design-time artifacts have been introduced within the Integration Hub framework, including a full CRUD API for managing tool configurations. These configurations are persisted on the SAP system and evaluated at runtime to serve MCP protocol metadata and execute tool calls.
ABAP class/method binding
Each MCP tool configuration binds to a specific ABAP class and method in the SAP back end. The tool definition captures:
-
The selected ABAP class and method
-
A structured payload schema
-
A natural-language description of the tool’s capabilities
This makes existing ABAP business logic discoverable and executable by agent runtimes in a controlled, protocol-compliant way.