Everything in ABAP
Type: 3
Domain
Origin
Signals
More
Group by: Capability
Where it runs
Distributed through
Form
Framework for multi-step ABAP processes with monitoring
Only on SAP S/4HANA 2023 and 2025, on premise or private cloud: [SAP S/4HANA Cloud, Public Edition](external:sap-s4hana-cloud-public-edition) and the [SAP BTP ABAP environment](artifact:btp-abap-environment) are listed as coming soon, and a 2023 system has to leave out `ZABAP_PRC_EVENTS_SE_2025`, whose event-based side effects rely on APIs released with S/4HANA 2025. Not for a system that already carries a copy, because object names are global and two versions cannot live side by side, and not for a productive system by way of the `ZABAP_PRC_DEMO*` packages, which the README states are not intended for one and whose init classes delete and rebuild their own tables on every run. While the major version is 0 the public API is not stable: minor bumps carry breaking changes with no deprecation period, so productive use means pinning a tag and reading the CHANGELOG before every upgrade.
ABAP class implementing the Either pattern
No published releases; repository quiet for 25 months.
Result pattern for ABAP instead of exceptions for expected failures
Shared root exception class and text getter for USI developments
Raises an ABAP exception from a text or the last system message
Release and repository quiet for 26 months.
ABAP classes for calling Azure services from SAP processes
ABAP API for Google Apps, with upload to Google Docs
No published releases; repository quiet for 97 months.
ABAP framework wrapping the Google Sheets API for SAP S/4HANA
No published releases; repository quiet for 81 months.
ABAP client for Firebase's Realtime Database REST API
No published releases; repository quiet for 95 months.
Fetch API-style HTTP polyfill for cloud and classic ABAP
Neither the package manifest nor the repository tree declares a licence.
Cloud-compatible plugin for the abapify Fetch API polyfill
No published releases; repository quiet for 26 months.
Legacy-release Fetch API implementation for outbound HTTP in ABAP
Web service client and connector layer for calling out of ABAP
Quiet No published releases; repository quiet for 28 months.
Functional boundary The maintainer records SSL as a known issue: an SAP Basis problem in older systems that depends on the remote certificate, so a system that cannot carry the remote certificate chain will not complete the call. It is published as free to use at your own risk, with no support statement behind it.
HTTP client for classic on-premise ABAP and ABAP Cloud
No published releases; repository quiet for 32 months.
Puts a number from an abap2UI5 app on a Fiori launchpad tile
There is nothing here for ABAP for Cloud: the requirements name Standard ABAP releases only, and a CDS/SADL based OData service for `ABAP for Cloud` compatibility stands under Limitations & Todo.
ABAP framework for OData services with one class per entity
OData and Gateway shims serving SEGW-style services on Node.js
ABAP code and slides from a talk on building SAP Gateway services
Exposes ABAP class methods as REST services with Swagger UI
No published releases; repository quiet for 47 months.
Configurable CSV reader and writer for ABAP
JSON renderer and parser for ABAP with camelCase conversion
JSON encoder and decoder for ABAP, modelled on Go's encoding/json
No published releases; repository quiet for 49 months.
Open-source Z* version of /UI2/CL_JSON for ABAP to JSON
Protocol Buffers (proto2) implementation in ABAP
JSON parser and serialiser for ABAP with a node tree
Parser of TAB-delimited text into ABAP internal tables and back
Regex RuleSets that read barcode strings into named fields
The project states that until v1.0.0 is reached, breaking changes may occur without prior notice. Rule items do not chain: every rule operates on the original input string, so a format whose second step needs the result of the first needs a custom logic class. A REPLACE rule whose replacement produces the exact same string as the input is reported as `no match`, which the documentation records as a known limitation.
ABAP library generating and parsing JSON strings
No published releases; repository quiet for 90 months.
RFC 4180 CSV parser and generator for ABAP
ABAP-native MCP endpoint that drives opted-in abap2UI5 apps
Stateful apps cannot be operated: a stateful session lives in one HTTP request and an MCP call is one request, so `app_start` refuses them. The repository carries no release yet and states the addon has not been run in production use, the 7.02 downport is lint-only with no 7.02 system having run it, and the ABAP Cloud HTTP service setup is written down but still to verify on your own system.
MCP server SDK written in ABAP
Server side only, and deliberately: the author states there is no realistic way to support the SSE streaming a client needs, so there are no notifications, no `listChanged`, no `subscribe` and no logging. It is also frozen — protocol versions up to 2025-11-25 and no further, with everything after that in a separate V2 SDK, so starting here today is starting on a closed branch.
Stateless ABAP MCP server SDK for the 2026-07-28 protocol draft
Stateless by design: with no `Mcp-Session-Id` and no SSE, notifications of any kind, `resources/subscribe` and stream-close cancellation are excluded, which the author states are protocol-level impossibilities on stateless ICF rather than gaps to be filled later within this design. ABAP Cloud is not supported and not planned, the stated reason being SAP pushing its own MCP strategy and features in BTP; the first iteration targets 7.5x classic, with 7.02 to 7.4x served from a separate generated downport repository. No authorization object and no default auth check are delivered, so a user who may call the ICF node may call every `AREA`/`SERVER` registered under it until `check_authorization` is redefined.
MCP server publishing SAP functions as tools from config tables
Not reachable Not reachable since 2026-10-20.
Functional boundary What it exposes is whatever somebody put in the configuration table, which moves the governance question inside the SAP system and out of the server — an advantage if that table is controlled and a hazard if it is not. The web management interface is a second surface to secure alongside the MCP one.
ABAP add-on serving business data and transactions as MCP tools
Its maker offers it commercially.
Server side of the flight reference scenario for SOAP in ABAP Cloud
Client side of the flight reference scenario for SOAP in ABAP Cloud
MCP server for BW/4HANA modelling objects
Its README says it plainly and so does this entry: this is not a simulation, every tool call reaches a live BW system, and write operations produce real changes. BW modelling objects are the definition of a warehouse — the blast radius of a wrong one is every report built on it.
Materials for the RAP400 to RAP620 ABAP Cloud workshops
TechEd 2023 tutorial on an analytical data model in ABAP Cloud
ABAP OData service for attachments and comments via GOS
No published releases; repository quiet for 66 months.
abapconf 2026 talk materials on RAP custom entities
Neither the package manifest nor the repository tree declares a licence.
Analytical ABAP CDS models for the ABAP Flight Reference Scenario
Example programs for the ODBC driver for ABAP in several languages
ABAP component importing XLSX or CSV files into RAP business objects
Maps clipboard, Excel or text data onto a declared ABAP structure
Helper methods over abap2xlsx for Excel, JSON and tables
Reader for Excel spreadsheets in OpenXML format from ABAP
No published releases; repository quiet for 81 months.
Sample uploading a JSON file into an ABAP table on BTP ABAP
Sample exporting SAP GUI ALV grid data to Google Drive
Not where SAP's own Google Workspace integration already applies: the README opens by announcing a native integration between Google Workspace and [SAP S/4HANA](external:sap-s4hana), whose first set of features is included in SAP S/4HANA Cloud 2208 and SAP S/4HANA 2022 and needs an additional licence for the SAP Document Management Service. Not where end users cannot each hold a regular Google account, since there is no way to use an enterprise account or to log on to Google Drive through single sign-on, and not where the redirect URL Google calls cannot reach a public top-level domain server. No SAP standard support is provided for it.
MCP server for BW/4HANA modelling objects
Its README says it plainly and so does this entry: this is not a simulation, every tool call reaches a live BW system, and write operations produce real changes. BW modelling objects are the definition of a warehouse — the blast radius of a wrong one is every report built on it.
DuckDB extension reading SAP ERP tables, CDS views and BW queries
DataZoo GmbH calls the extension experimental and states that minimal testing and benchmarking were done. The Business Source License 1.1 it carries restricts offering the software to third parties on a hosted or embedded basis, so an embedding product needs a commercial licence. Telemetry is on by default and is switched off per session with `SET erpl_telemetry_enabled = false` or for the machine with `DATAZOO_DISABLE_TELEMETRY=1`.
ABAP class stripping invalid characters in BW end routines
No published releases; repository quiet for 24 months.
Framework for BW transformation start routines from a table
No published releases; repository quiet for 72 months.
Table maintenance over HTTP for a table fixed in code
Not for a table whose contents matter, and not for one chosen at run time: the name of the table is fixed in the calling code, and the maintainer's own warning is "only hardcode the table name, don't use with important tables, use at own risk!"
ABAP, Python and C code for similarity search over field descriptions
ABAP class for descriptive statistics over an internal table
Utility for update task database changes and internal tables in ABAP
Task tracker on a BOPF-backed CDS view with a Fiori list report
abapconf 2026 talk materials on RAP custom entities
Neither the package manifest nor the repository tree declares a licence.
Practice repository for the unmanaged RAP scenario
Practice repository for managed RAP with unmanaged save
Multitenant S/4HANA Cloud extension built with RAP on BTP ABAP
CodeJam on RAP features from cloud releases 2502 to 2602
Materials for the RAP400 to RAP620 ABAP Cloud workshops
Beginner RAP workshop building a draft-enabled Fiori elements app
Intermediate RAP workshop on late numbering, side effects and events
RAP travel app workshop using SAP Joule for Developers
RAP travel app workshop built from VS Code via the ADT MCP Server
Guided workshop building a Travel Processing app in ABAP Cloud
Flight Reference Scenario with sample data and services for RAP
RAP business object that generates other RAP business objects
Loyalty Hub on-stack RAP extension for S/4HANA Cloud Public Edition
TechEd 2025 workshop modelling a RAP object in SAP Build Code
TechEd 2025 workshop rebuilding an ALV app as a RAP-based Fiori app
Framework for multi-step ABAP processes with monitoring
Only on SAP S/4HANA 2023 and 2025, on premise or private cloud: [SAP S/4HANA Cloud, Public Edition](external:sap-s4hana-cloud-public-edition) and the [SAP BTP ABAP environment](artifact:btp-abap-environment) are listed as coming soon, and a 2023 system has to leave out `ZABAP_PRC_EVENTS_SE_2025`, whose event-based side effects rely on APIs released with S/4HANA 2025. Not for a system that already carries a copy, because object names are global and two versions cannot live side by side, and not for a productive system by way of the `ZABAP_PRC_DEMO*` packages, which the README states are not intended for one and whose init classes delete and rebuild their own tables on every run. While the major version is 0 the public API is not stable: minor bumps carry breaking changes with no deprecation period, so productive use means pinning a tag and reading the CHANGELOG before every upgrade.
RAP sample with bgPF, business events and side effects
Transactional outbox pattern in ABAP Cloud with bgPF
Library that reads and generates Excel spreadsheets from ABAP
Single-file Handlebars templating for ABAP 7.40 SP02 and up
Standalone PDF generator written in ABAP
Submits an ABAP report to the spool and converts the output to PDF
ABAP template engine for Excel, Word, HTML and PDF
ABAP class filling a tagged Word .docx template with data
No published releases; repository quiet for 33 months.
Standalone ABAP class drawing PDFs without Adobe Document Server
RAP sales order using number ranges, change documents and Adobe forms
Projects integrating SAP Forms Service by Adobe with ABAP Environment
ABAP connector to Kafka through the Confluent Kafka REST Proxy
No published releases; repository quiet for 57 months.
ICF handler receiving Amazon SNS notifications in an ABAP system
No published releases; repository quiet for 64 months.
MQTT 3.1.1 client implemented in ABAP
No published releases; repository quiet for 68 months.
Framework for multi-step ABAP processes with monitoring
Only on SAP S/4HANA 2023 and 2025, on premise or private cloud: [SAP S/4HANA Cloud, Public Edition](external:sap-s4hana-cloud-public-edition) and the [SAP BTP ABAP environment](artifact:btp-abap-environment) are listed as coming soon, and a 2023 system has to leave out `ZABAP_PRC_EVENTS_SE_2025`, whose event-based side effects rely on APIs released with S/4HANA 2025. Not for a system that already carries a copy, because object names are global and two versions cannot live side by side, and not for a productive system by way of the `ZABAP_PRC_DEMO*` packages, which the README states are not intended for one and whose init classes delete and rebuild their own tables on every run. While the major version is 0 the public API is not stable: minor bumps carry breaking changes with no deprecation period, so productive use means pinning a tag and reading the CHANGELOG before every upgrade.
ABAP classes sending push notifications to Mobile Services
No published releases; repository quiet for 54 months.
ABAP helper class building HTML emails from templates
Quiet No published releases; repository quiet for 52 months.
Functional boundary On an SAP S/4HANA system the maintainer points elsewhere: the README calls this solution helpful for non-S/4 systems and names SAP's own e-mail templates with CDS views as what S/4 systems have instead.
RSS feed publisher for content from an SAP NetWeaver ABAP system
No published releases; repository quiet for 93 months.
JSON adapter exposing ABAP function modules over HTTP
Input arrives only as JSON, or as plain XML if the ABAP built-in transformation is switched on, whatever the output format is set to. Cross-site calls are limited to JSONP: the maintainer lists CORS support as planned.
RFC-callable ABAP API for SAP data extraction for ADELE
No published releases; repository quiet for 73 months.
DuckDB extension reading SAP ERP tables, CDS views and BW queries
DataZoo GmbH calls the extension experimental and states that minimal testing and benchmarking were done. The Business Source License 1.1 it carries restricts offering the software to third parties on a hosted or embedded basis, so an embedding product needs a commercial licence. Telemetry is on by default and is switched off per session with `SET erpl_telemetry_enabled = false` or for the machine with `DATAZOO_DISABLE_TELEMETRY=1`.
RFC client for Node.js and TypeScript without the NW RFC SDK
BUSL-1.1 rather than node-rfc's Apache-2.0, so a product you distribute has to be read against the licence and its Additional Use Grant first, and the source is closed: the GitHub repository is the issue tracker and the documentation, nothing else. `RfcServerOptions.bgRfcHandlers` raises instead of accepting handlers, so a server receiving inbound bgRFC units is outside what this does. An ABAP `MESSAGE`-raised failure still arrives with its T100 template rather than the rendered sentence, and the dump name is not reported as `key` for that case.
No published releases; repository quiet for 63 months.
MCP server for the abap2UI5 check, deploy and run loop
Every gate here runs off-system, so what the class does on a real system and what the view does on the oldest UI5 release it has to serve are what the `pitfalls` catalogues carry and no local run can see. It runs abap2UI5 app classes, so ABAP that is not one has nothing here to deploy into. In system mode the sandbox tools are not offered, and an `app_act` event runs on the system as the configured user.
ABAP ADT MCP server published as an npm scope and plugin
A descendant rather than a distinct idea: if what you need is the ADT surface itself, its ancestors are entered here too and one of them may already be in your stack.
AWS's ABAP MCP server for Amazon Q Developer and Kiro
Written for Amazon Q Developer and Kiro, and the central deployment path is ECS Fargate — the further you are from AWS, the more of it is scaffolding you do not need. Python rather than the Node most of this group uses. Its README says the repository is no longer maintained and that the latest version of ABAP Accelerator is shared after registering with AWS for [Modernization Agents for SAP on AWS](https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWS).
SAP's ABAP tools in VS Code for editing, debugging, ATC and transports
abapGit package adding create, modify and delete tools to ABAP AI Code
MCP server turning a transport request into a WRICEF specification
Neither the package manifest nor the repository tree declares a licence.
MCP connector for ECC and on-premise S/4HANA with a licensed SAP side
Commercial Its maker offers it commercially.
Functional boundary The MIT licence covers the connector only: connecting to SAP needs a licensed ABAPilot backend installed in your system, so this is a commercial decision wearing an open-source badge on one half. Its own published checks did not cover writes, activation, transports or authorisation boundaries.
ABAP MCP server over ADT with a local journal that can undo writes
A system that reports itself productive, or whose role the probe cannot prove non-productive, is write-locked with no override, so changing code in production is not something this does. The permission ladder constrains the package, object name and transport request the server itself passes on a write, and is not a sandbox around ABAP it executes: `abap_run`, `abap_test` and the opt-in `core.eval` run under the connected technical user's SAP authorisations, which is where the boundary actually sits. Data preview, dump variable contents and driving a transaction by batch input stay off in every mode, `admin` included, until each is named explicitly.
Local HTTP MCP server started from ABAP Development Tools for VS Code
There is nothing to install and nothing to deploy, and equally nothing to run headless: in VS Code it exists only while ADT for VS Code is running with a logged-on ABAP project, so it is a developer's local surface rather than anything a pipeline or a hosted agent can reach. No public repository, so what it exposes is what the documentation says it exposes.
Go MCP server that writes, activates and runs ABAP classes via ADT
Not reachable Not reachable since 2026-10-20.
Functional boundary `run_class` executes code in your system — that is the point and it is also the risk.
MCP server over the ADT REST API for ABAP objects
arc-1 extension for reading and maintaining BOPF enhancements
Classic BOPF only: business objects of the ABAP Programming Model for SAP Fiori are not handled, and on [the BTP ABAP environment](artifact:btp-abap-environment) or S/4HANA Public Cloud classic BOPF enhancements do not exist. It is version 0.1.0, verified on S/4HANA 2025 (SAP_BASIS 816) on-premise only, and [arc-1](artifact:arc-mcp-arc-1) still marks the plugin API it is built on as experimental. ARC-1 loads no extensions on its multi-target routes and offers none of these tools in its `hyperfocused` tool mode.
Edition of ARC-1 that runs ADT calls through adt-ls
Single-tenant today, one technical user, with per-user principal propagation on the roadmap — so a shared deployment cannot yet act as the developer who asked. The sibling edition [ARC-1](artifact:arc-mcp-arc-1) speaks ADT directly if you would rather not depend on the language server.
VS Code bridge between arc-1 and ADT for VS Code
The diff holds only while the object is inactive, since after activation the previous version is gone and a watched journal directory is what the maintainer points to instead. It adds no write path of its own: the IDE writes through SAP's extension, and the README states arc-1 can stay on `SAP_ALLOW_WRITES=false`. DDIC metadata files are skipped, because SAP's own stub for them says they are not supported in ABAP development tools for VS Code.
Eclipse add-on enabling the ADT MCP server with read-only tools
It lives inside Eclipse and inherits everything that implies — the session is a developer's, not a pipeline's. And it is version-bound: ADT 3.60 or newer for 0.5.1, with 0.3.x the path for ADT 3.58 and 3.59.
MCP server for BW/4HANA modelling objects
Its README says it plainly and so does this entry: this is not a simulation, every tool call reaches a live BW system, and write operations produce real changes. BW modelling objects are the definition of a warehouse — the blast radius of a wrong one is every report built on it.
ABAP MCP server with ADT tools and five authentication strategies
Built and last touched in the same week of March 2026, so the maintenance reading is what it is — the authentication work is the reason to look, and a stalled repository is the reason to read it before depending on it.
Fork of mcp-abap-abap-adt-api with 25 tools and session recovery
Freestyle SQL and `abap_run` mean an agent can read data and execute code, which is well past reading source. Neither is something to grant on a system where the distinction between development tooling and business data matters.
MCP server for ABAP on the ADT session, in Eclipse or standalone
In the Eclipse mode the server lives in a developer's IDE, binds to 127.0.0.1 and answers any request carrying an `Origin` header with HTTP 403, so a pipeline or a remote agent has nothing to reach; the standalone mode on the runtime of the ADT for VS Code extension is the documented route with no IDE open. A new connection starts in write mode, so the 11 write tools are live against a connected system until someone presses Toggle Read-Only. The dropins route for the two bundles is documented as untested.
C++ binary speaking the ADT REST API as a CLI and MCP server
A compiled binary rather than an npm package, shipped prebuilt per platform and through pip and uvx. It collects anonymous usage telemetry by default, switched off with `--no-telemetry` or `DATAZOO_DISABLE_TELEMETRY=1`. And the BW reach is what distinguishes it — if the work is plain ABAP, that half is weight you are not using.
Neither the package manifest nor the repository tree declares a licence.
ABAP MCP server with full CRUD on on-premise and ABAP Cloud
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.
MCP server in ABAP inside the application server, with agent skills
Its maker offers it commercially.
Policy-checked MCP server for ABAP development over ADT
Development and sandbox systems only: the README warns against pointing it at production. Transport release is never executed, since the tool exists to show the policy stopping it, and separation of duties is checked against the `identity.approvers` list in the policy file rather than against SAP authorisations, so it holds as far as that file does and no further. The write path has been tested with ABAP classes and other object types may need adjustments, there is deliberately no tool that creates or deletes an object, and one server instance serves one SAP system.
Write-oriented MCP server over abap-adt-api
Its own README opens by calling the server experimental. It also writes: locking, editing and activating in a system an agent can reach is a permissions decision before it is a tooling one.
Read-oriented MCP server fetching ABAP programs, classes, tables
Every tool its README lists reads — Get and Search, nothing that writes. Locking, editing, activation and transports are the other server, [mcp-abap-abap-adt-api](artifact:mario-andreschak-mcp-abap-adt-api), and mixing the two is how you end up with two MCP servers pointed at one system.
MCP server calling RFC-enabled function modules behind an allowlist
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.
Windows desktop manager handing SAP connections to assistants over MCP
MCP proxy pinning an agent's ABAP tools to one SAP system
MCP server reading ABAP short dumps over ADT
ABAP add-on serving business data and transactions as MCP tools
Its maker offers it commercially.
ADT-to-MCP bridge in Go reaching past what ADT exposes
Reach is the reason to use it and the reason to be careful: reading cluster tables and spool output goes well past what a development tool is normally pointed at. Decide what an agent may reach before granting it, not after.
Light MCP adapter for ABAP over ADT, documented in Korean
Read-only in practice, and the documentation is Korean; the tool names are English but the guidance around them is not.
arc-1 extension for SAPscript and Smart Forms objects
Smart Form content cannot be read or written, and HR Forms (`PE51`) are not implemented. Installing it needs SAP GUI or WebGUI once, to register the OData services in `/IWFND/MAINT_SERVICE` and to redefine the write service in `SEGW`, and the extension is built against a locally linked ARC-1.
Sample arc-1 extension in TypeScript with ten custom tools
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary It consumes the `@experimental` public API, which the README says may break in any release. The RFC tool dials as one shared technical user with its own credentials, so SAP's log records that user and not the person behind the agent.
LibreChat fork with four SAP MCP servers preconfigured
TechEd 2025 workshop on a Fiori app with ABAP Cloud and Joule
MCP server for the abap2UI5 check, deploy and run loop
Every gate here runs off-system, so what the class does on a real system and what the view does on the oldest UI5 release it has to serve are what the `pitfalls` catalogues carry and no local run can see. It runs abap2UI5 app classes, so ABAP that is not one has nothing here to deploy into. In system mode the sandbox tools are not offered, and an `app_act` event runs on the system as the configured user.
ABAP MCP server over ADT with a local journal that can undo writes
A system that reports itself productive, or whose role the probe cannot prove non-productive, is write-locked with no override, so changing code in production is not something this does. The permission ladder constrains the package, object name and transport request the server itself passes on a write, and is not a sandbox around ABAP it executes: `abap_run`, `abap_test` and the opt-in `core.eval` run under the connected technical user's SAP authorisations, which is where the boundary actually sits. Data preview, dump variable contents and driving a transaction by batch input stay off in every mode, `admin` included, until each is named explicitly.
Exposes S/4HANA or ECC OData services as MCP tools
It puts create, update and delete on business entities behind natural language. Whatever the destination's principal may change, an agent may change — and "create a new customer" is a sentence, not a form somebody signed off.
MCP server in ABAP inside the application server, with agent skills
Its maker offers it commercially.
Python MCP server for SAP Gateway OData operations
Python bridge generating MCP tools from OData v2 metadata
OData v2 only, and untouched since August 2025 — the same author's [Go port](artifact:oisee-odata-mcp-go) is where v4 support and the tool-explosion work went.
Go binary bridging any OData v2 or v4 service to MCP
Universal mode trades discoverability for size: one generic tool is harder for a model to pick correctly than a named one, which is why it is not the default. On a small service, standard mode is the better answer.
MCP server calling RFC-enabled function modules behind an allowlist
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.
On ECC the S/4HANA `API_*` services that the three convenience readers default to do not exist, so each one has to be pointed at a Z service of your own or replaced by the RFC tools. `read_table` inherits `RFC_READ_TABLE`'s 512-byte row, so a wide table needs an explicit field list and some fields cannot be selected at all, and the bridge starts a Node process and a fresh logon per call, with no pooling. The audit log is one line per call that includes the call arguments, so every filter and WHERE clause sent to SAP is written to a file that then has to be handled as sensitive.
Read-only security analysis MCP server for SAP audits and SoD review
Read-only does not mean low-stakes: a complete picture of who can do what in an SAP system is exactly what an attacker would want, and the ready-made endpoint is the vendor's rather than yours — the README also documents running the server yourself. The authentication is careful; the question of what leaves your landscape is still yours.
ABAP add-on serving business data and transactions as MCP tools
Its maker offers it commercially.
MCP server in ABAP inside the application server, with agent skills
Its maker offers it commercially.
Hosted MCP server of developers.sap.com tutorials and missions
MCP proxy pinning an agent's ABAP tools to one SAP system
Starter repository for an abap2UI5 app with CI and agent setup