MCP ABAP ADT
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAP_URL | Yes | Your SAP system URL (e.g., https://your-sap-system.com:8000) | |
| SAP_CLIENT | Yes | Your SAP client (e.g., 100) | |
| SAP_PASSWORD | Yes | Your SAP password. If your password contains a '#' character, make sure to enclose it in quotes | |
| SAP_USERNAME | Yes | Your SAP username |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| GetProgramB | Retrieve ABAP program source code |
| GetClassB | Retrieve ABAP class source code |
| GetFunctionGroupC | Retrieve ABAP Function Group source code |
| GetFunctionB | Retrieve ABAP Function Module source code |
| GetStructureC | Retrieve ABAP Structure |
| GetTableB | Retrieve ABAP table structure |
| GetTableContentsC | Retrieve contents of an ABAP table |
| GetPackageB | Retrieve ABAP package details |
| GetTypeInfoC | Retrieve ABAP type information |
| GetIncludeB | Retrieve ABAP Include Source Code |
| SearchObjectC | Search for ABAP objects using quick search |
| GetTransactionC | Retrieve ABAP transaction details |
| GetInterfaceC | Retrieve ABAP interface source code |
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 13 tools
Every tool has a clearly distinct purpose targeting specific ABAP object types or operations. The 'Get' tools each retrieve different ABAP artifacts (class, function, interface, etc.), while SearchObject provides a distinct search capability. No ambiguity exists between tools.
All tools follow a consistent verb_noun pattern with 'Get' prefix for retrieval operations and 'SearchObject' as the only exception that still maintains clear verb_noun structure. The naming is perfectly predictable and readable throughout the set.
13 tools is well-scoped for an ABAP development tool server, providing comprehensive coverage of different ABAP object types. Each tool earns its place by addressing a specific retrieval need in the ABAP domain without being overwhelming.
The server provides excellent retrieval coverage for ABAP development objects, but lacks modification capabilities (create, update, delete). For a read-only development tool interface, this is reasonable, though agents cannot perform full lifecycle operations.