AGENTIC DEVELOPMENT INSIDE SAP

Your agents.
Your SAP.
Your rules.

Give your AI agents the means to act inside your SAP system. From code to operations, with the authorizations and traceability your teams expect.

  • 01 Inside SAP
  • 02 Native authorizations
  • 03 Audit trail
  • 04 Your MCP client
Diagram: your AI agent, in your MCP client with the Klystron plugin and a local Git repository, calls the Klystron server installed in your SAP system over MCP on HTTPS, with its read and write modules; your rules apply on the SAP side: PFCG roles, native services, SLG1 log.

01 / THE PLATFORM

One platform.
Three pillars.

Klystron connects your MCP client to the SAP application server. Native tools to act, skills to guide the agent, shared knowledge to improve. Each pillar is detailed below.

01PILLAR

Native SAP tools.

The MCP server is written in ABAP and runs inside your system. ABAP development, quality, transports, customizing, security, Basis operations and integration, exposed as typed tools. Every object is also a file in SAP’s format, ready for Git.

The server inside SAP
02PILLAR

An agent guided by SAP skills.

A plugin for your MCP client. A coordinator pairs each task with a process and an SAP domain. Diagnostics, integration and Basis stay read-only; writing goes through the transport protocol.

COMING SOONAdvanced skills and agent teams.

The agentic plugin
03PILLARCOMING SOON

Shared knowledge.

The Central Hub will turn field findings into verified, signed documentation redistributed to participating systems. You will choose your contribution scope.

The Central Hub

02 / USE CASES

Real work.
In the real system.

Read the context. Propose a change. Verify it. Four scenarios; the first comes from a real session.

REAL SESSION · CODEX + KLYSTRON PLUGIN · SERVER V2SESSION OF 19 OCT 2026
BRIEF COMPLETE
68 min
6 h 40 min session, breaks included
YOUR MESSAGES
11
SAP CALLS
≈ 460
OBJECTS DELIVERED
38 · package ZBC_PRT
YOU

“Read BRIEF.md and build it.”

CODEX AGENT

Creates the transport request and the ZBC_PRT package. Design choice: binary IPP messages over SAP’s HTTP client, with separate checks for HTTP and IPP errors. Any change to SAP standard will be put to you for approval.

abap_create_transportabap_write_package
CODEX AGENT

The codec’s 8 unit tests are green: byte order, UTF-8, repeated values, malformed messages. Hook point found in the spool: RSPOLPRF’s MAIL2 callback already receives the print file.

klystron sync pushabap_run_unit_testsabap_read_file
CODEX AGENT

“May I activate enhancement ZBC_PRT_MAIL at the start of SAP program RSPOLPRF, FORM MAIL2? It redirects only output devices registered by ZBC_PRT; other devices continue through SAP’s existing code.”

request_user_input
YOU

“Approve this scoped enhancement.”

CODEX AGENT
INCIDENT REPORTED

Printing bypasses the hook: the enhancement-writing tool stored an invalid execution mode (“I”, while SAP only knows S and D). The agent fixes it through SAP’s enhancement API and reports the plugin defect itself.

abap_read_enhancement_codemcp_report_incident
CODEX AGENT

After one last fix (COMMIT WORK is forbidden in this callback), automatic printing works: the SAP spool request reaches the CUPS test queue, the job completes and SAP shows the status “completed”.

abap_read_dumpabap_classrun
CODEX AGENT

A print to a non-existent queue shows up as an error in SAP, with CUPS’s message in the spool log. At 10:38 the brief is complete: sync, printing, visible failure, ATC without priority 1 or 2, one transport.

abap_classrunabap_read_spool
YOU

“Would PDFUC not be better? Can you investigate that functional gap and propose something?”

CODEX AGENT

PDFUC is the right baseline for Unicode, but carries neither colour nor duplex. Proposal: synchronise each printer’s capabilities and translate each print’s choices into IPP attributes.

web searchabap_classrun
CODEX AGENT

