SkillSkilltypeA procedure an agent follows. Indexed here, never written here.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

claude-sap-kit

A Claude Code plugin of three skills that extends arc-1 with five Custom_* tools for an on-premise ABAP system: running a report and reading its ALV as JSON, previewing a NAST message as PDF, and reading, writing and replacing SmartForms as XML.

arc-1 reaches ABAP objects through ADT, and three things a developer otherwise does in SAP GUI sit outside that surface: running a report, looking at what a print program produced, and changing a form. This kit adds them as five tools an ARC-1 extension registers. Custom_LaunchReport submits a report by name or transaction with a variant or selection values and returns the ALV as JSON or the list as text; Custom_PrintPreview runs the print program of a NAST message to spool and saves the PDF, even for a form not yet configured in NACE; Custom_SmartFormRead, Custom_SmartFormWrite and Custom_SmartFormReplace download a SmartForms as XML, upload it back as a ZAI_* copy in $TMP with check, activation and function module generation, and then replace the customer form under a transport request in a prepare and execute pair. An ARC-1 extension can only make HTTP calls, so the tools reach remote-enabled function modules through the standard /sap/bc/soap/rfc service, and the ABAP half — classes and a function group under a prefix that defaults to ZAI and can be changed by a script, with ABAP Unit tests the installation runs on the system — is installed by the sap-arc1-kit skill. Two further skills carry the workflow rather than the reach: sap-report-launcher for running and comparing reports, sap-smartform-xml for reading, editing and checking a form. The form replacement is the path with conditions on it: a transport request the user gives, a prepare step with a summary and a one-time token, refusal if the original or the copy changed in the meantime, an XML backup before every overwrite, and allowed packages, allowed requests and the author check configured in the project .mcp.json.

Facts

Last pushLicenceMIT

Where it sits

Lives in
Provides
Agent access to your codeABAPAgent access to your codecapabilityLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from [MCP servers](capability:mcp-servers), which is a protocol adapter on your own running service, and from [agent guidance](capability:agent-guidance), which is knowledge handed over as files rather than read from the thing itself.Agent guidanceABAPAgent guidancecapabilityPackaged knowledge you hand a coding agent so it gets a framework right unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from [agent access to your code](capability:agent-code-access), where the agent reads the real project instead of being handed a file about it.
Requires
arc-1arc-1artifactthe MCP server the extension is loaded into and the session it calls the SAP system from; the five tools exist only inside it
Optional
SAP S/4HANASAP S/4HANAoutside the atlasthe on-premise or private cloud SAP system the kit's ABAP objects are installed on and the reports and forms run againstSAP ERP (ECC)SAP ERP (ECC)outside the atlasthe on-premise SAP system the kit's ABAP objects are installed on and the reports and forms run againstruntime system

Who is behind it

silvius1996silvius1996PersonMaintains this
In the atlas: maintains 1, contributes to 1
@silvius1996
maintainer

Before choosing this

Conditions

PracticalFunctional boundary

Not for S/4HANA Public Cloud or the BTP ABAP environment, where the README states there is no SUBMIT, NAST or SOAP-RFC; the floor elsewhere is SAP_BASIS 7.50, the /sap/bc/soap/rfc service active, and an SAP user with S_RFC on the kit's function group as well as the authorizations for the reports and the spool. Print output is NAST messages only, so S/4 Output Management through BRF+ or APOC is outside it, and editing covers SmartForms alone, with Adobe Forms and SAPscript previewable but not editable. A report that opens a popup, calls a screen or is a dialog transaction cannot be run at all.

PolicySAP API Policy 4.2026a§ 1.1, 1.2, 2.2.2from Agent access to your codeAn MCP server calls ADT or another SAP API of a running system for an agent.
  • § 1.1 Published APIs. Published APIs are made available for the documented purposes identified by SAP, including integration, extensions and data exchange.
  • § 1.2 Non-Published APIs. Customer and third-party applications must not access non-published APIs except where documentation permits it or SAP otherwise authorizes it.
  • § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.

An agent that plans and executes ADT calls is the case section 2.2.2 names. Check that the endpoints are published for the intended use, and that the design runs within a pathway SAP identifies for it.

SAP API Policy 4.2026a →

What it declares

Every artifact

Type
Skill
Origin
Independently maintained

As a skill

Distributed through
Agent plugin marketplace

For agent access to your code

Read
sourcesearchwhere-usedDDICCDStable data
Change
writecreateactivatetransportsgit
Check
syntaxATCABAP Unit
Run
run codedumps
property statedstated nonot said

Connections6

