sap-abap-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sap.capability.searchB | Search or page through the complete SAP tool catalog. Use category browsing when keyword search misses. |
| sap.capability.describeA | Return the exact input schema and schema hash for one capability before invoking it. |
| sap.capability.invoke_readB | Invoke a read capability after sap.capability.describe. The original tool validation and result are preserved. |
| sap.capability.invoke_writeC | Invoke a write capability after sap.capability.describe. The original tool validation and result are preserved. |
| sap.capability.invoke_destructiveB | Invoke a destructive capability after sap.capability.describe. The original tool validation and result are preserved. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| sap-explain-object | Explain current SAP source and its callers with source evidence, without changing it. |
| sap-change-object | Guide a scoped source change through impact review, diagnostics, activation, ABAP Unit and ATC. |
| sap-review-transport | Review one transport with bounded quality evidence; assessment does not release it. |
| sap-plan-rap | Discover backend RAP capabilities and validate a generation preview without generating or publishing. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| sap-docs-data-query | Read-only SAP ADT data-preview SQL rules and examples. |
TDQS
Scored across 5 tools
Each tool occupies a distinct phase: discovery (search), introspection (describe), and execution split by risk class (read/write/destructive). The three invoke tools share a description template and differ only by side-effect profile, so an agent could occasionally confuse write vs destructive if capability metadata is unclear.
All tool names use the same sap.capability.<action> dot-delimited convention, with snake_case for multiword actions. The pattern is predictable and consistent throughout.
Five tools are well-scoped for a capability broker: one search, one describe, and three execution variants by risk category. No tool feels redundant or missing.
The surface covers discovery, schema introspection, and invocation for read, write, and destructive operations, which is full lifecycle for a capability gateway. No obvious capability-broker operation is absent.