MCP Server — mario-andreschak/mcp-abap-aba

MCP server wrapping abap-adt-api for ABAP ADT development workflows against SAP systems

What the server does

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

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.

• 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

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• query — (string, required) The search term
• objSourceUrl — (string, required) The object's URI (obtained from searchObject)
• objectUrl — (string, required) The object's URI
• lockHandle — (string, required) The lock handle obtained from the lock operation
• objectSourceUrl — (string, required) The object's URI with the suffix /source/main. Example: /sap/bc/adt/oo/classes/zcl_invoice_xml_gen_model/source/main
• source — (string, required) The complete, modified ABAP source code
• transport — (string, optional) The transport request number
• code — (string, required) The ABAP source code to check
• url — (string, optional) The URL of the object
• mainUrl — (string, optional) The main URL
• mainProgram — (string, optional) The main program
• version — (string, optional) The version

Credentials and setup notes

Configuration is passed through the environment: SAP_URL, SAP_USER, SAP_PASSWORD, SAP_CLIENT, SAP_LANGUAGE, NODE_TLS_REJECT_UNAUTHORIZED. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• 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

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — query, objSourceUrl, objectUrl and 10 more — is a fair guide to whether it matches your workflow. It is maintained by mario-andreschak; worth a glance at recent repository activity before you build anything load-bearing on it.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Recorded tools

• query — (string, required) The search term.
• objSourceUrl — (string, required) The object's URI (obtained from searchObject).
• objectUrl — (string, required) The object's URI.
• lockHandle — (string, required) The lock handle obtained from the lock operation.
• objectSourceUrl — (string, required) The object's URI with the suffix /source/main. Example: /sap/bc/adt/oo/classes/zcl_invoice_xml_gen_model/source/main
• source — (string, required) The complete, modified ABAP source code.
• transport — (string, optional) The transport request number.
• code — (string, required) The ABAP source code to check.
• url — (string, optional) The URL of the object.
• mainUrl — (string, optional) The main URL.
• mainProgram — (string, optional) The main program.
• version — (string, optional) The version.
• object — The object to be activated.

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.