claude-sap-kit connectionsclaude-sap-kitPROVIDES→ provides2provides stated Adds five tools to what an agent can reach on a classic ABAP system beyond ADT: submitting a report and reading its ALV as JSON, running a NAST message's print program and fetching the spool PDF, and reading, writing and replacing SmartForms as XML. silvius1996/claude-sap-kit — README: https://raw.githubusercontent.com/silvius1996/claude-sap-kit/main/README.md silvius1996/claude-sap-kit — repository description: https://github.com/silvius1996/claude-sap-kitAgent access to your codeprovides stated Three skill directories beside the tools: `sap-arc1-kit` walks the installation on an SAP system, `sap-report-launcher` covers running and comparing reports, `sap-smartform-xml` covers reading, editing and checking a form. silvius1996/claude-sap-kit — README, Repository layout: https://raw.githubusercontent.com/silvius1996/claude-sap-kit/main/README.md silvius1996/claude-sap-kit — README, Repository layout: https://raw.githubusercontent.com/silvius1996/claude-sap-kit/main/README.md silvius1996/claude-sap-kit — README, Installation: https://raw.githubusercontent.com/silvius1996/claude-sap-kit/main/README.mdAgent guidanceNEEDS→ connects to1connects to stated calls the remote-enabled function modules the kit installs, so the report runs, the spool PDF is fetched and the SmartForms XML is read or written in the system itself silvius1996/claude-sap-kit — README, How it works: https://raw.githubusercontent.com/silvius1996/claude-sap-kit/main/README.md silvius1996/claude-sap-kit — README, Requirements: https://raw.githubusercontent.com/silvius1996/claude-sap-kit/main/README.mdABAP platformInterface: SOAP web services fromRFC function modules · soap→ needs1needs stated the MCP server the extension is loaded into and the session it calls the SAP system from; the five tools exist only inside it silvius1996/claude-sap-kit — README, Requirements: https://raw.githubusercontent.com/silvius1996/claude-sap-kit/main/README.md silvius1996/claude-sap-kit — README: https://raw.githubusercontent.com/silvius1996/claude-sap-kit/main/README.mdarc-1→ optionally needs2optionally needs stated If: the SAP system is ECC 6.0 EHP8, as an alternative to S/4HANA the on-premise SAP system the kit's ABAP objects are installed on and the reports and forms run against claude-sap-kit README: https://github.com/silvius1996/claude-sap-kitSAP ERP (ECC)ifoptionally needs stated If: the SAP system is S/4HANA (on-premise or private cloud edition), as an alternative to ECC 6.0 EHP8 the on-premise or private cloud SAP system the kit's ABAP objects are installed on and the reports and forms run against claude-sap-kit README: https://github.com/silvius1996/claude-sap-kitSAP S/4HANAif

Install

/plugin marketplace add silvius1996/claude-sap-kit
/plugin install sap-arc1-kit@claude-sap-kit
The config you actually write
"env": {
  "ARC1_PLUGINS": "<absolute path>/arc1-extension/dist/index.js",
  "SAP_ALLOW_PLUGIN_RAW_WRITES": "true"
}

Copied from silvius1996/claude-sap-kit — README, Installation, read . Not run by the atlas.

README

quoted from silvius1996/claude-sap-kit under MIT, read
silvius1996/claude-sap-kit/README.mdOn GitHub

claude-sap-kit

Listed in SAP AI MCP Servers & Claude Plugins

Tools and skills that let Claude Code work on an on-premise SAP system without SAP GUI, built as an extension of ARC-1.

ARC-1 already gives Claude read and write access to ABAP code through ADT. This kit adds what ADT does not cover: running reports, previewing print output and editing SmartForms and Adobe forms.

⭐ If you find it useful, please star the repo: it helps other SAP developers find it. Questions and ideas are welcome in Issues.

What you can ask Claude

  • "Run MB52 for plant 1001, storage locations M001 to M003" → runs the report and reads the ALV as JSON.
  • "Compare ZMM_STOCK with its copy on the same filters" → same selection on both, row-by-row comparison.
  • "Show me the PDF of delivery 80012345" → preview of the NAST message, nothing is printed.
  • "On the delivery note, replace the sender address with a fixed text" → Z copy of the SmartForms, XML edit, PDF preview and comparison with the original.
  • "OK, move the change to the original form in request DEVK900123" → controlled replacement, with backup, summary and explicit confirmation.
  • "On the order confirmation (Adobe form), make the footer text smaller" → Z copy of the form, XDP edit, PDF preview and comparison with the original.

How it works

