mcp-abap-adt

mcp-abap-adt provides an MCP server that connects to ABAP systems (ECC, S/4HANA on-premises or ABAP Cloud on SAP BTP) and exposes ABAP development tooling through the MCP protocol. It supports multiple transport modes (stdio, HTTP, SSE) and allows authenticated access via JWT/XSUAA destinations or service keys. Use cases include deep ABAP analysis (where-used, object metadata, dependencies), high-level ABAP development (RAP and classic ABAP artifacts), and automated documentation or RAG workflows that rely on up-to-date repository facts. You can run it as a standalone server or embed it into existing applications. To select the target ABAP system, place a service key JSON in the local service-keys directory and start the server with the destination name via --mcp=<destination>.

Getting started typically involves installing the server globally or locally, configuring a destination for your ABAP system, and then running the MCP server in your preferred transport mode (stdio by default, or HTTP/SSE for streaming). For CLI usage, start the server and pass a destination with --mcp to choose the appropriate service key. The server exposes a rich set of capabilities for object inspection, code and semantic analysis, and CRUD operations across ABAP artifacts, enabling AI-assisted workflows and automated data extraction for documentation and RAG pipelines.

Prerequisites:

• Node.js (LTS version, e.g., 14+ or 16+)
• npm or yarn
• Access to an ABAP system (ECC/S/4HANA or ABAP Cloud) with a service key file per destination stored locally (e.g., in ~/.config or your project directory under service-keys)

Install the MCP server (standalone CLI) and dependencies:

1. Install the MCP server package globally (example): npm install -g mcp-abap-adt // If the package is published under a scoped name, use the appropriate scope, e.g., @mcp-abap-adt/mcp-abap-adt
2. (Optional) Install configurator if you plan to generate client configurations: npm install -g @mcp-abap-adt/configurator
3. Prepare your destinations by placing JSON service keys under the conventional path, for example:
   • Unix/Linux/macOS: ~/.config/mcp-abap-adt/service-keys/<destination>.json
   • Windows: %USERPROFILE%\Documents\mcp-abap-adt\service-keys<destination>.json
4. Run the server in your preferred transport mode, specifying the destination with --mcp=<destination>. Example stdio: mcp-abap-adt --mcp=TRIAL Example HTTP transport: mcp-abap-adt --transport=http --mcp=TRIAL --url http://localhost:3000/mcp/stream/http

If you are integrating the server into an existing project, you can also embed it programmatically using the EmbeddableMcpServer API described in the project docs.

Tips and troubleshooting:

• Destination-based authentication is the default workflow. Ensure your service key files are present in the expected folder and named correctly without the extension.
• When running behind proxies or in containers, expose the transport port(s) you use (stdio doesn’t require a network port, but HTTP/SSE does).
• If you switch between on-prem and BTP ABAP systems, maintain separate destination keys and select via --mcp=<destination> each time you start the server.
• For debugging, enable verbose logs in your environment (check the project's logging options) to trace authentication and transport connections.
• The server supports a wide range of ABAP tooling capabilities (e.g., GetWhereUsed, GetObjectInfo, CreateTransport, GetProgFullCode, CreateClass, UpdateView, etc.). Refer to the documentation for specifics per capability and required permissions on the ABAP system.