Happy slice of mcp pizzaMCP.pizza

mcp-abap-abap-adt-api

MCP.Pizza Chef: mario-andreschak

Roughly 126 separate tools are registered across 25 groups here, covering object search, reading and rewriting source, locking and unlocking, activation, syntax and quality checks, unit tests, transport requests, debugging, renaming, Git and data dictionary access. Sign-in uses your genuine SAP username and password rather than a key, and those sit in the config file as plain text. One of the tools deletes objects outright, with no confirmation and no read-only mode anywhere. The author labels the whole project experimental.

Coding
Data

Use This MCP server To

Find an ABAP class by name and read its source Ask my assistant to fix a syntax error in a program Create a transport request without leaving the chat Run the unit tests for a class and explain the failures Check a program against our code quality rules

README

DISCLAIMER: This server is still in experimental status! Use it with caution!

ABAP-ADT-API MCP-Server

Description

The MCP-Server mcp-abap-abap-adt-api is a Model Context Protocol (MCP) server designed to facilitate seamless communication between ABAP systems and MCP clients. It is a wrapper for abap-adt-api and provides a suite of tools and resources for managing ABAP objects, handling transport requests, performing code analysis, and more, enhancing the efficiency and effectiveness of ABAP development workflows.

The server is published on npm as mcp-abap-abap-adt-api and listed in the MCP Registry as io.github.mario-andreschak/mcp-abap-abap-adt-api, so most MCP clients can install it with a single command (or a single click — see FLUJO below).

Related project: For higher-level, read-oriented ABAP tools (GetProgram, GetClass, GetTable, …) see the separate mcp-abap-adt server. This server (mcp-abap-abap-adt-api) exposes the lower-level ADT API (lock/unlock, edit source, transports, activation, syntax checks, DDIC access, …) for full read/write development workflows.

Features

  • Authentication: Securely authenticate with ABAP systems using the login tool.
  • Object Management: Create, read, update, and delete ABAP objects seamlessly.
  • Transport Handling: Manage transport requests with tools like createTransport and transportInfo.
  • Code Analysis: Perform syntax checks and retrieve code completion suggestions.
  • Extensibility: Easily extend the server with additional tools and resources as needed.
  • Session Management: Handle session caching and termination using dropSession and logout.

Prerequisites

  • An SAP ABAP System reachable via ADT (ABAP Development Tools). You'll need the system URL, a username and password, and the client number. Ensure the /sap/bc/adt service is active in transaction SICF (your basis administrator can help).
  • Node.js and npm — download the LTS version from nodejs.org. Verify with node -v and npm -v.

Installation

There are three ways to use this server, from easiest to most manual:

mcp-abap-abap-adt-api FAQ

What credentials does it need?
No key. It needs a real SAP login: the system address, your username, your password and the client number, and they are stored in the config file as plain text.
Can it break or delete things in my SAP system?
Yes. It can rewrite source, activate objects and delete them, with no confirmation step and no read-only mode, so point it at a sandbox system before anything that matters.
How many tools does it add?
About 126, grouped into 25 areas that run from source editing and transports through to debugging, tracing and quality checks.
Which apps does it work in?
Any assistant that starts a local helper; the readme uses Cline and Claude Desktop as examples. A companion app called FLUJO can also re-host it at a local web address for apps that need one.
Is it ready for real production work?
The readme opens with a warning that it is experimental and should be used with caution, so treat that as the honest answer.
What else has to be installed?
Node.js, plus an SAP system reachable through ABAP Development Tools with the ADT service switched on, which usually means asking your basis administrator.
Is there a security catch to watch for?
The instructions offer a setting that switches off certificate checking for self-signed certificates. It is marked development only and it does weaken the connection.
Is there a safer read-only option?
The same author points to a separate project, mcp-abap-adt, which offers higher-level tools aimed at reading rather than changing.