Claude Code ──MCP──▶ ARC-1 ──▶ extension (9 Custom_* tools) ──HTTP /sap/bc/soap/rfc──▶ remote-enabled FMs ZAI_* ──▶ ABAP classes
ToolWhat it does
Custom_LaunchReportSUBMIT of a report (by name or transaction) with a variant and/or selection values; returns the ALV as JSON or the list as text
Custom_PrintPreviewRuns the print program of a NAST message to spool and saves the PDF, even with a SmartForms or Adobe form not yet configured in NACE
Custom_SmartFormReadDownloads the XML of any SmartForms
Custom_SmartFormWriteUploads an XML as a ZAI_* copy in $TMP, with check, activation and FM generation
Custom_SmartFormReplaceReplaces a customer form with the approved copy, under a transport request, in two steps (prepare → execute)
Custom_AdobeFormReadDownloads any Adobe form (SFP) as three files: form XML without layout, layout XDP, interface XML
Custom_AdobeFormWriteUploads form XML + XDP as a ZAI_* copy in $TMP, with activation and FM generation
Custom_AdobeInterfaceWriteUploads an interface XML as a ZAI_* form interface in $TMP (new, or updated in place so the forms using it stay linked), with activation
Custom_AdobeFormReplaceGives a customer Adobe form the layout of the approved copy, in place, under a transport request, in two steps (prepare → execute); refused if the copy differs in anything else

ARC-1 extensions can only make HTTP calls, so the tools call remote-enabled function modules through the standard SOAP-RFC service.

Repository layout

.claude-plugin/                  Claude Code plugin and marketplace
skills/
  sap-arc1-kit/                  skill: installs the kit on an SAP system
    assets/abap/                 ABAP classes and function group (default prefix ZAI)
    assets/arc1-extension/       ARC-1 extension in TypeScript, with tests
    scripts/set_prefix.py        changes the object prefix (e.g. ZAI → ZXYZ)
  sap-report-launcher/           skill: how to run and compare reports
  sap-smartform-xml/             skill: how to read, edit and check SmartForms
  sap-adobe-form/                skill: how to read, copy, edit and check Adobe forms

Requirements

  • SAP_BASIS 7.50 or later, on-premise or private cloud: ECC 6.0 EHP8 and S/4HANA (all releases). Tested live on S/4HANA 2025 (SAP_BASIS 816) and ECC 6.0 EHP8 (SAP_BASIS 750); the ABAP sources avoid newer constructs. On ECC the class /UI2/CL_JSON must exist (used for the ALV output). Not for S/4HANA Public Cloud or the BTP ABAP Environment (no SUBMIT, NAST or SOAP-RFC there).
  • ARC-1 1.4.0 or later, configured in Claude Code with writes enabled.
  • SICF service /sap/bc/soap/rfc active.
  • For the Adobe forms tools: Adobe Document Services (ADS) configured (standard report FP_TEST_00).
  • SAP user with S_RFC on the kit function group, plus the authorizations for the reports to run and for spool requests.
  • Node.js 22.19+ or 24 (to build the extension) and Python 3 (for the scripts).

Installation

  1. Plugin (the four skills), from Claude Code:
    /plugin marketplace add silvius1996/claude-sap-kit
    /plugin install sap-arc1-kit@claude-sap-kit
    
  2. Kit on the SAP system: with ARC-1 connected, ask Claude "install the ARC-1 kit on this system". The skill sap-arc1-kit goes through every step: prefix, creation and activation of the ABAP objects, ABAP Unit tests, build of the extension and .mcp.json configuration. The steps are also described in skills/sap-arc1-kit/SKILL.md if you prefer to do them by hand.
  3. Restart Claude Code: the Custom_* tools appear after the restart.

Minimal extension configuration in the ARC-1 server of .mcp.json:

"env": {
  "ARC1_PLUGINS": "<absolute path>/arc1-extension/dist/index.js",
  "SAP_ALLOW_PLUGIN_RAW_WRITES": "true"
}

Safety

The kit is designed to be safe even when an AI is driving it:

  • standard SAP objects are never changed;
  • SmartForms and Adobe forms are written only as copies with the kit prefix, in $TMP, created by the logged-on user; every overwrite first saves a local backup;
  • replacing a customer form needs a transport request given by the user, a prepare step with a summary and a one-time token, and is refused if the original or the copy changed in the meantime; for Adobe forms only the layout is replaced, in place, and only when the copy differs from the original in nothing else;
  • allowed packages, allowed requests and the author check are configured in the project .mcp.json;
  • nothing is ever deleted, with one exception: the SAP API cannot replace the context of an Adobe form, so an existing ZAI_* copy (own, in $TMP) is deleted and created again after its backup;
  • the skills ask for confirmation before running reports or print programs that change data.

Business data and the model

What a tool returns goes into Claude's context, and from there to the model provider under your agreement with them. The tools are not equal from this point of view:

