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.
SETUP_REQUIRED (setup_required): No local SAP profiles exist. MCP initialization is available, but SAP authentication and useful reads are not verified. Run npx -y @coaspe/sap-abap-mcp onboard (Linux: setup) in a terminal, then reconnect. Never request a password in chat. Use advertised tools directly. For a known capability name, skip search: call sap.capability.describe (batch known names with names), then the matching invoke_read, invoke_write or invoke_destructive with its schemaHash and arguments. Otherwise use sap.capability.search; browse categories if needed. Reuse schemas until CAPABILITY_SCHEMA_CHANGED. If systemId is unknown, describe sap.system.list.
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 | Find capabilities; browse categories if keyword search misses. |
| sap.capability.describeB | Get exact input schemas and hashes: name or names (up to 10). |
| sap.capability.invoke_readC | Invoke a read capability with its described schemaHash and arguments. |
| sap.capability.invoke_writeC | Invoke a write capability with its described schemaHash and arguments. |
| sap.capability.invoke_destructiveC | Invoke a destructive capability with its described schemaHash and arguments. |
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 has a clearly distinct role: search discovers capabilities, describe retrieves schemas/hashes, and the three invoke tools are cleanly separated by effect class (read/write/destructive). An agent can select the right tool based on intent without overlapping functionality.
All tools follow the same `sap.capability.<action>` namespace with lowercase and snake_case suffixes. The invoke variants consistently append the effect type, creating a predictable and readable pattern.
Five tools neatly cover the generic capability gateway pattern: discovery, introspection, and execution split by effect class. Each tool earns its place with no redundant or missing meta-operations.
The set covers discovery (search), schema retrieval (describe), and execution across all effect classes (read/write/destructive), forming a complete lifecycle for invoking SAP capabilities without obvious dead ends.