ABAP-ADT-API MCP-Server

@mario-andreschak

About ABAP-ADT-API MCP-Server

MCP-Server for SAP ABAP wrapping abap-adt-api

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-abap-abap-adt-api": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli",
        "install",
        "@mario-andreschak/mcp-abap-abap-adt-api",
        "--client",
        "claude"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is ABAP-ADT-API MCP-Server?

The ABAP-ADT-API MCP-Server is a Model Context Protocol (MCP) server that acts as a wrapper for the abap-adt-api, enabling seamless communication between ABAP systems and MCP clients. It provides tools and resources for managing ABAP objects, handling transport requests, performing code analysis, and more. It is intended for ABAP developers working with SAP systems via ADT (ABAP Development Tools).

How to use ABAP-ADT-API MCP-Server?

Install via Smithery using npx -y @smithery/cli install @mario-andreschak/mcp-abap-abap-adt-api --client claude, or clone the repository, run npm install, copy .env.example to .env, set SAP_URL, SAP_USER, SAP_PASSWORD (and optionally SAP_CLIENT, SAP_LANGUAGE), build with npm run build, and start with npm run start. Integrate with an MCP client such as Cline using the provided JSON configuration. Key tools include searchObject, transportInfo, lock, unLock, setObjectSource, getObjectSource, syntaxCheckCode, activate, and various DDIC inspection tools.

Key features of ABAP-ADT-API MCP-Server

Securely authenticate with ABAP systems using the login tool.
Manage ABAP objects with create, read, update, delete operations.
Handle transport requests using createTransport and transportInfo.
Perform syntax checks and retrieve code completion suggestions.
Manage sessions with dropSession and logout.
Inspect DDIC repository, table contents, and object structures.

Use cases of ABAP-ADT-API MCP-Server

Modify ABAP source code with proper locking, transport, and syntax checking.
Retrieve and analyze ABAP object metadata and DDIC definitions.
Automate transport request creation and object activation.
Perform ad-hoc database queries via runQuery or tableContents.

FAQ from ABAP-ADT-API MCP-Server

How does ABAP-ADT-API MCP-Server differ from the mcp-abap-adt server?

This server (mcp-abap-abap-adt-api) exposes lower-level ADT API tools (e.g., searchObject, lock, setObjectSource), while the separate mcp-abap-adt project provides higher‑level tools like GetTable and GetStructure.

What runtime dependencies are required?

Node.js is required. The server also needs network access to an ABAP system and credentials supplied via environment variables (SAP_URL, SAP_USER, SAP_PASSWORD). Self‑signed certificates may require setting NODE_TLS_REJECT_UNAUTHORIZED="0".

Where does the ABAP data reside?

All ABAP source code, transport requests, and DDIC data reside on the SAP system. The server retrieves and modifies that data via ADT APIs; no local file synchronization occurs.

How are transport requests managed?

Use createTransport to create a new transport, transportInfo to get details on an object’s transport, and include the transport number in setObjectSource to assign modifications to a transport. Locks are obtained via lock and released via unLock.

How does authentication work?

The server authenticates using the login tool or via initial environment variables (SAP_USER and SAP_PASSWORD). A session is cached and can be dropped with dropSession or terminated with logout.

Frequently asked questions

How does ABAP-ADT-API MCP-Server differ from the mcp-abap-adt server?

This server (`mcp-abap-abap-adt-api`) exposes lower-level ADT API tools (e.g., `searchObject`, `lock`, `setObjectSource`), while the separate `mcp-abap-adt` project provides higher‑level tools like `GetTable` and `GetStructure`.

What runtime dependencies are required?

Node.js is required. The server also needs network access to an ABAP system and credentials supplied via environment variables (`SAP_URL`, `SAP_USER`, `SAP_PASSWORD`). Self‑signed certificates may require setting `NODE_TLS_REJECT_UNAUTHORIZED="0"`.

Where does the ABAP data reside?

All ABAP source code, transport requests, and DDIC data reside on the SAP system. The server retrieves and modifies that data via ADT APIs; no local file synchronization occurs.

How are transport requests managed?

Use `createTransport` to create a new transport, `transportInfo` to get details on an object’s transport, and include the transport number in `setObjectSource` to assign modifications to a transport. Locks are obtained via `lock` and released via `unLock`.

How does authentication work?

The server authenticates using the `login` tool or via initial environment variables (`SAP_USER` and `SAP_PASSWORD`). A session is cached and can be dropped with `dropSession` or terminated with `logout`.