ToolWhat reaches the model
Custom_SmartFormRead, Custom_SmartFormWrite, Custom_SmartFormReplace, Custom_AdobeFormRead, Custom_AdobeFormWrite, Custom_AdobeInterfaceWrite, Custom_AdobeFormReplaceForm definitions: layout, texts and code. Customer code, but no business documents
Custom_LaunchReportBusiness data: the report output (ALV rows or list), for example stock, prices, customers
Custom_PrintPreviewBusiness data: the printed document, with addresses, prices and quantities. The PDF is saved locally and reaches the model when Claude reads or compares it, as the skills do to check a form

Test systems are often copies of production, so "only development and test systems" does not keep real data out. Decide per system and per customer:

  • where business data must not leave the system, keep the report and preview tools off, for example with a deny rule in the project's .claude/settings.json (arc1 is the name of the ARC-1 server in .mcp.json):
    {
      "permissions": {
        "deny": ["mcp__arc1__Custom_LaunchReport", "mcp__arc1__Custom_PrintPreview"]
      }
    }
    With ARC-1 in read-only mode all the kit tools are off, because they need writes enabled;
  • where the customer accepts it, keep selections narrow (one material and plant, not the whole stock), so that only the data needed for the task is read.

Limits

  • Print output with NAST messages only: no S/4 Output Management (BRF+/APOC).
  • Editing: SmartForms (copies and replacement of the original) and Adobe forms (copies, ZAI_* interfaces and replacement of the layout of the original in its original language; context, interface and translations of a customer form are changed in SFP / SE63). SAPscript can be previewed but not edited.
  • Reports that open popups, CALL SCREEN or dialog transactions cannot be run.

Tests

cd skills/sap-arc1-kit/assets/arc1-extension
npm ci --ignore-scripts
npm test

The ABAP classes come with ABAP Unit tests: the installation skill runs them on the system.

License

MIT. ARC-1 is a separate project, also under the MIT license.

MIT, read

History

Latest

v0.7.0

Other 8

Notes