Reading back the document CUPS actually received, the agent sees Cyrillic and Chinese replaced by “#”, although SAP’s preview was correct. Fixed with SAP’s standard PDF conversion, per call, without any system parameter.

abap_classrunabap_read_spool
CODEX AGENT

18 unit tests green, ATC without priority 1 or 2 across 30 objects, all in one transport. At your request, a colour duplex page is printed on a real HP printer.

abap_run_unit_testsabap_run_atc
  1. Brief
  2. IPP protocol
  3. Sync
  4. Printing
  5. QA
  6. Capabilities
The code on GitHub · coming soon Quotes shortened and summarised. Addresses, hosts and identifiers removed. These sessions are also a test bench: in real use, the agents themselves report the defects they hit in the plugin.

03 / HOW IT WORKS

The entry point is
inside your system.

Three mechanisms, in the order of the pillars: the server that exposes the tools, the agents that use them, the hub that builds on what they learn.

OVERVIEW

A reference architecture.

An example: one agent, two SAP landscapes. Development is read and write; quality assurance and production are read only.

Klystron reference architecture: a single AI agent, with a local Git repository in AFF format, connects over MCP to two SAP landscapes. In each landscape, the development system carries the read and write modules of the Klystron server; quality assurance and production carry the read module only. Transports link DEV, QA and PROD. The Central Hub, optional and coming soon, shares verified knowledge.
Example setup: the number of landscapes and systems is free, and you choose which systems receive the write module. Click to enlarge. Drawn with the SAP BTP solution diagram kit.
3.1 / PILLAR 01

The server inside SAP.

An ICF service exposes the tools. Execution, checks and log stay on the SAP side.

YOUR AI ENVIRONMENT WORKSTATION OR CI
YOUR AGENT MCP client + Klystron plugin The agent and the SAP skills. It reads and writes the repository files.
YOUR GIT REPOSITORY
zsd_pricing/one folder = one package
zcl_discount.clas.jsonheader · SAP format
zcl_discount.clas.abapsource
zcl_discount.clas.testclasses.abaptests
zsd_price.tabl.jsontable · SAP format
zi_sd_price.ddls.acdsCDS view
zi_sd_price.bdef.abdlRAP behavior
zsd_price_var.vari.jsonKlystron format
Your SAP objects, as files, on your side. Version, review, open merge requests, with native Git tools.
MCP / HTTPS
Typed tool calls
DESERIALIZEWrite a file: checked, written if the fingerprint matches, read back, activated.
SERIALIZERead a package: its objects become files, one fingerprint per file.
Results, explained refusals, log
YOUR SAP SYSTEMABAP APPLICATION SERVER
klystron.The MCP server, in ABAP, behind an ICF service.
Typed tools
Bounded actions
THE REPOSITORYCustomer objects Z / Y
Classes, interfaces, programsTables, domains, data elementsCDS viewsRAPFunction modulesVariantsPFCG rolesTransports

Every object has a file name and a format: the one SAP publishes, ABAP File Formats, where it exists; a Klystron format in the same convention otherwise, distinguishable by its version (formatVersion 900). Serialization is SAP’s own: transformations generated from the ABAP types, canonical JSON identical to the SAP handler’s.

AuthorizeSAP roles / PFCG
ExecuteNative SAP services
LogSLG1 log
TOOLS BY DOMAIN

The whole system, not just the code.

Each domain is exposed through typed tools, under the SAP authorizations of the signed-in user. In blue, the plugin skill that puts them to work; dashed, the skill still to come. Either way, the tools are available on the server.

ABAP DEVELOPMENT

From code to RAP service.

Classes, programs, functions, dictionary, CDS, RAP, enhancements and BAdIs, texts, packages, transactions, Adobe forms. Read, write, activate.

abap-dev
QUALITY AND DIAGNOSIS

Check, understand.

Syntax, ATC, ABAP Unit, ST22 dumps, versions, inactive objects, where-used, code search, SAP Notes.

incident-analysis + quality-read
TRANSPORTS

Deliver through CTS.

