ABAP-ADT-API MCP-Server

Exposes ABAP ADT capabilities via MCP for object management, transports, and code checks.
  • typescript

0

GitHub Stars

typescript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "dachienit-mcp_abap": {
      "command": "node",
      "args": [
        "PATH_TO_YOUR/mcp-abap-abap-adt-api/dist/index.js"
      ],
      "env": {
        "SAP_URL": "YOUR_SAP_URL",
        "SAP_USER": "YOUR_SAP_USERNAME",
        "SAP_CLIENT": "YOUR_SAP_CLIENT",
        "SAP_LANGUAGE": "YOUR_SAP_LANGUAGE",
        "SAP_PASSWORD": "YOUR_SAP_PASSWORD",
        "NODE_TLS_REJECT_UNAUTHORIZED": "0"
      }
    }
  }
}

You can extend your ABAP development workflow by running an MCP server that exposes ABAP Development Tools (ADT) functionalities as MCP endpoints. This server lets you authenticate, read and modify ABAP objects, manage transports, and perform syntax checks from MCP clients, streamlining ABAP development within your toolchain.

How to use

To use this MCP server with an MCP client, run the local MCP server and connect your client using the provided MCP entry. The server exposes a set of tools that let you search for ABAP objects, read and modify sources, manage transports, run syntax checks, and activate changes. You will typically start the server after building the project, then point your MCP client at the local process.

How to install

Prerequisites: you need Node.js installed and access to an ABAP system with valid credentials.

  1. Clone the project repository to your workspace.

  2. Install dependencies.

  3. Configure environment variables to connect to your ABAP system (see the example below).

  4. Build the project.

  5. Run the server.

Additional notes

Configuration focuses on ABAP system access via ADT APIs. You can set up environment variables for SAP connection details and certificates as needed. The server can be launched in local development environments for testing and integration with MCP clients.

Security and operation tips: don’t hard-code credentials in production. Use secure environment management for SAP access details and TLS settings. If you use self-signed certificates, you may temporarily disable TLS verification during development, but re-enable it for production.

Configuration example for local running

{
  "mcp-abap-abap-adt-api": {
    "command": "node",
    "args": [
      "PATH_TO_YOUR/mcp-abap-abap-adt-api/dist/index.js"
    ],
    "disabled": true,
    "autoApprove": []
  }
}

Troubleshooting and tips

If you encounter connection or authentication issues, verify that your SAP URL, user, password, client, and language are correctly set in your environment. Check that the server process has started and is listening on the expected path. Review lock/unlock workflows if you modify ABAP sources and ensure you have a valid lock handle for source modifications.

Example workflow for ABAP code modification

  1. Find the ABAP object with a search tool to obtain its URI.

  2. Retrieve the current source using the appropriate getObjectSource call with the "/source/main" suffix.

  3. Locally clone and modify the source code as needed.

  4. Obtain transport information for the object if required.

  5. Lock the object to prepare for changes and obtain a lock handle.

  6. Submit the modified source via setObjectSource, including the lock handle and optional transport number.

  7. Run a syntax check with syntaxCheckCode to validate the changes.

  8. Activate the object and unlock when appropriate.

Available tools

login

Authenticate with the ABAP system to establish a session for subsequent operations.

searchObject

Find ABAP objects by a query term and obtain their URIs.

getObjectSource

Retrieve the source code for an ABAP object, with the /source/main suffix.

lock

Lock an ABAP object to prepare it for modification and obtain a lockHandle.

setObjectSource

Submit modified ABAP source for an object, including lockHandle and optional transport.

syntaxCheckCode

Perform a syntax check on ABAP source code and return errors if any.

activate

Activate an ABAP object after modifications.

unLock

Unlock a previously locked ABAP object.

transportInfo

Retrieve transport information for a given ABAP object.

getTable

Retrieve the structure of an ABAP Dictionary table.

GetStructure

Retrieve the structure of an ABAP Dictionary structure.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
ABAP-ADT-API MCP-Server MCP Server - dachienit/mcp_abap | VeilStrat