Replacement of a customer Adobe form with the approved copy, for layout changes. Tested live on S/4HANA (SAP_BASIS 816) with ADS on a Z copy of FP_TEST_00 in a transportable package; on 7.50 checked with abaplint only (the LOAD parameters used for the replacement are not verified there yet).

  • Custom_AdobeFormReplace: gives a customer Adobe form (Z*/Y*, in a transportable package) the layout of the approved ZAI_* copy, recording it in the given transport request. Two steps as for SmartForms: prepare (checks, XML/XDP backup of the original, summary with the owner of the request, one-time token; no writes) and execute (with the token, refused if the original or the copy changed). The layout is written in place (CL_FP_WB_FORM=>LOAD in write mode, SET_LAYOUT_DATA, SAVE, activation): the SAP API cannot replace the context of a form, so the copy is refused if its form XML differs from the original outside the layout (context, interface, properties), with the differing lines. Also refused: a task instead of its request (the message names the request), an original with an inactive version, project rules of .mcp.json.
  • Fixes from the live test of Custom_AdobeFormReplace:
    • execute ended in a short dump (DYNPRO_SEND_IN_BACKGROUND) when the original language of the form was not the logon language of the SOAP call: locking the form asked in a popup whether to change the original language. The form is now opened in its original language without language check and without dialogs (LOAD with I_LANGUAGE, I_SUPPRESS_LANGUAGE_CHECK, I_ORDERNUM, I_DARK); this also writes the layout of the original language, not a new translation in the logon language.
    • prepare refused a copy with a changed layout because it compared the layouts per language (<LAYOUTT> in the form XML), which SAP generates from the layout. They are no longer compared.
    • The summary no longer says that translated layouts stay as they are: after execute SAP generates the layouts of the other languages again from the new one, as when the form is saved in SFP.
  • Skill sap-adobe-form: SAP writes the <tags> of the XDP (texts for the translation) again from the texts of the template at every write, so a text is changed in the template, not in <tags>.
  • Custom_AdobeFormRead: object ids renumbered in document order and CACHE_INFO emptied, as abapGit does, so the same form always gives the same XML and copy and original can be compared line by line.
  • Fix: with ZAI_CHECK_AUTHOR=false the author check of Custom_SmartFormReplace stayed on, because SOAP-RFC drops the empty parameter and the function module default 'X' applied. A check switched off is now sent as '-'.
  • Fix: the object prefix may have at most 8 characters, not 10: with 9 or 10 the function module <PREFIX>_ADOBE_INTERFACE_WRITE (since 0.6.0) exceeded the 30 characters allowed by SAP. set_prefix.py refuses longer prefixes.
  • README: Adobe form interfaces are no longer read only (Custom_AdobeInterfaceWrite, since 0.6.0).
  • New remote-enabled FM ZAI_ADOBE_FORM_REPLACE; 8 more ABAP Unit tests (harmless) in ZAI_CL_ADOBE_FORM (22 in all); 36 Node tests.
  1. v0.6.0

    Other 6

    Notes

    Adobe forms (Interactive Forms by Adobe, transaction SFP). Tested live on S/4HANA (SAP_BASIS 816) with ADS: read of FP_TEST_00 and of the sales document form SD_SDOC_FORM01, copy, preview of an order with the copy (same text as the original), text change in the XDP, preview and rollback; a new printed field read from a Z form interface; update in place of that interface (initialization code), preview, creation of a second interface, refusals and rollback from the backup. Not tested live on SAP_BASIS 7.50 (ECC) yet: the ABAP sources pass abaplint with the v750 syntax only.

    • Custom_AdobeFormRead: downloads any Adobe form as three files, as abapGit does: the form XML without layout (<NAME>.form.xml, one element per line), the layout as XDP (<NAME>.xdp) and the form interface (<INTERFACE>.interface.xml, found in the form XML or passed explicitly).
    • Custom_AdobeFormWrite: uploads form XML + XDP as a ZAI_* copy in $TMP of the logged-on user, activates it and returns the generated function module. Checks Adobe Document Services (ADS) first. The SAP API updates the layout of a loaded form in place but cannot replace its context (abapGit deletes and creates the form again too), so an existing copy is deleted and created again after a local backup; customer and standard forms are never written. The timeStamp of the xdp element is renewed at every write, as LiveCycle Designer does: ADS caches the template under timeStamp and uuid, and a changed layout with the old timeStamp was printed unchanged.
    • Custom_AdobeInterfaceWrite: uploads an interface XML (parameters, global data, types, initialization code, reference fields) as a ZAI_* form interface in $TMP and activates it. Unlike forms, an existing ZAI_* interface is updated in place with the setters of IF_FP_INTERFACE_DATA, so the forms using it stay linked and print the change at the next preview, without being regenerated; its current version is saved first in output/adobe-forms/backup, and uploading the backup is the rollback. Refuses non-ZAI_* names (checked before any call, so no backup file is written for them), interfaces of other users or outside $TMP, XML schema based interfaces, a change of interface type, and a file that is not an interface XML (such as a form XML). Both write tools now check the ZAI_* name locally first.
    • Custom_PrintPreview: form also accepts an active Adobe form, always with form type 2 (PDF, domain NA_FORMTYPE): print programs such as SD_SDOC_PRINT01 refuse a form of another type. For SmartForms the form type comes from the TNAPR entry of the output type when its form is a SmartForms too.
    • New ABAP objects ZAI_CL_ADOBE_FORM, ZAI_CX_ADOBE_FORM and the remote-enabled FMs ZAI_ADOBE_FORM_READ, ZAI_ADOBE_FORM_WRITE, ZAI_ADOBE_INTERFACE_WRITE; 14 ABAP Unit tests (harmless) for the new class, 2 more for the preview. 27 Node tests for the extension.
    • New skill sap-adobe-form: workflow copy → preview → change → compare, how to find one's way in the XDP and in the context, how to add a printed field through a ZAI_* interface, errors and limits. Replacing the original form under a transport request is not part of this version.
  2. v0.5.2

    Other 7

    Notes

    Skills reviewed against Anthropic's skill authoring best practices. No change to the tools or the ABAP sources.

    • Script paths use ${CLAUDE_SKILL_DIR}, so set_prefix.py and pdf_text_diff.py are found wherever the plugin is installed (before: a <skill> placeholder and a path relative to the skill folder).
    • ARC-1 tools are explained with their full Claude Code name (mcp__<server>__<tool>), to pick the right server when several are configured.
    • pdf_text_diff.py: pypdf is listed in the skill; a missing package, a missing file or an unreadable PDF now end with a clear message and exit code 2.
    • Checklists to copy for the installation and for a SmartForms change; the PDF comparison is an explicit loop (compare, fix, repeat).
    • One placeholder for the prefix (<PREFIX>); test history moved out of the installation skill.
    • evals/: three cases for claude plugin eval (narrow report filters, copy before changing a form, checks before installing). With the plugin 1.00 on all three, without 0.00.
    • Extension version aligned with the plugin (index.ts and package.json said 0.5.0).
  3. v0.5.1

    Other 5

    Notes
    • Fix: the ABAP Unit test classes of ZAI_CL_PRINT_PREVIEW and ZAI_CL_SMARTFORM_XML did not compile on SAP_BASIS 7.50, so the two classes could not be activated on ECC. They used CL_ABAP_UNIT_ASSERT=>SKIP, which is not available on 7.50. Tests that find no suitable data on the system now end with a tolerable assertion (FAIL with LEVEL = TOLERABLE) instead of being skipped: ARC-1 reports it as failed with severity: tolerable (see SKILL.md, step 3).
    • Fix: ZAI_CL_PRINT_PREVIEW did not compile on 7.50: CALL FUNCTION ... EXPORTING is_nast = prepare_nast( is_nast = ... ) is read as a duplicate formal parameter IS_NAST. The NAST copy is now built in a separate variable first.
    • Fix: the test missing_config of ZAI_CL_PRINT_PREVIEW joined NAST with TNAPR and could read the whole NAST on systems with many messages, exceeding the 60 second limit of ABAP Unit. It now uses an output type without TNAPR entry and no NAST record.
    • ATC on ECC (variant DEFAULT) had one priority 1 and one priority 2 finding: pseudo comment CI_NOFIRST added to the TSP01 read by title in find_spools (on ECC TSP01 has only the index RQFINAL/RQCLIENT/RQOWNER), and the variant list of ZAI_CL_REPORT_LAUNCHER=>get_variants is sorted in ABAP, because ORDER BY bypassed the buffer of VARID.
    • Tested live on ECC 6.0 EHP8 (SAP_BASIS 750) and S/4HANA 2025 (SAP_BASIS 816).
  4. v0.5.0

    Other 1

    Notes
    • Compatible with SAP_BASIS 7.50: RAISE EXCEPTION TYPE ... EXPORTING instead of RAISE EXCEPTION NEW, POSIX regular expressions instead of PCRE.