Requests and tasks: creation, assignment, contents, simulation and release.

transports
CUSTOMIZING

Configuration too.

Table contents, customizing views, IMG, BC Sets and their activation, under a customizing request.

skill · coming soon
SECURITY AND ROLES

Authorizations, with tools.

PFCG roles and profiles, roles built from a trace, SU24 values, authorization objects, users and role holders, security audit.

role skills · coming soon
BASIS OPERATIONS

Observe, schedule.

Work processes, updates, locks, system log, database, backups, CCMS, RFC queues, spool; jobs and ABAP daemons.

basis-observation + basisjobs · coming soon
INTEGRATION

IDocs and web services.

IDoc basic types, segments and extensions, IDoc status, web services and proxies, WSDL, RFC destinations.

integration-inspection + integration
INCIDENT REPORTING

Defects report themselves.

Tool failures, missing capabilities, attempts to bypass a permission: the agent reports them to the server’s audit log.

tool-reporting

Explicit permissions.

A defined scope for each domain and activity. Reading, changing and executing are separate permissions, checked on the server.

A clear contract.

Typed inputs and outputs, in the vocabulary of the files. The agent knows what to send, what to expect and why a request is refused.

Safe writes.

Syntax check before anything is saved; fingerprint and conditional write against concurrent overwrites; read-back after writing.

No middleware.

The AI model remains your client’s: the choice of provider and the data sent to it are governed by your policy.

3.2 / PILLAR 02

The agentic plugin.

A plugin for your MCP client: a coordinator, SAP skills by process and by domain, and the server’s tools.

THE PLUGIN · MCP CLIENT SIDETHE SERVER · INSIDE SAP
LEVEL 1 · COORDINATIONThe coordinatorFor each task, it picks a process skill and a domain skill, then the tools that are needed.
klystron-core+ agent teams · coming soon
LEVEL 2 · SAP PROCEDURESThe SAP skillsThe process carries the method, the domain the SAP knowledge and a focused tool catalogue. Two cross-cutting skills complete them.
abap-dev + transportsincident-analysis + quality-readintegration-inspection + integrationbasis-observation + basistool-reportingshared-memorycli · optional+ advanced skills · coming soon
LEVEL 3 · KLYSTRON SERVER INSIDE SAPThe native toolsThe MCP server exposes typed tools by domain; authorizations, execution and log stay on the SAP side (see 3.1).
ABAP developmentQuality and diagnosisTransportsCustomizingSecurity and rolesBasis operationsIntegration

Why this stack. Loading every SAP tool into an agent’s context wastes context and says nothing about ordering rules or risks. Skills bring the procedure and a narrow tool catalogue; the coordinator loads only the pair the task needs; SAP controls frame execution.

THE PLUGIN’S GUARDRAILS

Write, read, deliver, report.

Rules enforced by the plugin, on top of the SAP authorizations of the signed-in user.

  1. 01 / WRITE

    Transports skill

    Under the transport protocol.

    Any action that writes, creates, deletes or releases in SAP is blocked until the transport protocol is loaded, for MCP tools and the command line alike.

    THE ONLY PROCESS THAT WRITESABAP development; a write always covers the whole file.
  2. 02 / READ

    Diagnostics · integration · Basis

    Read-only by design.

    Every read goes through its process skill. Dump diagnostics, interface inspection and Basis observation change nothing.

    OUTCOMEA documented finding, for your teams to decide on.
  3. 03 / DELIVER

    Transports skill

    Release with full knowledge.

    Simulation before release; ATC and unit tests before releasing code; deletion only with the request that holds the object, after confirmation.

    SERVER SIDEWrite tools refuse objects outside the customer namespace (Z, Y).
  4. 04 / REPORT

    tool-reporting skill

    Defects report themselves.

    The agent itself reports tool failures, missing capabilities and any attempt to work around a permission.

    IN A REAL SESSIONSee the first use case: the agent reports a plugin defect and works around it cleanly.

