github.com/abap2UI5-addons/abap-agent-runtime

ABAP Agent Runtime

An MCP endpoint in ABAP: AI agents operate your apps as the real user.

BetaABAP CloudActiveMIT license

Repository on GitHubInstall with abapGit

What it does

An MCP server inside the SAP system, built on the headless frontend simulator, through which AI agents such as Claude, Copilot Studio or Joule read the screen of an abap2UI5 app as structured data, fill its fields and fire its events. Every call runs as the SAP user of the HTTP request through the app's own main( ), with its validation and authority checks; no second API per app is needed. Apps opt in with the interface z2ui5_if_agent_app, events can be classified allowed, confirm or forbidden, and every call is audited. On top of the endpoint it brings a language model client, generative UI and an in-app copilot, all off by default.

  • MCP Streamable HTTP endpoint with the tools app_list, app_start, app_describe and app_act
  • Agent snapshot v1 of the screen: fields, actions, tables, messages, pending values
  • Runs as the real SAP user through the app's own main( ), no technical user
  • Opt-in per app, events classified allowed/confirm/forbidden, handover to a human
  • Audit log of every call, settings app and audit app included
  • Language model client (Claude API or own provider), generative UI, in-app copilot
  • Disabled after installation until an administrator switches it on

Requirements

  • abap2UI5 (installed first)
  • abap2UI5/headless-frontend (installed before this addon)
  • ABAP Cloud (BTP ABAP environment, S/4HANA Cloud Public Edition) or ABAP Standard 7.50 or higher
  • ABAP 7.02 downport is lint-only in CI, not run on a 7.02 system

Installation

Pull the repository with abapGit into a package of your own. abap2UI5 itself has to be installed first.

https://github.com/abap2UI5-addons/abap-agent-runtime

  1. Install in this order with abapGit: abap2UI5, abap2UI5/headless-frontend, then this repository
  2. Pull from the branch of your platform: standard (ABAP Standard, packages 01-03 and ICF node /sap/bc/z2ui5_agent) or cloud (ABAP Cloud, packages 01, 02, 04); main holds all four packages and does not activate on one system
  3. Not yet in a release; a release will tag the branches as X.Y.Z-standard and X.Y.Z-cloud
  4. After installation the endpoint is disabled: add the first agent administrator with z2ui5_cl_agent_settings=>admin_add( '<USER>' ) and commit
  5. Open the settings app ?app_start=z2ui5_cl_agent_app_admin and switch 'Agents may operate apps' on
  6. ABAP Standard: activate the ICF node /sap/bc/z2ui5_agent in SICF; ABAP Cloud: create an HTTP service with handler class Z2UI5_CL_AGENT_HTTP_CLOUD and expose it through a communication arrangement (to verify)
  7. Opt your apps in with the interface z2ui5_if_agent_app; z2ui5_cl_agent_demo is a complete example

Usage

CLASS zcl_sales_order_app DEFINITION PUBLIC.
  PUBLIC SECTION.
    INTERFACES z2ui5_if_app.
    INTERFACES z2ui5_if_agent_app.
    ...

  METHOD z2ui5_if_agent_app~describe.
    result-description = `Create and change sales orders`.
    result-t_event = VALUE #( ( event = `DELETE*` policy = z2ui5_if_agent_app=>cs_policy-forbidden )
                              ( event = `POST`    policy = z2ui5_if_agent_app=>cs_policy-confirm ) ).
    result-t_sensitive = VALUE #( ( `/MS_PARTNER/IBAN` ) ).
  ENDMETHOD.