Others providing93

Agent access to your code
  1. @abap2ui5/mcp-serverMCP server for the abap2UI5 check, deploy and run loopfrom ABAP
  2. arc-1-bopf-enharc-1 extension for reading and maintaining BOPF enhancementsfrom ABAP
  3. HammerNative macOS code editor for ABAP and CDSfrom ABAP
  4. arc-1-lspEdition of ARC-1 that runs ADT calls through adt-lsfrom ABAP
  5. arc-1MCP server over the ADT REST API for ABAP objectsfrom ABAP
  6. arc1-abap-bridgeVS Code bridge between arc-1 and ADT for VS Codefrom ABAP
  7. arc1-adt-abap-mcp-extEclipse add-on enabling the ADT MCP server with read-only toolsfrom ABAP
  8. capforgeMCP server scaffolding CAP and CDS checked by cds compilefrom CAP
  9. ABAP Accelerator MCP ServerAWS's ABAP MCP server for Amazon Q Developer and Kirofrom ABAP
  10. Modernization Agents for SAP on AWSAWS agents for ABAP, PI/PO and BW modernisation workfrom ABAP
  11. @mcp-abap-adt/coreABAP ADT MCP server published as an npm scope and pluginfrom ABAP
  12. @cap-js/mcp-serverMCP server for CAP development: model and docs searchfrom CAP
  13. chandrashekhar-mahajan/abap-mcp-serverABAP MCP server with ADT tools and five authentication strategiesfrom ABAP
  14. dassian-adtFork of mcp-abap-abap-adt-api with 25 tools and session recoveryfrom ABAP
  15. erpl-adtC++ binary speaking the ADT REST API as a CLI and MCP serverfrom ABAP
  16. bw-modeling-mcpMCP server for BW/4HANA modelling objectsfrom BTP/BAIP
  17. EPOD ADT MCP ServerMCP server for ABAP on the ADT session, in Eclipse or standalonefrom ABAP
  18. ZARC1_EXTENSION_FORMSarc-1 extension for SAPscript and Smart Forms objectsfrom ABAP
  19. fgalastri/MCP_ABAPValidates an ABAP class before it is deployed by converting the global class to a local one and syntax-checking that — plus CDS DDL and table metadata retrieval.from ABAP
  20. fr0ster/mcp-abap-adtABAP MCP server with full CRUD on on-premise and ABAP Cloudfrom ABAP
  21. abapsmithABAP MCP server over ADT with a local journal that can undo writesfrom ABAP
  22. sap-ai-dev-toolkitMCP proxy pinning an agent's ABAP tools to one SAP systemfrom ABAP
  23. aibap.mcpGo MCP server that writes, activates and runs ABAP classes via ADTfrom ABAP
  24. BellaEclipse plugin bringing Claude into ABAP Development Toolsfrom ABAP
  25. Maherd18/sap-mcp-serverPolicy-checked MCP server for ABAP development over ADTfrom ABAP
  26. sapdumpmcpMCP server reading ABAP short dumps over ADTfrom ABAP
  27. ABAP remote filesystemVS Code extension editing ABAP systems over ADT as a filesystemfrom ABAP
  28. mcp-abap-abap-adt-apiWrite-oriented MCP server over abap-adt-apifrom ABAP
  29. mcp-abap-adtRead-oriented MCP server fetching ABAP programs, classes, tablesfrom ABAP
  30. SAP MCP Connection ManagerWindows desktop manager handing SAP connections to assistants over MCPfrom ABAP
  31. ABAPilotMCP connector for ECC and on-premise S/4HANA with a licensed SAP sidefrom ABAP
  32. vibing-steampunkADT-to-MCP bridge in Go reaching past what ADT exposesfrom ABAP
  33. ADT MCP ServerLocal HTTP MCP server started from ABAP Development Tools for VS Codefrom ABAP
  34. ABAP Development Tools for VS CodeSAP's ABAP tools in VS Code for editing, debugging, ATC and transportsfrom ABAP
  35. SAP Joule for Developers, ABAP AI capabilitiesSAP's AI for ABAP development in ADT for Eclipse and VS Codefrom ABAP
  36. @sap/mdk-mcp-serverMCP server with five tools for Mobile Development Kit workfrom BTP/BAIP
  37. @sap-ux/fiori-mcp-serverMCP server for creating and editing Fiori applicationsfrom UI5
  38. ABAPDocMCPMCP server turning a transport request into a WRICEF specificationfrom ABAP
  39. Skybuffer AI MCP serverABAP add-on serving business data and transactions as MCP toolsfrom ABAP
  40. @ui5/mcp-serverMCP server for UI5 development with ten toolsfrom UI5
  41. abap-adt-cliCLI that pulls and pushes ABAP packages as local files over ADTfrom ABAP
  42. workskong/mcp-abap-adtLight MCP adapter for ABAP over ADT, documented in Koreanfrom ABAP
  43. KlystronMCP server in ABAP inside the application server, with agent skillsfrom ABAP
  44. pyrfc-mcpMCP server calling RFC-enabled function modules behind an allowlistfrom ABAP
  45. ABAP-AI-CODE-TOOLSabapGit package adding create, modify and delete tools to ABAP AI Codefrom ABAP
  46. ABAP AI CodeAgentic coding assistant in ABAP that runs as an SAP GUI reportfrom ABAP
  47. VERTEXADT extension for Eclipse and VS Code showing three SAP GUI toolsfrom ABAP
