Mcp Abap Adt
by
Provides an MCP server for SAP ABAP Development Tools (ADT) that enables full CRUD operations, JWT/XSUAA and service‑key authentication across SAP BTP ABAP Cloud and on‑premise ECC/S/4HANA systems.
Mcp Abap Adt Overview
What is Mcp Abap Adt about?
Mcp Abap Adt delivers a model‑context‑protocol (MCP) server exposing ABAP ADT capabilities. It connects AI agents or other clients to real ABAP repositories, allowing deep analysis and high‑level development while respecting system‑side validation.
How to use Mcp Abap Adt?
- Install the CLI globally or on‑the‑fly:
npx mcp-abap-adt --help - Configure a destination – place a service‑key JSON file in
~/.config/mcp-abap-adt/service-keys/(or the Windows equivalent) and reference it with the--mcp=<destination>flag. - Start the server in the desired transport mode:
- StdIO (default, for MCP clients):
npx mcp-abap-adt --transport=stdio --mcp=TRIAL - HTTP:
npx mcp-abap-adt --transport=http --http-port=8080 - SSE:
npx mcp-abap-adt --transport=sse --sse-port=3001
- StdIO (default, for MCP clients):
- Configure the client using the companion configurator (
@mcp-abap-adt/configurator) or manually via JSON/TOML.
Key features of Mcp Abap Adt
- Full CRUD for ABAP objects: classes, interfaces, function modules, programs, DDIC, CDS/View, RAP artifacts.
- Multi‑system support – on‑premise ECC/S/4HANA, SAP BTP ABAP Cloud, and legacy systems via RFC.
- Authentication options – JWT/XSUAA, service‑key (destination‑based), and basic/RFC credentials.
- Transport mechanisms – stdio, HTTP, Server‑Sent Events (SSE).
- Rich analysis tools – where‑used, object structure, AST, semantic analysis, include discovery, enhancement inspection.
- Transport & activation – create transport requests, activate objects automatically.
- Embeddable server – can be instantiated inside other Node.js applications.
- Extensive documentation – user guide, admin guide, developer architecture docs.
Use cases of Mcp Abap Adt
- Impact analysis before refactoring large ABAP codebases.
- Rapid RAP development with AI‑assisted pair programming.
- Migration planning by extracting repository metadata for cloud readiness.
- Automated documentation generation and retrieval for RAG pipelines.
- Continuous integration pipelines that need to create or modify ABAP artifacts programmatically.
FAQ from the Mcp Abap Adt
Q: Do I need a full ABAP Cloud tenant to use the server? A: No. It works with on‑premise ECC/S/4HANA via HTTP or RFC and with ABAP Cloud using JWT/XSUAA.
Q: Can I run the server without installing it globally?
A: Yes. Use npx mcp-abap-adt to execute the package directly.
Q: Where are service‑key files stored?
A: ~/.config/mcp-abap-adt/service-keys/<destination>.json on Unix/macOS or %USERPROFILE%\Documents\mcp-abap-adt\service-keys\<destination>.json on Windows.
Q: How do I switch between stdio and HTTP transports?
A: Provide the --transport flag (stdio, http, or sse) when starting the server.
Q: Is there support for legacy systems that cannot use HTTP?
A: Yes, the server can connect via RFC by setting --connection-type=rfc and providing the corresponding credentials.
Mcp Abap Adt's README
mcp-abap-adt: Your Gateway to ABAP Development Tools (ADT)
mcp-abap-adt is an MCP server for ABAP ADT in SAP ECC/S/4HANA (on-premise) and SAP BTP ABAP Cloud systems. It gives agents controlled access to real ABAP repositories through ADT, so analysis and changes are grounded in system data instead of assumptions. It is built for AI-assisted pair programming (AIPNV: AI Pairing, Not Vibing), not autopilot vibe coding.
Primary workflows:
- Deep ABAP analysis: where-used, object metadata, repository navigation, object structure, semantic analysis, dependency and impact exploration.
- High-level ABAP development: rapid CRUD and iterative updates for RAP and classic ABAP artifacts (classes, interfaces, function groups/modules, programs, DDIC, CDS/view/service artifacts), validated through ADT flows.
Why teams use it:
- Full CRUD (not read-only): create, read, update, and delete ABAP artifacts
- Works with On-Premise (ECC/S/4HANA), ABAP Cloud (BTP), and Legacy systems (BASIS < 7.50 via RFC)
- JWT/XSUAA, service key (destination-based), and RFC authorization
- Multiple transports: stdio, HTTP, SSE
- Rich tool surface for ABAP objects, metadata, transports, and search
Authorization & Destinations (Important): A destination is the filename of a service key stored locally. You place service keys in the service-keys directory, and use --mcp=<destination> to select which one to use. This is the primary auth model for on‑prem and BTP systems. See Authentication & Destinations.
You can configure MCP clients either manually (JSON/TOML) or via the configurator CLI (@mcp-abap-adt/configurator, repo: mcp-abap-adt-conf).
Table of Contents
- Getting Started
- Architecture
- Quick Start
- Use Cases
- Target Users
- Capabilities (High-Level Focus)
- Terminology
- Authorization & Destinations
- Registries
- Features
- Documentation
- Dependencies
- Running the Server
Getting Started
Install the server and configure your client using the configurator:
npm install -g @mcp-abap-adt/core
npm install -g @mcp-abap-adt/configurator
# stdio (destination)
mcp-conf --client cline --name abap --mcp TRIAL
# HTTP (streamable HTTP)
mcp-conf --client copilot --name abap --transport http --url http://localhost:3000/mcp/stream/http --mcp trial
Full configurator usage (separate repo): CLIENT_INSTALLERS.md.
Terminology
Destination: a local service key filename. You store service keys in the standard service-keys directory, and pass the filename (without extension) via --mcp=<destination> to select which system to use.
See docs/user-guide/TERMINOLOGY.md for the full list.
Authorization & Destinations
Destination-based auth is the default. Drop service keys into the standard platform folder and use the filename as your destination:
mcp-abap-adt --transport=stdio --mcp=TRIAL
Standard service key paths:
- Unix (Linux/macOS):
~/.config/mcp-abap-adt/service-keys/<destination>.json - Windows:
%USERPROFILE%\\Documents\\mcp-abap-adt\\service-keys\\<destination>.json
For full details (paths, .env, direct headers), see Authentication & Destinations.
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:
mcp-abap-adt # stdio (default)
mcp-abap-adt --transport=http # HTTP mode
mcp-abap-adt --transport=sse # SSE mode
2. Embeddable Server (For Integration)
Embed MCP server into existing applications (e.g., SAP CAP/CDS, Express):
import { EmbeddableMcpServer } from '@mcp-abap-adt/core/server';
const server = new EmbeddableMcpServer({
connection, // Your AbapConnection instance
logger, // Optional logger
exposition: ['readonly', 'high'], // Handler groups to expose
});
await server.connect(transport);
Quick Start
- Install server: See Installation Guide
- Configure client (auto): Use
mcp-conffrom@mcp-abap-adt/configurator(repo:mcp-abap-adt-conf, docs: CLIENT_INSTALLERS.md) - Configure client (manual): See Client Configuration
- Use:
Use Cases
- Impact analysis / where-used before changes: map object usage and probable blast radius.
- Dependency audit: inspect links across classes, interfaces, DDIC, CDS/views, and RAP artifacts.
- Migration and cleanup prep: extract repository facts to plan refactoring or cloud-readiness work.
- RAP and ABAP iterative development: create/update artifacts quickly with ADT-backed operations.
- Automated documentation and RAG ingestion: pull structured facts from ABAP systems for downstream tooling.
Target Users
- ABAP developers and ABAP architects
- RAP developers
- Team leads and tech leads who need fast repository visibility
- Teams building RAG/agent workflows for SAP landscapes
Capabilities (High-Level Focus)
Key examples of high-value workflows and tools:
- Repository and impact analysis:
GetWhereUsed,DescribeByList,GetObjectStructure,GetObjectInfo,SearchObject,GetPackageTree,GetPackageContents - Code and semantic introspection:
GetAbapAST,GetAbapSemanticAnalysis,GetIncludesList,GetProgFullCode - RAP development:
CreateBehaviorDefinition,UpdateBehaviorDefinition,CreateBehaviorImplementation,UpdateBehaviorImplementation,CreateServiceDefinition,UpdateServiceDefinition,CreateMetadataExtension,UpdateMetadataExtension - CDS/View development:
CreateView,UpdateView,GetView,DeleteView - ABAP OO CRUD:
CreateClass,UpdateClass,GetClass,DeleteClass,CreateInterface,UpdateInterface,GetInterface,DeleteInterface - Function module/group CRUD:
CreateFunctionGroup,UpdateFunctionGroup,GetFunctionGroup,DeleteFunctionGroup,CreateFunctionModule,UpdateFunctionModule,GetFunctionModule,DeleteFunctionModule - Transport and activation support:
CreateTransport,GetTransport,ActivateObject
Registries
Published in the official MCP Registry and listed on Glama.ai.
- MCP Registry: docs/deployment/MCP_REGISTRY.md
- Glama.ai:
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 - 🧪 Runtime Diagnostics:
RuntimeCreateProfilerTraceParameters,RuntimeListProfilerTraceFiles,RuntimeGetProfilerTraceData,RuntimeListDumps,RuntimeGetDumpById- Profiling and dump analysis with JSON payloads - 📡 Runtime Feeds:
RuntimeListFeeds,RuntimeListSystemMessages,RuntimeGetGatewayErrorLog- Feed reader, SM02 system messages, Gateway error log - 🚀 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
- Docs Index - Full documentation index
- Installation Guide - Installation overview and platform guides
- User Guide - End-user docs (auth, config, tools)
- Authentication & Destinations - Destination-based auth and service keys
- Handlers Management - Enable/disable handler groups
- Configurator:
@mcp-abap-adt/configurator(repo:mcp-abap-adt-conf) provides themcp-confCLI to auto-configure clients - Tools by level
For Administrators
- Deployment Docs - MCP Registry, Docker, release notes
- Server Configuration - YAML config reference
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:
# Show help
mcp-abap-adt --help
# Default HTTP mode (works without .env file)
mcp-abap-adt
# HTTP mode on custom port
mcp-abap-adt --http-port=8080
# Use stdio mode (for MCP clients, requires .env file or --mcp parameter)
mcp-abap-adt --transport=stdio
# Use stdio mode with auth-broker (--mcp parameter)
mcp-abap-adt --transport=stdio --mcp=TRIAL
# Use env destination from platform sessions store
mcp-abap-adt --env=trial
# Use explicit .env file path
mcp-abap-adt --env-path=/path/to/my.env
# SSE mode (requires .env file or --mcp parameter)
mcp-abap-adt --transport=sse --sse-port=3001
# SSE mode with auth-broker (--mcp parameter)
mcp-abap-adt --transport=sse --mcp=TRIAL
Development Mode
# Build and run locally
npm run build
npm start
# HTTP mode
npm run start:http
# SSE mode
npm run start:sse
# Legacy v1 server (for backward compatibility)
npm run start:legacy
Environment Configuration
Env resolution:
--env-path=<path|file>(orMCP_ENV_PATH) for explicit.envfile.- Absolute path: used as-is.
- Relative path or file name only (e.g.
my.env): resolved from current working directory.
--env=<destination>for destination file in standard sessions store:- Unix:
~/.config/mcp-abap-adt/sessions/<destination>.env - Windows:
%USERPROFILE%\\Documents\\mcp-abap-adt\\sessions\\<destination>.env
- Unix:
- Fallback to
.envin current working directory.
Example .env file:
SAP_URL=https://your-sap-system.com
SAP_CLIENT=100
SAP_AUTH_TYPE=basic
SAP_USERNAME=your-username
SAP_PASSWORD=your-password
For JWT authentication (SAP BTP):
SAP_URL=https://your-btp-system.com
SAP_CLIENT=100
SAP_AUTH_TYPE=jwt
SAP_JWT_TOKEN=your-jwt-token
For legacy systems (RFC):
SAP_URL=https://your-legacy-system.com
SAP_CLIENT=100
SAP_AUTH_TYPE=basic
SAP_USERNAME=your-username
SAP_PASSWORD=your-password
SAP_CONNECTION_TYPE=rfc
See RFC Setup Guide for prerequisites (SAP NW RFC SDK).
Generate .env from Service Key (JWT):
# Install the connection package globally (one-time setup)
npm install -g @mcp-abap-adt/connection
# Generate .env file from service key JSON
mcp-auth auth -k path/to/service-key.json
This will automatically create/update .env file with JWT tokens and connection details.
.env comments rule: only full-line comments are supported (lines that start with #).
Inline comments are not parsed, so keep comments on separate lines.
Claude recommendation: place the service key in the service-keys directory and use --mcp=<destination> (avoid manual JWT tokens).
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--browser-auth-port=<port>- Override OAuth browser callback port (default: 5000 for HTTP, 4000 for SSE, 4001 for stdio)--connection-type=<http|rfc>- SAP connection transport:http(default) orrfc(legacy systems)--unsafe- Enable file-based session storage (persists tokens to disk). By default, sessions are stored in-memory (secure, lost on restart)
When --mcp=<destination> is specified, automatic fallback loading of ./.env is skipped.
Examples:
# Use auth-broker with file-based session storage (persists tokens)
mcp-abap-adt --auth-broker --unsafe
# Use auth-broker with in-memory session storage (default, secure)
mcp-abap-adt --auth-broker
# Custom path for service keys and sessions
mcp-abap-adt --auth-broker --auth-broker-path=~/prj/tmp/ --unsafe
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=truealso enablesdebug.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
npm test
Test logging switches
TEST_LOG_LEVEL=error|warn|info|debug— controls test logger verbosity (DEBUG_TESTS/DEBUG_ADT_TESTS/DEBUG_CONNECTORS forcedebug).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
npm run build
Developer Tools
# Generate tool documentation
npm run docs:tools
# See tools/README.md for more developer utilities
Contributors
Thank you to all contributors! See CONTRIBUTORS.md for the complete list.
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.
Mcp Abap Adt Reviews
Login Required
Please log in to share your review and rating for this MCP.
Similar MCP Servers like Mcp Abap Adt
Explore related MCPs that share similar capabilities and solve comparable challenges
Git
Officialby modelcontextprotocol
A Model Context Protocol server for Git repository interaction and automation.
Zed
OfficialClientby zed-industries
A high‑performance, multiplayer code editor designed for speed and collaboration.
Everything
Officialby modelcontextprotocol
Model Context Protocol Servers
Time
Officialby modelcontextprotocol
A Model Context Protocol server that provides time and timezone conversion capabilities.
Cline
OfficialClientby cline
An autonomous coding assistant that can create and edit files, execute terminal commands, and interact with a browser directly from your IDE, operating step‑by‑step with explicit user permission.
Context7 MCP
Officialby upstash
Provides up-to-date, version‑specific library documentation and code examples directly inside LLM prompts, eliminating outdated information and hallucinated APIs.
Daytona
by daytonaio
Provides a secure, elastic infrastructure that creates isolated sandboxes for running AI‑generated code with sub‑90 ms startup, unlimited persistence, and OCI/Docker compatibility.
Continue
OfficialClientby continuedev
Enables faster shipping of code by integrating continuous AI agents across IDEs, terminals, and CI pipelines, offering chat, edit, autocomplete, and customizable agent workflows.
GitHub MCP Server
by github
Connects AI tools directly to GitHub, enabling natural‑language interactions for repository browsing, issue and pull‑request management, CI/CD monitoring, code‑security analysis, and team collaboration.