mcp-abap-adt
mcp-abap-adt opens SAP ECC, S/4HANA and BTP ABAP repositories to an agent: analysis, creation and editing of objects through ADT.
- 106 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- The agent can create, change and delete objects in an SAP system.
- The connection uses SAP credentials or service keys.
Install
- Works in
Manual install
npm install -g @mcp-abap-adt/coreThe first Getting Started command. Then `npm install -g @mcp-abap-adt/configurator` and `mcp-conf`.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent can create, change and delete objects in an SAP system.
- The connection uses SAP credentials or service keys.
This is third-party code. Review the repository files before installing.
What it does
mcp-abap-adt is an MCP server for ABAP Development Tools (ADT) on SAP ECC and S/4HANA (on-premise) and SAP BTP ABAP Cloud. The agent gets controlled access to real ABAP repositories so analysis and changes rest on system data. The authors call the mode AI pair programming, not autopilot. Two main workflows. Deep analysis: where-used, object metadata, repository navigation, structure and dependencies. Development with full CRUD: classes, interfaces, function groups and modules, programs, DDIC, CDS, views and service artifacts validated through ADT. Connection: basic (HTTP or RFC), passwordless SNC (RFC) and JWT with browser login via a service key. Transports are stdio, Streamable HTTP and SSE, with a compact variant and read-only (`-ro`) variants.
Who it is for. ABAP developers and SAP consultants who want to connect an agent to their system for code analysis and RAP development.
Good fit when
- All usages of a class or function module must be found.
- A CDS view and service must be built from a description and checked through ADT.
- Before a change the dependencies and impact on other objects must be understood.
- The agent may only read the system, with no writes.
Not a fit when
- The system is older than BASIS 7.50: support is parked on the `parked/legacy-support` branch.
- Policy forbids agent access to a production system.
- Node.js 22 or 24 is not installed.
Example request
Through ADT find every usage of class ZCL_ORDER in the TRIAL system and show its dependencies without changing anything.MCP
- Transport
- stdio, http, sse
- Authentication
- OAuth
Limitations
The full set can create, change and delete ABAP objects, so connect an agent to a test system or use the read-only variants (`mcp-abap-adt-ro`). HTTP needs only Node.js 22 or 24, while RFC and SNC need the SAP NW RFC library on the server machine. Packages ship under different licenses (the repository is Apache-2.0, some server packages AGPL-3.0-only), which matters when embedding. Older BASIS systems below 7.50 are not supported yet.
How to disable. Remove the server entry from the client configuration and the packages with `npm uninstall -g @mcp-abap-adt/core`. Delete service key files in the `service-keys` directory separately.
FAQ
How do I install it?
Run `npm install -g @mcp-abap-adt/core` and `npm install -g @mcp-abap-adt/configurator`, then `mcp-conf --client cline --name abap --mcp TRIAL`.
Which authentication methods exist?
Basic over HTTP or RFC, passwordless SNC over RFC and JWT with browser login via a service key. An existing JWT goes in the `x-sap-jwt-token` header.
Can it be read-only?
Yes, there are `mcp-abap-adt-ro` and `mcp-abap-adt-compact-ro` variants, plus HTTP and SSE versions.
What is a destination?
The name of a local service key file without extension, passed as `--mcp=<destination>`.
Which systems are supported?
SAP ECC and S/4HANA (on-premise) and BTP ABAP Cloud. Systems below BASIS 7.50 are not supported yet.
Discussion
No questions or reviews yet.
Related
MCP serversMCP server to SAP ABAP through ADT: an agent reads code of programs, classes, tables and CDS and searches objects in the system
An MCP server for SAP ABAP: an agent finds objects, reads and edits sources, checks syntax and handles transports through ADT
ARC-1: an MCP server for SAP ABAP systems, safe by default, with reading, code edits, transports and checks through ADT.
vsp is an ADT to MCP bridge: an agent reads and writes ABAP code, runs tests and drives the SAP debugger with no server install
A debugger MCP server: the agent sets breakpoints, steps through code and reads variables of a live program over DAP.
An MCP server for SAP documentation: unified search across SAPUI5, CAP, ABAP, BTP and RAP with BM25 full-text ranking.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| mcp-abap-adt (this card) | no | OAuth | 106 | |
| mcp-abap-abap-adt-api | no | API key | 213 | another MCP for ADT with fewer capabilities; this one has full CRUD, SNC, JWT and read-only variants |
| MCP SAP GUI | no | not required | 146 | works through the SAP GUI; this one reaches the ABAP repository directly through ADT |
README in short
A server with full CRUD for ABAP through ADT, several auth methods and transports. Compact and read-only variants are available.