mcp-abap-adt
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | TCP port for HTTP server (required in remote mode) | 6969 |
| SAP_URL | Yes | SAP ABAP server URL with ADT services (required) | |
| NODE_ENV | No | Environment mode (production, development) | production |
| SAP_CLIENT | No | SAP client number (fallback when not provided via function parameters) | |
| SAP_LANGUAGE | No | Default SAP language (fallback when not provided via function parameters) | EN |
| SAP_PASSWORD | Yes | SAP password (fallback when not provided via function parameters) | |
| SAP_USERNAME | Yes | SAP username (fallback when not provided via function parameters) | |
| TLS_REJECT_UNAUTHORIZED | No | TLS certificate validation (0=disabled, 1=enabled) | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| API_ReleasesC | Retrieve API Release information for an ADT object |
| DataPreviewB | Preview ABAP data for a DDIC entity |
| GetDDIC_CDSC | Retrieve CDS view definition |
| GetDDIC_DataElementsC | Retrieve data element definition |
| GetDDIC_DomainsC | Retrieve domain definition |
| GetDDIC_StructureC | Retrieve structure definition |
| GetDDIC_TableB | Retrieve table definition |
| GetDDIC_TypeInfoC | Retrieve DDIC type information |
| Get_ABAPTracesC | Retrieve ABAP Trace (performance) information |
| Get_ABAPTracesDetailsC | Retrieve detailed ABAP Trace information |
| Get_ClassB | Retrieve ABAP class source code |
| Get_FunctionB | Retrieve ABAP function module source code |
| Get_FunctionGroupB | Retrieve ABAP function group source code |
| Get_IncludeB | Retrieve ABAP include source code |
| Get_InterfaceB | Retrieve ABAP interface source code |
| Get_MessageClassC | Retrieve ABAP message class information |
| Get_PackageB | Retrieve ABAP package details |
| Get_ProgramB | Retrieve ABAP program source code |
| Get_TransactionB | Retrieve ABAP transaction details |
| GetRuntimeDumpDetailsC | Retrieve detailed ABAP runtime dump information |
| GetRuntimeDumpsC | Retrieve ABAP runtime dump list |
| SearchObjectC | Search for ABAP objects |
| Get_ATC_ResultListA | Retrieve ATC (ABAP Test Cockpit) result list. Use scope=central for central hub results or scope=local for local system results. Filter by period (today/yesterday/older), createdBy, and contactPerson. |
| Get_ATC_ResultDetailB | Retrieve detailed ATC (ABAP Test Cockpit) findings for a specific result entry by its ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
Each tool targets a distinct ABAP object or operation (e.g., class, function, DDIC entity, runtime dump, ATC result). There is no ambiguity between tools; their names and descriptions clearly differentiate them.
Most tools follow a `Get_<Object>` pattern (e.g., Get_Class, Get_Function), but several deviate: GetRuntimeDumpDetails, SearchObject, API_Releases, DataPreview, and GetDDIC_* use different prefixes or casing. This inconsistency, while not chaotic, makes the naming less predictable.
24 tools cover a wide range of ABAP development tasks (source retrieval, runtime analysis, DDIC, ATC, data preview). The count is slightly high but remains scoped to the server's purpose; no tool feels superfluous.
The tool set covers retrieval and inspection of many ABAP artifacts and diagnostic data. However, it lacks any creation, update, or deletion operations, which are notable gaps for a fully capable server. It serves well as a read-only interface but misses typical lifecycle operations.