mcp-abap-adt: Your Gateway to ABAP Development Tools (ADT)

Acknowledgment: This project was originally inspired by mario-andreschak/mcp-abap-adt. We started with the core concept and then evolved it into an independent project with our own architecture and features.

This project provides a server that allows you to interact with SAP ABAP systems using the Model Context Protocol (MCP). Think of it as a bridge that lets tools like Cline (a VS Code extension) talk to your ABAP system and retrieve information like source code, table structures, and more.

Architecture

The project provides two main usage patterns:

1. Standalone MCP Server (Default)

Run as a standalone MCP server with stdio, HTTP, or SSE transport:

2. Handler Exporter (For Embedding)

Export handlers for integration into existing servers (e.g., SAP CAP/CDS applications):

Quick Start

1. Install: See Installation Guide

2. Configure: See Client Configuration

3. Use: See Available Tools

Features

• 🏗️ Domain Management: GetDomain, CreateDomain, UpdateDomain - Create, retrieve, and update ABAP domains

• 📊 Data Element Management: GetDataElement, CreateDataElement, UpdateDataElement - Create, retrieve, and update ABAP data elements

• 📦 Table Management: GetTable, CreateTable, GetTableContents - Create and retrieve ABAP database tables with data preview

• 🏛️ Structure Management: GetStructure, CreateStructure - Create and retrieve ABAP structures

• 👁️ View Management: GetView, CreateView, UpdateView - Create and manage CDS Views and Classic Views

• 🎓 Class Management: GetClass, CreateClass, UpdateClass - Create, retrieve, and update ABAP classes

• 📝 Program Management: GetProgram, CreateProgram, UpdateProgram - Create, retrieve, and update ABAP programs

• 🔧 Behavior Definition (BDEF) Management: GetBehaviorDefinition, CreateBehaviorDefinition, UpdateBehaviorDefinition - Create and manage ABAP Behavior Definitions with support for Managed, Unmanaged, Abstract, and Projection types

• 📋 Metadata Extension (DDLX) Management: CreateMetadataExtension, UpdateMetadataExtension - Create and manage ABAP Metadata Extensions

• ⚡ Activation: ActivateObject - Universal activation for any ABAP object

• 🚚 Transport Management: CreateTransport, GetTransport - Create and retrieve transport requests

• 🔍 Enhancement Analysis: GetEnhancements, GetEnhancementImpl, GetEnhancementSpot - Enhancement discovery and analysis

• 📋 Include Management: GetIncludesList - Recursive include discovery

• 🔍 System Tools: GetInactiveObjects - Monitor inactive objects waiting for activation

• 🚀 SAP BTP Support: JWT/XSUAA authentication with browser-based token helper

• 🔑 Destination-Based Authentication: Service key-based authentication with automatic token management (see Client Configuration)

• 💾 Freestyle SQL: GetSqlQuery - Execute custom SQL queries via ADT Data Preview API

ℹ️ ABAP Cloud limitation: Direct ADT data preview of database tables is blocked by SAP BTP backend policies. The server returns a descriptive error when attempting such operations. On-premise systems continue to support data preview.

Documentation

For Users

• Installation Guide - Installation instructions for all platforms

• Client Configuration - How to configure MCP clients

• Available Tools - Complete list of available MCP tools

For Administrators

• Installation Guide - Platform-specific installation guides

For Developers

• Architecture Documentation - System architecture and design decisions

• Development Documentation - Testing guides and development resources

• CHANGELOG.md - Version history and changes

Dependencies

This project uses two npm packages:

• @mcp-abap-adt/connection – connection/auth/session layer

• @mcp-abap-adt/adt-clients – Builder-first ADT clients

These packages are automatically installed via npm install and are published to npm.

Running the Server

Global Installation (Recommended)

After installing globally with npm install -g, you can run from any directory:

Development Mode

Environment Configuration

The server automatically looks for .env file in this order:

1. Path specified via --env argument

2. .env in current working directory (where you run the command)

3. .env in package installation directory

Example .env file:

For JWT authentication (SAP BTP):

Generate .env from Service Key (JWT):

This will automatically create/update .env file with JWT tokens and connection details.

Command-Line Options

Authentication:

• --auth-broker - Force use of auth-broker (service keys), ignore .env file

• --auth-broker-path=<path> - Custom path for auth-broker service keys and sessions

• --unsafe - Enable file-based session storage (persists tokens to disk). By default, sessions are stored in-memory (secure, lost on restart)

Examples:

See Client Configuration for complete configuration options.

Handler logging switches

• AUTH_LOG_LEVEL=error|warn|info|debug — sets base log level for handler logger; DEBUG_AUTH_LOG=true also enables debug.

• HANDLER_LOG_SILENT=true — fully disables handler logging.

• DEBUG_CONNECTORS=true — verbose connection logging in high-level handlers.

• DEBUG_HANDLERS=true — enables verbose logs for selected read-only/system handlers.

Development

Testing

Test logging switches

• TEST_LOG_LEVEL=error|warn|info|debug — controls test logger verbosity (DEBUG_TESTS/DEBUG_ADT_TESTS/DEBUG_CONNECTORS force debug).

• TEST_LOG_FILE=/tmp/adt-tests.log — writes test logs to a file (best-effort).

• TEST_LOG_SILENT=true — disables test logging pipeline (console output muted).

• TEST_LOG_COLOR=true — adds colored/prefixed tags to test log lines.

• All console.* in tests are routed through the test logger with a [test] prefix.

Building

Developer Tools

Contributors

Thank you to all contributors! See CONTRIBUTORS.md for the complete list.