GetBehaviorDefinition
Retrieve RAP Behavior Definition (BDEF) source code (requires ~NW 7.54 / S/4HANA)
LABSCO SUMMARY
ABAP source stops being something you have to be inside SAP GUI to read.
Every tool starts with Get or Search — nothing activates, transports or writes — so a wrong call costs a read against the system and nothing else. The split of the tool set follows how ABAP is actually stored: a function module is retrievable separately from its group, an include separately from the program that uses it, which is what lets a model assemble the full picture from parts. Only one tool returns business data rather than code, and it caps rows rather than streaming them.
What it is
A read-only client for SAP's ABAP Development Tools services, retrieving source and dictionary objects from one system and client over its ADT endpoints.
What you get
- Source for every container a change usually spans: programs, classes, interfaces, includes, function groups and individual function modules
- Dictionary objects on their own terms — structures, table definitions and type information
- Actual table contents with a row cap, not only the definition
- RAP artefacts where the system supports them: behaviour definitions and service definitions as source
- CDS views returned as DDL source
- Object discovery through a quick search with a result cap, plus package details and transaction details
Requirements
Node and four values for the system you are pointing at: SAP_URL, SAP_USERNAME, SAP_PASSWORD and SAP_CLIENT, with SAP_LANGUAGE optional. Two things on the SAP side decide whether it answers at all: the /sap/bc/adt service has to be active in SICF, and the user needs the authorizations for ADT. A system behind a self-signed certificate needs TLS_REJECT_UNAUTHORIZED set. Behaviour and service definitions need roughly NetWeaver 7.54 or S/4HANA; on older systems those objects do not exist to fetch. MIT.
Setup effort
One command plus credentials — npx -y mcp-abap-adt, then supply credentials
USE CASES
01
Understanding a program you have been asked to change
Read the program source, then the includes it pulls in and the classes it calls, so the whole unit of behaviour is in front of you rather than one file of it.
02
Tracing a function module back to its group
Find the object by name when you only half remember it, read the module itself, then read the group around it for the shared data and the other modules that touch it.
03
Working out what a table actually holds
Read the table definition, take a capped sample of the rows to see the shape of real data, and follow the structure behind the fields you do not recognise.
04
Reviewing a RAP service before extending it
Read the CDS view as DDL source, then the behaviour definition and the service definition, which together say what the service exposes and what it allows.
05
Finding where a transaction code lands
Read the transaction's details to see what it starts, then the package it belongs to, and search for the neighbouring objects that make up the same functional area.
16 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
GetCDSView
Retrieve CDS view (DDL source) source code
GetClass
Retrieve ABAP class source code
GetFunction
Retrieve ABAP Function Module source code
GetFunctionGroup
Retrieve ABAP Function Group source code
GetInclude
Retrieve ABAP Include Source Code
GetInterface
Retrieve ABAP interface source code
GetPackage
Retrieve ABAP package details
GetProgram
Retrieve ABAP program source code
GetServiceDefinition
Retrieve RAP Service Definition (SRVD) source code (requires ~NW 7.54 / S/4HANA)
GetStructure
Retrieve ABAP Structure
GetTable
Retrieve ABAP table structure
GetTableContents
Retrieve contents of an ABAP table
GetTransaction
Retrieve ABAP transaction details
GetTypeInfo
Retrieve ABAP type information
SearchObject
Search for ABAP objects using quick search
BEFORE YOU INSTALL
What to know first
Tools you get
16 tools when we connected. Every tool is read-only (Get* or SearchObject); none writes ABAP source back to the system.
Requires
- npx on PATH
- SAP_URL in your environment
- SAP_USERNAME in your environment
- SAP_PASSWORD in your environment
- SAP_CLIENT in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 16 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y mcp-abap-adtMCP Clients
FLUJO
Add Server → Spotlight tab → mcp-abap-adt (FLUJO fetches the npm package and opens the Local Server tab for URL / Username / Password)
Cline
CLINE · JSON
{
"mcpServers": {
"mcp-abap-adt": {
"command": "npx",
"args": [
"-y",
"mcp-abap-adt"
],
"env": {
"SAP_URL": "<YOUR_SAP_SYSTEM_URL>:8000",
"SAP_USERNAME": "<YOUR_SAP_USERNAME>",
"SAP_PASSWORD": "<YOUR_SAP_PASSWORD>",
"SAP_CLIENT": "100"
},
"disabled": false,
"autoApprove": []
}
}
}Claude Desktop, Claude Code
JSON
{
"mcpServers": {
"mcp-abap-adt": {
"command": "npx",
"args": [
"-y",
"mcp-abap-adt"
],
"env": {
"SAP_URL": "<YOUR_SAP_SYSTEM_URL>:8000",
"SAP_USERNAME": "<YOUR_SAP_USERNAME>",
"SAP_PASSWORD": "<YOUR_SAP_PASSWORD>",
"SAP_CLIENT": "100"
}
}
}
}HTTP clients — via FLUJO
HTTP CLIENTS — VIA FLUJO · JSON
{
"mcpServers": {
"mcp-abap-adt": {
"type": "http",
"url": "http://localhost:4200/mcp-proxy/mcp-abap-adt"
}
}
}