What the guardrails do not do. They block or stay silent; they never grant a right. The real limit remains the SAP authorizations of the signed-in user and the permissions of your MCP client; depending on the client, these rules are enforced by hooks or carried by the skills’ instructions.

3.3 / PILLAR 03 COMING SOON

The Central Hub.

A loop: what one customer learns comes back to all the others.

Knowledge loop: the agents of several customers write their documentation and share it with the Central Hub, which consolidates the knowledge and redistributes it to every customer.
  1. 01 / AT EACH CUSTOMERThe agents document.

    Findings, incidents, release quirks: every mission leaves documentation behind.

  2. 02 / TO THE HUBThey share it.

    Signed, encrypted contributions, within the scope you chose.

  3. 03 / AT THE HUBThe hub consolidates.

    Triage, reproduction on reference systems, human review, signed publication.

  4. 04 / BACK TO EVERY CUSTOMER ↻The knowledge comes back.

    Business documentation, known limits and verified solutions, for the teams and their agents. Then the loop starts again.

The Central Hub is in preparation. The native tools and the plugin work without it; sharing will be enabled as you need it.

04 / WHY NOW

AI moves forward.
So does your codebase.

Teams need to modernize code, prepare the transition and keep systems running. Our approach: give agents practical access to the system, within a framework SAP teams can examine.

THE TRANSITION IS ALREADY HERE
2027→ 2030

One timeline.
Years of code.

Mainstream maintenance for core Business Suite 7 applications ends in late 2027; optional extended maintenance runs through the end of 2030.

SAP maintenance strategy
AN ECOSYSTEM GAINING NEW TOOLS

The protocol opens the door.
The product does the work.

MCP connects your agents to SAP. Klystron gives them the tools, the method and the knowledge to act.

SAP on the agentic evolution

05 / THE RIGHT QUESTIONS

Let’s get practical.

Data, rights, hosting and its place in your toolchain.

Do we need an intermediary server?

No. The MCP server is written in ABAP and runs inside the SAP application server, behind an ICF service. You then connect your MCP client. The agent and its model keep their own hosting and network requirements.

What data is sent to the AI model?

Results your MCP client sends to the model may contain code or system data. A server inside SAP does not mean the model is local. The client, AI provider, authorized domains and accessible data are part of the pilot scope.

Which permissions does the agent use?

The SAP identity used by the client, the applicable native permissions and the server’s authorizations by domain and activity. Any technical account must be explicitly authorized. Validate the pilot scope with the account that will actually be used.

Is the hub required to use the SAP tools?

No. The Central Hub opens soon; the native SAP tools and the plugin work without it. Once it is open, you enable knowledge exchange as needed, with an explicit configuration and contribution scope.

Does the Central Hub control my agents remotely?

No. The Central Hub, coming soon, will share verified knowledge. Agents work in their own environment, under your system’s SAP controls. The hub will collect contributions, coordinate reproduction and review, then distribute signed documentation. Your teams retain control of execution and shared data.

Does Klystron replace abapGit?

No. abapGit remains a useful and important part of your infrastructure. For its agents, Klystron needed a method closer to native Git: the server synchronises objects with a local repository, directly in SAP’s ABAP File Formats (AFF) wherever the object allows it. Agents and teams get the full power of native Git tools: diff, branches, review, merge requests. Your delivery pipelines remain your own.

Does Klystron replace Joule?

Klystron is not an assistant. Through MCP, it gives the assistant of your choice native tools inside your system, agents and SAP skills. The client, the model and the data sent are governed by your policy; no Klystron service sits in between.

How does Klystron fit into my SAP landscape?

Deployment is scoped to your release, components and use cases, on ECC or S/4HANA. A development or test pilot validates scenarios and permissions with your teams. Production rollout follows your change management and operations processes.

How do we start a pilot?

Choose a release, a domain and a measurable scenario: an ABAP test, findings analysis or a role proposal.

06 / LET’S START WITH A REAL USE CASE

Your system has potential.
Give it an agent.

Prepare a pilot by email

Or write directly to contact-klystron@thirion.fr

One system. One scope. One first use case.