MCP serverMCP serverExposes tools to a coding agent over MCP.See every one →What this type is →independently maintainedindependently maintainedPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
ADAM
An MCP server that debugs ABAP on a connected system over ADT, as one-shot captures or an interactive session, over stdio next to the assistant or as a shared server on SAP BTP Cloud Foundry.
An agent can read ABAP source and still not know why a value came out wrong. ADAM gives it SAP's own debugger over the ADT resourcesADT resourcesThe HTTP endpoint an ABAP system exposes as the adt ICF service under /sap/bc/adt, so a client outside the system can reach development objects, delivered with the platform rather than installed.sap official, abap: one abap_debug call resolves the breakpoints against the active source, arms them for the session's own SAP user, triggers the run with the object's harmless ABAP Unit tests or an OData GET, and records every stop of that single run with the position, the call stack, the variables it was asked for and the steps after each stop, compacted into a line trace past twenty. A breakpoint addresses a line, a method, a MESSAGE statement, a statement kind such as COMMIT WORK or an exception class, and carries a hit count and an ABAP condition SAP evaluates there, so one stop can be the 500th pass of a loop. With interactive: true the program stays stopped and abap_debug_session drives it one move per call: a step (into, over or out), a continue to a line, an inspection of any variable, an end that lets the program run on or aborts it where it stands. abap_source returns the active source numbered the way breakpoints address it and abap_search finds objects by name or pattern; nothing is installed on the SAP system, the capture writes nothing there, and it refuses when Eclipse, VS Code or another capture already listens for that SAP user.
Facts
Last push
Where it sits
Lives in
Provides
DebuggingABAPDebuggingSeeing what running code did between an input arriving and a result coming out: which code ran, what the values were at each point, and why a value ended up as it did.Agent access to your codeABAPBTPAgent access to your codeLetting 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.
Serves
Flavors
Runs
Cloud Foundrylocal
Requires
ADT resourcesADT resourcesthe ADT resources the server calls on the connected system: it needs a system reachable over HTTP(S) with ADT enabled, and a user with ADT access and debug authorization
Optional
SAP BTP ABAP environmentSAP BTP ABAP environmentthe ABAP instance whose service key the server logs on with, opening the browser for the SAP login on the first call@arc-mcp/xsuaa-auth@arc-mcp/xsuaa-auththe authentication stack in front of the /mcp route and the destination lookups behind itSAP Authorization and Trust Management serviceSAP Authorization and Trust Management servicethe sign-in of the MCP clients, with dynamic client registration and the debug scope every tool call needs; the MTA creates the instance from xs-security.jsonSAP Destination serviceSAP Destination servicethe destination that names the SAP system and how each user logs on to it: PrincipalPropagation for an on-premise system or OAuth2UserTokenExchange for the BTP ABAP environmentSAP Connectivity serviceSAP Connectivity servicethe forward proxy the ADT calls leave through on their way into the customer's networkCloud ConnectorCloud Connectorthe tunnel into the customer's network and the certificate mapping that turns the propagated user into an SAP logon name; its access control has to expose /sap/bc/adt with all sub-pathsSAP BTP, Cloud Foundry RuntimeSAP BTP, Cloud Foundry Runtimethe runtime the MTA is deployed to, at one instance because an interactive session holds the program and its debugger session in the process
Who is behind it
Clément RingotClément RingotMaintains this
In the atlas: maintains 3, contributes to 3@ClementRingotmaintainer
In the atlas: maintains 3, contributes to 3@ClementRingotmaintainer
Before choosing this
Conditions
PracticalFunctional boundary
A stopped program holds an SAP work process and its caller's request, so an interactive session is the wrong shape wherever that matters: one runs per SAP user at a time, other captures for that user are refused while it is open, and a Cloud Foundry deployment stays at one instance because the next call must reach the same process. Breakpoints in report and function-group includes are not accepted, and a message breakpoint catches MESSAGE statements only, so RAP messages from new_message( … ) and BAPI return tables never stop a run. On SAP_BASIS 7.50 and older the system cannot name the session's debug user, so there SAP_USER is used behind Basic or cookie authentication only.
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
- MCP server
- Origin
- Independently maintained
- Runtime
- Node.js
- Runs on
- Cloud Foundrylocal
As an MCP server
- Transport
- stdioHTTP
For agent access to ABAP code
- Read
- sourcesearchwhere-usedDDICCDStable data
- Change
- writecreateactivatetransportsgit
- Check
- syntaxATCABAP Unit
- Run
- run codedumps
Connections
Group by12 of 12 connections
NodeRelationBasis
Functional
Agent access to your codeAgent access to your codeLetting a coding agent read and act on your project or systemSAP and community, unassessed
provides
stated
provides Agent access to your code
Hands a coding agent the debugger of the connected system and the two reads around it, as the caller's own SAP user: the active source numbered the way breakpoints address it, the repository quick search, a run triggered by the object's harmless ABAP Unit tests or an OData `GET`, and what the program did at each stop of that run.
“An [MCP](https://modelcontextprotocol.io) server that lets an AI assistant debug ABAP code on an SAP
system, in two modes:”“- **Only the session's own user.** The debug user is the one SAP itself names for the session
(`/sap/bc/adt/core/http/systeminformation`), never a name passed in a call.”
Letting a coding agent read and act on your project or system
DebuggingDebuggingSeeing what running code did between input and resultSAP and community, narrow by design
provides
stated
provides Debugging
Drives SAP's own ABAP debugger from outside the system over ADT: it resolves and arms external breakpoints for the session's own SAP user, triggers the run, and at every stop of that one run records where the program stands, the call stack, the variables asked for and the steps taken after the stop, then releases the program and removes what it set. An interactive mode keeps the program waiting at a stop and takes one move per call.
“- **One-shot** (default): in **one tool call** it arms breakpoints, runs the code, and at every stop
of that run records where the program stands, the call stack, the variables and as many steps as
the call's time and size budgets allow — then lets the program finish and removes everything it set.”“- **Interactive** (`interactive: true`): it stops at the first breakpoint and keeps the program
waiting there; the assistant then drives it one move per call — step in, over or out, continue,
inspect any variable — deciding each move from what it sees, until it ends the session.”“- **Observes, never changes.** No variable writes, no jumps, no system debugging; the program's flow
is the one it would have taken anyway — unless an interactive session is ended with
`terminate: true`, which aborts the program on request. Frames of SAP system programs are skipped.”
Seeing what running code did between input and result
Technical
connects to
stated
connects to ABAP platform
arms the external breakpoints, starts the debugger listener, attaches from the application server the program stopped on and reads the position, call stack and variables, all through the ADT REST API that Eclipse ADT uses
“It talks to SAP through the ABAP Development Tools (ADT) REST API — the same resources Eclipse ADT
uses — so nothing has to be installed on the SAP system.”“2. **Arm.** External breakpoints are set for the session's own SAP user, and SAP's debugger listener
starts (a long poll).”
SAP's application server and development platform for ABAP. For the things here it is the system a developer's editor or an agent's tool reaches over ADT, and a program calls over RFC; where it runs is the deployment's, as for SAP BW/4HANA.
SAP Destination serviceSAP Destination serviceNamed, credentialed addresses of other systems resolved at runtimesap official, btp
connects to
stated
connects to SAP Destination service
the server is deployed as a shared server on SAP BTP Cloud Foundry
exchanges the signed-in MCP user's token at the Destination service for the per-user credentials the ADT calls then carry, so the debugger reaches SAP as that person's own SAP user
“user token → Destination service (PrincipalPropagation)”“The server checks the destination at its first call: an identity per user, an `http://` URL behind the
Connectivity proxy.”
Named, credentialed addresses of other systems resolved at runtime
ADT resourcesADT resourcesHTTP endpoint under /sap/bc/adt exposing ABAP development objectssap official, abap
needs
stated
needs ADT resources
the ADT resources the server calls on the connected system: it needs a system reachable over HTTP(S) with ADT enabled, and a user with ADT access and debug authorization
“- An SAP system reachable over HTTP(S) with ADT enabled: SAP NetWeaver / S/4HANA on-premise (SAP_BASIS
7.50 or later), or the SAP BTP ABAP Environment.”“- An SAP user with ADT access (`S_ADT_RES`) and debug authorization (`S_DEVELOP` with
`OBJTYPE = DEBUG`, `ACTVT = 03`).”
HTTP endpoint under /sap/bc/adt exposing ABAP development objects
@arc-mcp/xsuaa-auth@arc-mcp/xsuaa-authXSUAA authentication stack for an MCP server on SAP BTPindependent, btp
optionally needs
stated
optionally needs @arc-mcp/xsuaa-auth
the server runs in HTTP mode on SAP BTP Cloud Foundry
the authentication stack in front of the `/mcp` route and the destination lookups behind it
“The authentication stack and the destination lookups come from
[`@arc-mcp/xsuaa-auth`](https://www.npmjs.com/package/@arc-mcp/xsuaa-auth), extracted from ARC-1's
production deployment.”
XSUAA authentication stack for an MCP server on SAP BTP
Cloud ConnectorCloud ConnectorSAP's on-premises agent linking SAP BTP to customer-network systemssap official, btp
optionally needs
stated
optionally needs Cloud Connector
the deployed server reaches an on-premise SAP system
the tunnel into the customer's network and the certificate mapping that turns the propagated user into an SAP logon name; its access control has to expose `/sap/bc/adt` with all sub-paths
“On-premise: the Cloud Connector connected to the subaccount, with principal propagation configured (system certificate, CA, subject pattern) and a mapping to the SAP system exposing `/sap/bc/adt` with all sub-paths”
SAP's on-premises agent linking SAP BTP to customer-network systems
SAP Authorization and Trust Management serviceSAP Authorization and Trust Management serviceOAuth server issuing JWTs and holding scopes for BTP appssap official, btp
optionally needs
stated
optionally needs SAP Authorization and Trust Management service
the server is deployed as a shared server on SAP BTP Cloud Foundry
the sign-in of the MCP clients, with dynamic client registration and the `debug` scope every tool call needs; the MTA creates the instance from `xs-security.json`
“The server runs on SAP BTP the way [ARC-1](https://github.com/arc-mcp/arc-1) does: an MTA with XSUAA
for the MCP clients' sign-in, the Destination service for the SAP system, and the Connectivity service
for an on-premise system behind the Cloud Connector.”“The role collection carries the scope `debug`, which every tool call needs.”
OAuth server issuing JWTs and holding scopes for BTP apps
SAP BTP ABAP environmentSAP BTP ABAP environmentABAP runtime on BTP for the ABAP Cloud modelsap official, btp
optionally needs
stated
optionally needs SAP BTP ABAP environment
the SAP system debugged is the SAP BTP ABAP environment, reached with a service key instead of a URL and credentials
the ABAP instance whose service key the server logs on with, opening the browser for the SAP login on the first call
“**SAP BTP ABAP Environment.** Create a service key for the ABAP instance in the BTP cockpit, save it
as a file, and set `SAP_BTP_SERVICE_KEY_FILE` instead of URL and credentials. On the first call the
server opens your browser for the SAP login (the flow Eclipse ADT uses); the token is then refreshed
automatically.”
ABAP runtime on BTP for the ABAP Cloud model
SAP BTP, Cloud Foundry RuntimeSAP BTP, Cloud Foundry RuntimeCloud Foundry runtime of SAP BTP for polyglot applicationssap official, btp
optionally needs
stated
optionally needs SAP BTP, Cloud Foundry Runtime
the server is deployed as a shared server on SAP BTP instead of run locally over stdio
the runtime the MTA is deployed to, at one instance because an interactive session holds the program and its debugger session in the process
“**As a shared server on SAP BTP.** Deploy the MTA to Cloud Foundry (`mbt build`, `cf deploy`), point it
at a principal-propagation destination, assign the role collection, and connect the clients to
`https://<route>/mcp` — they sign in through XSUAA in the browser, and each user debugs as their own
SAP user.”“The deployment creates the XSUAA, Destination and Connectivity instances, binds them, and starts **one**
instance (256 MB). Keep it at one: an interactive session holds the program and its debugger session in
the process, and the next call must reach the same process.”
Cloud Foundry runtime of SAP BTP for polyglot applications
SAP Connectivity serviceSAP Connectivity serviceProxy from cloud apps to on-premise systems via Cloud Connectorsap official, btp
optionally needs
declared
optionally needs SAP Connectivity service
the deployed server reaches an on-premise SAP system behind the Cloud Connector
the forward proxy the ADT calls leave through on their way into the customer's network
“the Connectivity service reaches an on-premise system through the Cloud Connector”“A Cloud Foundry space with entitlements for XSUAA (`application`), Destination (`lite`) and Connectivity (`lite`)”
Proxy from cloud apps to on-premise systems via Cloud Connector
SAP Destination serviceSAP Destination serviceNamed, credentialed addresses of other systems resolved at runtimesap official, btp
optionally needs
stated
optionally needs SAP Destination service
the server is deployed as a shared server on SAP BTP Cloud Foundry
the destination that names the SAP system and how each user logs on to it: `PrincipalPropagation` for an on-premise system or `OAuth2UserTokenExchange` for the BTP ABAP environment
“BTP destination of the SAP system: `PrincipalPropagation` (on-premise, Cloud Connector) or `OAuth2UserTokenExchange` (BTP ABAP Environment) — each user as themselves”“The server runs on SAP BTP the way [ARC-1](https://github.com/arc-mcp/arc-1) does: an MTA with XSUAA
for the MCP clients' sign-in, the Destination service for the SAP system, and the Connectivity service
for an on-premise system behind the Cloud Connector.”
Named, credentialed addresses of other systems resolved at runtime
Download
Architecture
Download
ABAP platformSAP's application server and development platform for ABAP. For the things here it is the system a developer's editor or an agent's tool reaches over ADT, and a program calls over RFC; where it runs is the deployment's, as for SAP BW/4HANA.
ADAMAn MCP server that debugs ABAP on a connected system over ADT, as one-shot captures or an interactive session, over stdio next to the assistant or as a shared server on SAP BTP Cloud Foundry.independent, abap
@arc-mcp/xsuaa-authThe client-to-server authentication stack for an MCP server on SAP BTP: an XSUAA OAuth proxy, dynamic client registration, a chained bearer verifier, and a separate entrypoint for per-user principal propagation.independent, btp
Cloud ConnectorSAP's on-premises agent that links SAP BTP applications to systems in a customer's own network, as a reverse invoke proxy that exposes only the systems and resources it is configured to allow.sap official, btp
ADT resourcesThe HTTP endpoint an ABAP system exposes as the adt ICF service under /sap/bc/adt, so a client outside the system can reach development objects, delivered with the platform rather than installed.sap official, abap
SAP BTP ABAP environmentSAP's ABAP runtime on BTP: ABAP systems developed in the ABAP Cloud model on SAP HANA Cloud, for cloud apps, OData services and side-by-side extensions of SAP S/4HANA.sap official, btp
SAP Authorization and Trust Management serviceThe OAuth server behind a BTP application: issues the JWT the app checks, holds the scopes and role collections it checks against, and brokers trust to an identity provider. Bound, never installed.sap official, btp
SAP Destination serviceNamed, credentialed addresses of other systems, resolved at runtime — so an application holds no URL and no secret of its own, and the same code reaches a different system in every landscape.sap official, btp
SAP Connectivity serviceThe proxy through which a cloud application reaches an on-premise system behind a Cloud Connector — HTTP, RFC and raw sockets — without that system being exposed.sap official, btp
SAP BTP, Cloud Foundry RuntimeThe Cloud Foundry runtime of SAP BTP: memory for applications in a Cloud Foundry org, run from SAP's Java, Node.js and Python buildpacks or community buildpacks and managed with the standard Cloud Foundry tools.sap official, btp
Your MCP client → ADAMStated in the document, dataClementRingot/ADAM — README, Development, checked 2026-10-26: “
src/http-server.ts
(Streamable HTTP with XSUAA/API-key auth), src/server.ts (MCP), src/config.ts, src/index.ts
(entry point, stdio or --http).”ADAM → ADT resourcesDocumented onlythe ADT resources the server calls on the connected system: it needs a system reachable over HTTP(S) with ADT enabled, and a user with ADT access and debug authorization
ADAM → SAP BTP ABAP environmentDocumented only, under a conditionthe ABAP instance whose service key the server logs on with, opening the browser for the SAP login on the first callIf the SAP system debugged is the SAP BTP ABAP environment, reached with a service key instead of a URL and credentials
ADAM → @arc-mcp/xsuaa-authDocumented only, under a conditionthe authentication stack in front of the
/mcp route and the destination lookups behind itIf the server runs in HTTP mode on SAP BTP Cloud FoundryADAM → SAP Authorization and Trust Management serviceDocumented only, under a conditionthe sign-in of the MCP clients, with dynamic client registration and the
debug scope every tool call needs; the MTA creates the instance from xs-security.jsonIf the server is deployed as a shared server on SAP BTP Cloud FoundryADAM → SAP Destination serviceDocumented only, authentication, outbound, under a conditionexchanges the signed-in MCP user's token at the Destination service for the per-user credentials the ADT calls then carry, so the debugger reaches SAP as that person's own SAP userIf the server is deployed as a shared server on SAP BTP Cloud Foundry
ADAM → SAP Connectivity serviceDocumented only, under a conditionthe forward proxy the ADT calls leave through on their way into the customer's networkIf the deployed server reaches an on-premise SAP system behind the Cloud Connector
ADAM → Cloud ConnectorDocumented only, under a conditionthe tunnel into the customer's network and the certificate mapping that turns the propagated user into an SAP logon name; its access control has to expose
/sap/bc/adt with all sub-pathsIf the deployed server reaches an on-premise SAP systemADAM → SAP BTP, Cloud Foundry RuntimeDocumented only, under a conditionthe runtime the MTA is deployed to, at one instance because an interactive session holds the program and its debugger session in the processIf the server is deployed as a shared server on SAP BTP instead of run locally over stdio
ADAM → ABAP platformDocumented only, data, HTTP, outboundarms the external breakpoints, starts the debugger listener, attaches from the application server the program stopped on and reads the position, call stack and variables, all through the ADT REST API that Eclipse ADT uses
Cloud Connector → SAP Connectivity serviceDocumented only, data, outboundRegistering with the Connectivity service of a subaccount and, with it, providing the tunnel through which applications on SAP BTP reach systems in the on-premise network. The connector works as a reverse invoke proxy, and no port is exposed on the on-premise side.
SAPnot SAP's, or the project's ownauthenticationstated in the documentdocumented onlyunder a condition
README
quoted from ClementRingot/ADAM, readClementRingot/ADAM/README.mdthe maintainer’s wordsOn GitHub
ADAM
ADAM is an MCP server that lets an AI assistant — Claude, GitHub Copilot, Cursor… — debug ABAP code in SAP's own debugger: set breakpoints, run the code, read the variables, step through it. It speaks the ABAP Development Tools (ADT) REST API, as Eclipse does, so nothing has to be installed on the SAP system.
You: Why does ZCL_ORDER=>GET_TOTAL return 0 for order 4711?
Claude: abap_source {type: "CLAS", name: "ZCL_ORDER", method: "get_total"}
abap_debug {type: "CLAS", name: "ZCL_ORDER", breakpoints: [{line: 42, hits: 3}],
variables: ["LS_ITEM-NETWR", "LV_TOTAL"], steps: 2}
→ three iterations of the loop in one run, each with both values and two steps
Others providing
DebuggingDebuggingSeeing what running code did between an input arriving and a result coming out: which code ran, what the values were at each point, and why a value ended up as it did.SAP and community, narrow by design
- dbg_value_statementdbg_value_statementAn ABAP Debugger script that turns a variable's structure or table into the VALUE statement that recreates it, with a tree explorer, also callable as a function module from a report.independent, abapDebugger script generating a VALUE statement for a variable
- dump_infodump_infoDisplays the variables an ABAP short dump captured, for dumps selected on a selection screen; its documentation does not state which dumps it reads, which releases it runs on or how it installs.independent, abapDisplays the variables of ABAP short dumps
- abapsmithabapsmithAn MCP server that lets an LLM develop in ABAP on a live system over ADT, with writes off by default and every mutation recorded in a local journal that can undo it.independent, abapABAP MCP server over ADT with a local journal that can undo writes
- ABAP-Object-VisualizerABAP-Object-VisualizerA debugger script that writes an object hierarchy to the clipboard at a breakpoint as a Graphviz description, for pasting into a renderer such as webgraphviz.com.independent, abapDebugger script exporting an object hierarchy as Graphviz
- abap_debugger_object_graph_extensionabap_debugger_object_graph_extensionAn ABAP debugger extension that shows the object on the debugger's Objects tab as a Graphviz graph in a browser window, built on ABAP Graph and Graphviz-browser and tested on NetWeaver 7.5.independent, abapABAP debugger extension drawing objects as a Graphviz graph
- Graphviz-browserGraphviz-browserA static page that draws a Graphviz graph in a browser, written for the ABAP debugger object graph extension and deployable as BSP pages in the system the debugger runs in.independent, abapStatic page drawing Graphviz graphs for the ABAP debugger extension
- ABAP remote filesystemABAP remote filesystemA Visual Studio Code extension that opens an ABAP system over ADT as an editable filesystem and exposes system tools to GitHub Copilot and external MCP clients.independent, abapVS Code extension editing ABAP systems over ADT as a filesystem
- ABAP Development Tools for EclipseABAP Development Tools for EclipseSAP's Eclipse plugins for ABAP: source, dictionary and CDS editors, Project Explorer, Outline and ABAP Unit, calling ADT resources on the connected system.sap official, abapSAP's Eclipse plugins for ABAP development over ADT
- Smart DebuggerSmart DebuggerA debugger script for the SAP GUI New Debugger that records every step and variable change of an ABAP program, so execution can be stepped backwards with F5 and F8.independent, abapSAP GUI debugger script recording steps so execution can run backwards
Agent access to ABAP codeAgent access to your codeLetting 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, which is a protocol adapter on your own running service, and from agent guidance, which is knowledge handed over as files rather than read from the thing itself.SAP and community, unassessed
- @abap2ui5/mcp-server@abap2ui5/mcp-serverAn MCP server that puts the abap2UI5 development loop on the machine an agent runs on: check the view the ABAP builds, photograph it, deploy the class into a sandbox, boot the app headless and read the errors.community org, abapMCP server for the abap2UI5 check, deploy and run loop
- arc-1-bopf-enharc-1-bopf-enhAn extension of four tools for arc-1, with an ABAP service behind it, that lets an agent read and maintain classic BOPF enhancements of SAP standard business objects.independent, abaparc-1 extension for reading and maintaining BOPF enhancements
- HammerHammerA native macOS code editor for ABAP and CDS, with an Object Navigator, Transport Organizer, Data Browser and Gateway Client in the same app as the editor.independent, abapNative macOS code editor for ABAP and CDS
- arc-1-lsparc-1-lspAn edition of ARC-1 that hands every ADT interaction to SAP's own embedded adt-ls language server instead of a hand-rolled HTTP client.independent, abapEdition of ARC-1 that runs ADT calls through adt-ls
- arc-1arc-1An MCP server in front of the ADT REST API that runs locally and on Cloud Foundry with twelve tools that read, search, write, activate, lint and transport ABAP objects.independent, abapMCP server over the ADT REST API for ABAP objects
- arc1-abap-bridgearc1-abap-bridgeA VS Code extension between arc-1 and ABAP Development Tools for VS Code, so GitHub Copilot can open an ABAP object by name, diff the inactive version and ask the system whether an edit would be accepted.independent, abapVS Code bridge between arc-1 and ADT for VS Code
- arc1-adt-abap-mcp-extarc1-adt-abap-mcp-extOne JAR in Eclipse's dropins that turns on SAP's own ADT MCP server and adds read-only repository tools beside it — so an AI client reads your system without leaving Eclipse.independent, abapEclipse add-on enabling the ADT MCP server with read-only tools
- ABAP Accelerator MCP ServerABAP Accelerator MCP ServerAWS's ABAP MCP server for Amazon Q Developer and Kiro, deployable locally, in Docker or centrally on ECS Fargate with OAuth principal propagation; its repository is no longer maintained.partner, abapAWS's ABAP MCP server for Amazon Q Developer and Kiro
- Modernization Agents for SAP on AWSModernization Agents for SAP on AWSAWS's suite of agents for SAP modernisation work: custom ABAP converted for S/4HANA, PI/PO interfaces moved to Integration Suite, BW objects moved to SAP Datasphere, deployed into a customer's own AWS account and reached only after registration.partner, abapAWS agents for ABAP, PI/PO and BW modernisation work
- @mcp-abap-adt/core@mcp-abap-adt/coreA descendant of the Andreschak and fr0ster servers rebuilt on its own architecture, published as an npm scope and a Claude Code plugin, with Korean and Japanese documentation beside the English.independent, abapABAP ADT MCP server published as an npm scope and plugin
- chandrashekhar-mahajan/abap-mcp-serverchandrashekhar-mahajan/abap-mcp-serverFifteen ADT tools behind five pluggable authentication strategies — Kerberos/SPNEGO, OAuth 2.0, X.509, browser SSO and basic — for systems where basic auth is not an option.independent, abapABAP MCP server with ADT tools and five authentication strategies
- dassian-adtdassian-adtA fork of mcp-abap-abap-adt-api hardened for use: 25 tools, input validation, error intelligence, MCP elicitation, session recovery and a test suite.independent, abapFork of mcp-abap-abap-adt-api with 25 tools and session recovery
- erpl-adterpl-adtOne C++ binary that speaks the ADT REST API as a CLI and as an MCP server — no Eclipse, no NetWeaver RFC SDK, no JVM — and reaches BW/4HANA modelling as well as ABAP.independent, abapC++ binary speaking the ADT REST API as a CLI and MCP server
- bw-modeling-mcpbw-modeling-mcpReads, creates and modifies BW/4HANA modelling objects through the same internal APIs Eclipse BWMT and the BW/4HANA Cockpit use — and can run centrally on BTP with each caller reaching BW as themselves.independent, btpMCP server for BW/4HANA modelling objects
- EPOD ADT MCP ServerEPOD ADT MCP ServerAn MCP server for ABAP that runs inside ABAP Development Tools for Eclipse on the ADT session of each connected project, with a standalone mode that runs with no IDE open.independent, abapMCP server for ABAP on the ADT session, in Eclipse or standalone
- ZARC1_EXTENSION_FORMSZARC1_EXTENSION_FORMSAn extension of four tools for arc-1, with an ABAP backend behind it, that reaches the classic form objects ADT has no API for: SAPscript layout sets, Smart Styles and the TADIR record of a Smart Form.independent, abaparc-1 extension for SAPscript and Smart Forms objects
- fgalastri/MCP_ABAPfgalastri/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.independent, 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.
- fr0ster/mcp-abap-adtfr0ster/mcp-abap-adtFull CRUD across on-premise and ABAP Cloud systems, with five authentication methods and three transports: a library under Apache-2.0 and a standalone server under AGPL-3.0-only.independent, abapABAP MCP server with full CRUD on on-premise and ABAP Cloud
- abapsmithabapsmithAn MCP server that lets an LLM develop in ABAP on a live system over ADT, with writes off by default and every mutation recorded in a local journal that can undo it.independent, abapABAP MCP server over ADT with a local journal that can undo writes
- sap-ai-dev-toolkitsap-ai-dev-toolkitAn MCP proxy that pins an agent's ABAP tools to one SAP system: setup reads the BAS destinations or the local SAP GUI landscape and writes one stdio server per system, leaving the credentials in the destination or in the editor's own login prompts.independent, abapMCP proxy pinning an agent's ABAP tools to one SAP system
- aibap.mcpaibap.mcpA Go server that closes the loop: after create, write and activate it can run the class it just wrote through ADT's classrun and hand the console output back.independent, abapGo MCP server that writes, activates and runs ABAP classes via ADT
- BellaBellaAn Eclipse plugin that puts Claude into ABAP Development Tools: explain, generate, rework and implement from the editor's context menu, completion as ghost text, and a chat whose tools reach the system through the developer's existing ADT logon.independent, abapEclipse plugin bringing Claude into ABAP Development Tools
- Maherd18/sap-mcp-serverMaherd18/sap-mcp-serverAn MCP server for ABAP development over the ADT resources: eight tools, each checked against a JSON policy file before the call reaches the system, with activation and transport release held for a person to approve.independent, abapPolicy-checked MCP server for ABAP development over ADT
- sapdumpmcpsapdumpmcpAn MCP server for SAP dumps: it connects to an ABAP system over the ADT resources and lets an MCP client ask a dump for its description and call stack.independent, abapMCP server reading ABAP short dumps over ADT
- ABAP remote filesystemABAP remote filesystemA Visual Studio Code extension that opens an ABAP system over ADT as an editable filesystem and exposes system tools to GitHub Copilot and external MCP clients.independent, abapVS Code extension editing ABAP systems over ADT as a filesystem
- mcp-abap-abap-adt-apimcp-abap-abap-adt-apiThe write half of the same pair: a thin wrapper over Marcello Urbani's abap-adt-api, exposing lock, edit, activate, transport and syntax check for a full development loop.independent, abapWrite-oriented MCP server over abap-adt-api
- mcp-abap-adtmcp-abap-adtThe read-oriented half of a pair of ABAP MCP servers: high-level tools such as GetProgram, GetClass and GetTable that fetch from a system, aimed at understanding it rather than changing it.independent, abapRead-oriented MCP server fetching ABAP programs, classes, tables
- SAP MCP Connection ManagerSAP MCP Connection ManagerA Windows desktop manager that holds SAP connections and hands them to Claude Desktop or Codex through a local MCP server, each connection carrying a policy that decides what the assistant may change and what data it may read.independent, abapWindows desktop manager handing SAP connections to assistants over MCP
- ABAPilotABAPilotAn MIT-licensed MCP connector for ECC and on-premise S/4HANA that reads ABAP source and dictionary context, whose SAP-side half is a licensed product you install in the system.independent, abapMCP connector for ECC and on-premise S/4HANA with a licensed SAP side
- vibing-steampunkvibing-steampunkAn ADT-to-MCP bridge in Go that reaches past what ADT exposes — cluster tables decoded, spool and job logs read as tables, the IMG searched, selection texts written back.independent, abapADT-to-MCP bridge in Go reaching past what ADT exposes
- ADT MCP ServerADT MCP ServerSAP's own ADT MCP server, and not a package: a preference inside ABAP Development Tools for VS Code that starts a local HTTP MCP server on a port you choose.sap official, abapLocal HTTP MCP server started from ABAP Development Tools for VS Code
- ABAP Development Tools for VS CodeABAP Development Tools for VS CodeSAP's ABAP tools in VS Code: editing, debugging, ABAP Unit, ATC and transports for classes, CDS and RAP objects, over RFC to an on-premise or Private Cloud system and HTTP to a cloud one, with Joule's ADT MCP server and code completion behind an AI-unit licence.sap official, abapSAP's ABAP tools in VS Code for editing, debugging, ATC and transports
- SAP Joule for Developers, ABAP AI capabilitiesSAP Joule for Developers, ABAP AI capabilitiesSAP's AI for ABAP development in ADT for Eclipse and VS Code: chat, code completion, explain, test and CDS generation, RAP logic prediction, and since June 2026 an agentic mode over the ADT MCP Server, metered in AI units through the ABAP AI Hub Service on BTP.sap official, abapSAP's AI for ABAP development in ADT for Eclipse and VS Code
- ABAPDocMCPABAPDocMCPTurns a transport request into a WRICEF technical specification: reads the transport's objects and source over ADT and writes a structured Markdown document with an object-relationship diagram.independent, abapMCP server turning a transport request into a WRICEF specification
- claude-sap-kitclaude-sap-kitA 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.independent, abapClaude Code plugin adding Custom_* tools to arc-1
- Skybuffer AI MCP serverSkybuffer AI MCP serverAn ABAP add-on that serves SAP business data, transactions and development context as MCP tools from an ICF node inside SAP ECC and S/4HANA, each call running as the signed-in user under PFCG authorization checks.independent, abapABAP add-on serving business data and transactions as MCP tools
- abap-adt-cliabap-adt-cliPulls an ABAP package to local files over the ADT REST API in parallel, and pushes edited objects back under a transport — bulk sync rather than one object at a time in SE80 or Eclipse.independent, abapCLI that pulls and pushes ABAP packages as local files over ADT
- workskong/mcp-abap-adtworkskong/mcp-abap-adtA deliberately light MCP adapter over ABAP ADT for object search, source, DDIC metadata, a data preview and runtime diagnostics, read-only in practice and documented in Korean.independent, abapLight MCP adapter for ABAP over ADT, documented in Korean
- KlystronKlystronAn MCP server written in ABAP that runs inside the application server behind an ICF service and exposes typed tools for ABAP development, quality, transports, customizing, roles, Basis operations and integration, with a client-side plugin of SAP skills.independent, abapMCP server in ABAP inside the application server, with agent skills
- pyrfc-mcppyrfc-mcpAn MCP server for calling an SAP system's RFC-enabled function modules from an agent, built so that discovering a function does not authorise calling it: a read or a write is denied unless the function name matches an allowlist the server is configured with.independent, abapMCP server calling RFC-enabled function modules behind an allowlist
- ABAP-AI-CODE-TOOLSABAP-AI-CODE-TOOLSAn optional abapGit package that adds create, modify and delete tools to ABAP AI Code, for ABAP programs and classes, with each diff block approved before it is saved.independent, abapabapGit package adding create, modify and delete tools to ABAP AI Code
- ABAP AI CodeABAP AI CodeAn agentic coding assistant written in ABAP that runs as a SAP GUI report and reads, explains and reviews repository objects inside the system, running an LLM's tool calls as ABAP.independent, abapAgentic coding assistant in ABAP that runs as an SAP GUI report
- VERTEXVERTEXAn extension for ABAP Development Tools for Eclipse and VS Code that shows Simple Data Explorer, AVE and ACE in the editor over the developer's ADT connection.independent, abapADT extension for Eclipse and VS Code showing three SAP GUI tools
Details
Sources
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
runtimesnode
deploymentCloud Foundry, local
discovered viaGitHub API
first seen in the atlas
ecosystem and domainabap, ai-and-agents
Flavors
Standard ABAP
“- An SAP system reachable over HTTP(S) with ADT enabled: SAP NetWeaver / S/4HANA on-premise (SAP_BASIS 7.50 or later), or the SAP BTP ABAP Environment.” — ClementRingot/ADAM — README, Requirements
ABAP Cloud
“- An SAP system reachable over HTTP(S) with ADT enabled: SAP NetWeaver / S/4HANA on-premise (SAP_BASIS 7.50 or later), or the SAP BTP ABAP Environment.” — ClementRingot/ADAM — README, Requirements
History in the atlas
- First seen.
For your agent
- Ref
artifact:clementringot-adam- JSON
- /artifacts/clementringot-adam.json
- MCP
- Connecting an agent