SAP Clean Core MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Set debug for verbose logs | info |
| DEFAULT_TARGET | No | Default deployment target (PCE/PUBLIC/BTP) | PCE |
| FETCH_TIMEOUT_MS | No | GitHub dataset fetch timeout | 60000 |
| DISABLE_EMBEDDINGS | No | Set true to skip semantic search index | false |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cc_lookup_objectA | Look up a single ABAP object by name and return its SAP Clean Core classification. Returns: Clean Core level (A/B/C/D), ATC priority, state, software component, application component, object type, successor objects, and data source. If the object exists as both a CDS view (DDLS) and a RAP business object (BDEF), both entries are returned. Objects not found are classified as Level C (Internal — inferred from SAP whitepaper default rule, Section 3.3.4.3.3). |
| cc_classify_objectsA | Bulk compliance check — classify up to 500 ABAP objects at once. Returns a table: object name, Clean Core level (A/B/C/D), ATC priority, state, recommended action. Uses the most restrictive state when an object has multiple entries (safety-first). Objects not found in the dataset are classified as Level C (Internal — inferred from SAP whitepaper Section 3.3.4.3.3). Use this to audit a transport's object list or a codebase's dependency inventory. |
| cc_find_successorsA | Find successor APIs for deprecated or classic API ABAP objects. Returns: successorClassification (oneObject / multipleObjects / none), list of successor object names and types, their Clean Core levels, and migration advice. Tells you exactly which Released API to migrate to when retiring a deprecated dependency. |
| cc_semantic_searchA | Natural language search across ~200,000+ ABAP objects using in-process AI embeddings (Xenova/all-MiniLM-L6-v2). Use this when you know WHAT the API should do but not its exact name. Examples: 'APIs for posting goods movements', 'purchase order creation functions', 'credit management interfaces'. The vector index builds in the background after the first dataset load (~60 seconds). Returns top-k results ranked by semantic similarity score. |
| cc_search_objectsA | Search ABAP objects by name pattern with wildcard support. Use for prefix search ('BAPI_MATERIAL') or wildcards ('CL_SALV*', 'MM_%'). For natural language search ('APIs for posting goods movements') use cc_semantic_search instead. |
| cc_search_by_componentA | Find all ABAP objects belonging to a SAP software component or application component. Use this to audit an entire functional area (e.g. all MM-IM objects) for Clean Core compliance, or to discover which Released APIs exist in a given component. |
| cc_partner_objectsA | Search ABAP objects from SAP partner namespaces. Partner objects are cross-target (not filtered by deployment environment). Supported partners: CDE, CONLUTIO, ICO, INFHCM, INVICL, IXOS, MIC, NAMESPACE, OBZERVR, OTX, OTXAF, PAT, PROS, QTYW, SIAV, TFTO, TOP, XPR. Use this to check if a partner product's APIs follow the Clean Core approach. |
| cc_get_statisticsA | Dataset summary and statistics for the SAP Cloudification Repository. Returns: total object count, breakdown by Clean Core level (A/B/C/D), breakdown by state, top object types, top software components, and semantic index status. |
| cc_list_object_typesA | List all ABAP object types in the SAP Cloudification Repository dataset with their counts. Use this to understand what types of objects are documented and discoverable via cc_lookup_object or cc_search_objects. |
| cc_explain_levelA | Explains what a SAP Clean Core level means: what states map to it, what ATC check priority it triggers, what action is required, and governance guidance. Use this to communicate Clean Core compliance requirements to developers and architects. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nidhideep/sap-clean-core-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server