SAP Released Objects Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port number for the HTTP server. Default is 3001. | 3001 |
| API_KEYS | No | API keys in key:profile format, comma-separated for simple key-based access. | |
| NODE_ENV | No | Node environment, set to 'production' for deployment. | production |
| TRANSPORT | No | Transport mode, set to 'http' for HTTP transport. | http |
| OAUTH_ISSUER | No | Authorization Server issuer URL for OIDC authentication. | |
| API_RATE_LIMIT | No | Rate limit for /api endpoints in requests per minute. Default 600. | 600 |
| MCP_RATE_LIMIT | No | Rate limit for /mcp endpoint in requests per minute. Default 600. | 600 |
| OAUTH_AUDIENCE | No | Resource identifier for OIDC token validation. | |
| DCR_SIGNING_SECRET | No | Stable secret for OAuth dynamic client registration and state codec (used with XSUAA). | |
| CORS_ALLOWED_ORIGINS | No | Comma-separated list of allowed CORS origins. | |
| OAUTH_DCR_TTL_SECONDS | No | DCR client lifetime in seconds. 0 means never expire. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sap_search_objectsA | Search for SAP objects (classes, interfaces, CDS views, tables, data elements, function groups, RAP artifacts, etc.) in the SAP Cloudification Repository. Filter by Clean Core Level (A/B/C/D), object type, application component, and state. Use this tool to find released APIs for ABAP Cloud development, check if a specific object is available for your target system, or discover alternatives when an object is not released. SEARCH TIPS:
System types:
Clean Core Levels (cumulative filter):
|
| sap_get_object_detailsA | Get detailed information about a specific SAP object by its exact type and name. Returns Clean Core Level, state, successor info, application component, and more. Use this to check if a specific object (table, class, CDS view...) is released for ABAP Cloud and what its Clean Core Level is. |
| sap_find_successorA | Find the released successor(s) of a deprecated or non-released SAP object. Essential for ABAP Cloud migration: when your code uses a non-released object (e.g., table MARA), this tool finds the replacement (e.g., CDS view I_PRODUCT). Also useful for checking if a deprecated API has a modern replacement. |
| sap_list_object_typesA | List all available TADIR object types in the Cloudification Repository with their counts per Clean Core Level. Useful to understand what kind of objects are available (classes, CDS views, tables, BDEFs, etc.) and their distribution across Levels A-D. |
| sap_get_statisticsA | Get overall statistics about the SAP Cloudification Repository: total object counts by Clean Core Level, by object type, by state, and top application components. Useful for understanding the scope of available APIs and planning ABAP Cloud migration efforts. |
| sap_list_versionsA | List all available S/4HANA PCE versions for Private Cloud and On-Premise systems. Versions are discovered dynamically from the SAP Cloudification Repository on GitHub. Use this to find which versions can be passed to other tools (sap_search_objects, sap_get_object_details, etc.). |
| sap_check_clean_core_complianceA | Check the Clean Core compliance of a list of SAP objects. Provide a comma-separated list of object names and get their Clean Core Level classification, compliance status, and successor recommendations. Essential for assessing existing custom code during ABAP Cloud migration. |
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 7 tools
Each tool has a clearly distinct purpose: listing versions, searching objects, getting details, finding successors, listing types, statistics, and compliance checking. No overlap.
All tool names follow a consistent 'sap_verb_noun' pattern (e.g., sap_list_versions, sap_search_objects). No deviations.
7 tools is an appropriate number for this domain, covering key operations without being excessive or insufficient.
The tool surface covers the full lifecycle of exploring and assessing SAP released objects: version discovery, search, detail, successor, types, statistics, and compliance. No obvious gaps.