Agent guidance
  1. abap2UI5 for VS CodeVS Code extension to preview, activate and lint abap2UI5 appsfrom ABAP
  2. sap-cx-developer-companionAgent skill for SAP Customer Experience APIs, CDS and errorsfrom SAP Commerce
  3. sap-basis-opsRunbook skills for Basis operations at the OS and database layerfrom ABAP
  4. abap-offstack-aunitAgent skill for off-stack ABAP Unit tests and an abaplint gatefrom ABAP
  5. ARC-1 SkillsTwenty-two agent skills shipped with arc-1from ABAP
  6. sapskillsAgent skills for Clean ABAP, ADT in VS Code and guardrailsfrom ABAP
  7. SuperClaude for SAPClaude Code plugin with an ABAP MCP server and write guardsfrom ABAP
  8. sap-dm-pod2-mcp-serverMCP server for SAP Digital Manufacturing POD 2.0 extensionsfrom SAP Digital Manufacturing
  9. capire/skillsAgent skills for CAP development, each a SKILL.md with referencesfrom CAP
  10. sap-cloud-integration-pipeline-assistantAgent skill for the Pipeline Concept in SAP Cloud Integrationfrom BTP/BAIP
  11. claude-abap-devFive ABAP workflows for Claude Code on existing MCP serversfrom ABAP
  12. DanKromp/skillOverflowCollection of 41 agent skills, 37 for SAP development tasksfrom CAP
  13. sap-commerce-skillAgent skill for SAP Commerce Cloud 2211-jdk21.1 and laterfrom SAP Commerce
  14. ARC-DRAWMCP server drawing BTP solution diagrams on a draw.io canvasfrom BTP/BAIP
  15. cap-mtx-scaffoldAgent skill for CAP multitenancy scaffoldingfrom CAP
  16. sap-ai-dev-toolkitMCP proxy pinning an agent's ABAP tools to one SAP systemfrom ABAP
  17. scaffold-fiori-ai-bridgeAgent skill generating a Joule Frontend Actions bridge for UI5 appsfrom UI5
  18. sapcli Claude Code PluginAgents and skills that drive sapcli instead of ADTfrom ABAP
  19. CAP GuardianCAP review skill for coding agents with gates and prohibitionsfrom CAP
  20. sap-odata-explorerRust CLI and desktop app for exploring SAP OData servicesfrom BTP/BAIP
  21. btp-solution-diagram-generatorClaude plugin writing BTP solution diagrams as .drawio filesfrom BTP/BAIP
  22. abap-skillsSeventeen agent skills for ABAP developmentfrom ABAP
  23. drawio-skill-sapGitHub Copilot skill writing BTP solution diagrams as draw.io XMLfrom BTP/BAIP
  24. sap-mdk-appsAgent skill for Mobile Development Kit projectsfrom BTP/BAIP
  25. ABAP remote filesystemVS Code extension editing ABAP systems over ADT as a filesystemfrom ABAP
  26. sap-architectureClaude Code plugin and skill drawing validated BTP diagramsfrom BTP/BAIP
  27. WerkbankLocal desktop workspace for AI conversations with SAP connectorsfrom Across stacks
  28. SAP Datasphere Plugin for ClaudeEighteen Datasphere skills over a bundled MCP serverfrom BTP/BAIP
  29. claude-abap-skillsClaude Code plugins with Clean ABAP rules and templatesfrom ABAP
  30. SAP Power for KiroSAP skills for the Kiro IDEfrom BTP/BAIP
  31. drawio-btp-diagram-skillsClaude Code skills for BTP architecture diagrams in draw.iofrom BTP/BAIP
  32. @patimweb/pi-cap-bestpracticesSAP's capire/skills packaged for the pi coding agentfrom CAP
  33. pod2-configAn agent skill that turns a described POD change into an importable [SAP Digital Manufacturing](external:sap-digital-manufacturing) POD 2.0 export, built from standard plugins and actions only.from SAP Digital Manufacturing
  34. aicore-skillsFour agent skills for SAP AI Core in SAP's AI Skills Libraryfrom BTP/BAIP
  35. SAP/automation-pilot-agent-skillsEight skills for writing and operating SAP Automation Pilot contentfrom BTP/BAIP
  36. SAP Developers MCPHosted MCP server of developers.sap.com tutorials and missionsfrom Across stacks
  37. sap-fiori-guidelinesAgent skill built from the Fiori Design Guidelinesfrom UI5
  38. sap-fiori-iosAgent skill mapping Fiori iOS UI Kit nodes in Figma to SwiftUIfrom BTP/BAIP
  39. SAP/leanix-ai-pluginsClaude Code plugin with two skills for SAP LeanIX scriptingfrom BTP/BAIP
  40. SAP-samples/html5-applications-migration-skills-for-sap-btpClaude Code plugin with skills migrating HTML5 apps to appFrontfrom BTP/BAIP
  41. SAP-samples/joule-a2a-agent-toolkitSkills for building an A2A agent for Joule and deploying it to CFfrom BTP/BAIP
  42. SAP-samples/sap-devs-cliCLI adding SAP developer knowledge and MCP servers to AI coding toolsfrom BTP/BAIP
  43. sap-tutorials-contentAgent skill mapping the developers.sap.com content APIfrom BTP/BAIP
  44. SAP/ui-theme-designer-plugins-for-coding-agentsAgent plugin on the SAP Design System and theming parametersfrom UI5
  45. secondsky/sap-skillsForty SAP development plugins for coding agentsfrom BTP/BAIP
  46. UI5/plugins-coding-agentsUI5 plugins for coding agentsfrom UI5
  47. UI5 Web Components agent skillsTwo agent skills for accessibility and styling of web componentsfrom UI5
  48. rap-skillsRAP skills delivered branch-per-target for each deploymentfrom ABAP
  49. KlystronMCP server in ABAP inside the application server, with agent skillsfrom ABAP

Details

Sources3
Added by handdiscovered herechecked
github.com/silvius1996/claude-sap-kittree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainabap, ai-and-agents
Flavors1
Standard ABAP
“SAP_BASIS 7.50 or later, on-premise or private cloud: **ECC 6.0 EHP8** and **S/4HANA** (all releases).” — silvius1996/claude-sap-kit — README, Requirementschecked
History in the atlas2
  1. Handed over as a URL. Typed `skill` rather than `mcp-server` or `package`: what a reader installs is a Claude Code plugin of three `SKILL.md` directories, and the tool surface it brings belongs to [arc-1](artifact:arc-mcp-arc-1), which serves MCP — one artifact_type per entry (hard rule 9), the same shape [ARC-1 Skills](artifact:arc-mcp-arc-1-skills) takes beside that server. It answers [agent access to your code](capability:agent-code-access) through the five `Custom_*` tools and [agent guidance](capability:agent-guidance) through the three skills, and states the standard-abap flavor by its requirements, which rule out the two public-cloud ABAP targets by name.
  2. First seen.
For your agent
Ref
artifact:silvius1996-claude-sap-kit
JSON
/artifacts/silvius1996-claude-sap-kit.json
MCP
Connecting an agent