Skip to main content
Glama
SAP Released Objects Server

SAP Released Objects Server

ROSA — Released Objects Search Assistant

@rosa-mcp/server ghcr.io rosa CI Release node license MIT MCP server

ROSA gives AI agents real-time knowledge of which SAP objects are released for ABAP Cloud / Clean Core — and what to use instead when they're not.

It plugs into the SAP Cloudification Repository (the official source of truth) and exposes it two ways, sharing the same business logic — no feature gap between them:

Access mode

Protocol

Use case

MCP Server

Model Context Protocol on POST /mcp

AI agents with native MCP support (Claude Desktop, Claude Code, Cline, Cursor…)

REST API

GET endpoints on /api/* returning JSON

LLM skills, scripts, CI pipelines — anything that speaks HTTP

Ask "Is table MARA available in ABAP Cloud?" and the agent instantly knows: no — use I_PRODUCT instead.

Quick start

The previously hosted public instance (on Railway) has been retired — it was too costly to keep running. There is no default public URL anymore. Everything else still works: run ROSA via npx, a native executable, Docker, any Node host, or SAP BTP — see the deployment options below.

The quickest path is npx — no install, runs in stdio mode (what MCP clients expect). Add this to your client config (Claude Code .mcp.json, Claude Desktop claude_desktop_config.json, or Cursor ~/.cursor/mcp.json):

{
  "mcpServers": {
    "rosa": {
      "command": "npx",
      "args": ["-y", "@rosa-mcp/server"]
    }
  }
}

Already running ROSA somewhere (self-hosted / your own server)? Point your client at its URL instead:

{
  "mcpServers": {
    "rosa": {
      "type": "url",
      "url": "https://<your-instance>/mcp"
    }
  }
}

REST API

All endpoints are GET, return JSON, and support CORS (replace <your-instance> with your own host):

curl "https://<your-instance>/api/search?query=purchase+order"
curl "https://<your-instance>/api/object?object_type=TABL&object_name=MARA"
curl "https://<your-instance>/api/compliance?object_names=MARA,BSEG,I_PRODUCT"

For LLM-skill usage, the full API reference is available as a skill you point at your instance:


Related MCP server: abap-adt-mcp

Self-hosted / alternative deployments

I want to…

Use

One-liner

Run locally via npx (stdio)

npm

npx -y @rosa-mcp/server

Run without Node.js installed

Native executable

download from Releases

Run as a server / self-host

Docker

docker run -p 3001:3001 ghcr.io/clementringot/rosa

Deploy on a generic Node host

Node PaaS

Railway / Render / Fly.io — set TRANSPORT=http

Deploy on SAP BTP Cloud Foundry

MTA or npm wrapper

see DEPLOYMENT

Deploy on classic Cloud Foundry

cf push

see cloud-foundry-classic

Full details for every option: docs/DEPLOYMENT.md.

Local MCP (stdio mode)

{
  "mcpServers": {
    "rosa": {
      "command": "npx",
      "args": ["-y", "@rosa-mcp/server"]
    }
  }
}

Features

  • Search SAP objects — classes, CDS views, tables, data elements, BDEFs…

  • Filter by Clean Core Level (A / B / C / D) — the model replacing the 3-tier system since August 2025.

  • Find successors for deprecated or non-released objects.

  • Clean Core compliance check for a list of objects (with compliance rate).

  • Statistics — counts by level, type, and application component.

  • Smart search — multi-token scoring ("purchase order" → I_PURCHASEORDER).

  • Multi-system — S/4HANA Cloud Public, BTP ABAP Environment, Private Cloud, On-Premise; PCE versions discovered dynamically.

Data is fetched from SAP's public GitHub repository at runtime and cached in memory for 24h — no SAP system connection required.

Clean Core Level Concept

Level

Meaning

Upgrade safety

A

Released APIs (ABAP Cloud)

✅ Upgrade-safe

B

Classic APIs

⚠️ Upgrade-stable

C

Internal / unclassified

🟡 Manageable risk

D

noAPI (not recommended)

🔴 High risk

MCP tools & REST endpoints

Each MCP tool on POST /mcp has an identical REST counterpart under /api:

MCP tool

REST endpoint

Purpose

sap_search_objects

GET /api/search

Search objects, ranked by relevance, with filters

sap_get_object_details

GET /api/object

Full details + Clean Core assessment for one object

sap_find_successor

GET /api/successor

Successor(s) of a deprecated / non-released object

sap_check_clean_core_compliance

GET /api/compliance

Compliance rate for a list of objects

sap_list_versions

GET /api/versions

Available S/4HANA PCE versions

sap_list_object_types

GET /api/types

TADIR object types with per-level counts

sap_get_statistics

GET /api/statistics

Repository statistics

Parameters and response shapes are documented in skills/sap-released-objects/SKILL.md.

Server modes & authentication

ROSA runs over stdio (default; local MCP clients) or HTTP (--http / TRANSPORT=http; remote/self-hosted). On HTTP it auto-detects four authentication modes from the environment — public, OIDC / OAuth 2.1, XSUAA (SAP BTP), and API keys — with no rebuild:

Mode

Trigger

Public

no auth env vars

OIDC / OAuth 2.1

OAUTH_ISSUER + OAUTH_AUDIENCE

XSUAA

VCAP_SERVICES xsuaa binding (SAP BTP)

API keys

API_KEYS (alongside any mode)

How transports, auth auto-detection, the auth × deployment matrix, and the system diagram work: docs/ARCHITECTURE.md.

Usage examples

You:   "Is table MARA available in ABAP Cloud?"
Agent: → sap_get_object_details(TABL, MARA) → "deprecated; successor I_PRODUCT"

You:   "My code uses BSEG, MARA, CL_GUI_ALV_GRID. Is it Clean Core?"
Agent: → sap_check_clean_core_compliance(...) → "Compliance rate: 0%"

You:   "What's available for sending emails on BTP?"
Agent: → sap_search_objects(query="send email", system_type="btp")

Documentation

Doc

For

ARCHITECTURE.md

Transports, auth modes, system diagram, MCP tools

DEPLOYMENT.md

Every deployment option + config reference + troubleshooting

cloud-foundry-classic.md

Classic (non-BTP) Cloud Foundry

RELEASE.md

Release train & pipeline (maintainers)

CONTRIBUTING.md

Dev setup, tests, commit convention

CHANGELOG.md

Notable changes

Contributing & releases

PRs welcome — see CONTRIBUTING.md. This repo uses Conventional Commits; releases are cut by an automated release train that publishes the npm package, the multi-arch Docker image, and native executables from a single tag.

License

MIT

Available Tools

7 tools
sap_check_clean_core_complianceCheck Clean Core ComplianceA
Read-onlyIdempotent

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.

Inputs: object_names (required), version, system_type, target_level.

sap_find_successorFind SAP Object SuccessorA
Read-onlyIdempotent

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.

Inputs: object_name (required), version, object_type, system_type.

sap_get_object_detailsGet SAP Object DetailsA
Read-onlyIdempotent

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.

Inputs: object_name (required), object_type (required), version, system_type, +1 more.

sap_get_statisticsGet Repository StatisticsA
Read-onlyIdempotent

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.

Inputs: version, system_type, clean_core_level.

sap_list_object_typesList SAP Object TypesA
Read-onlyIdempotent

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.

Inputs: version, system_type, clean_core_level.

sap_list_versionsList Available S/4HANA VersionsA
Read-onlyIdempotent

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.).

Inputs: no named parameters.

sap_search_objectsSearch SAP ObjectsA
Read-onlyIdempotent

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:

  • Use separate words for business concepts: 'purchase order' not 'PURCHASEORDER'

  • SAP abbreviations are automatically resolved: 'billing document' also finds BILLGDOC*, BILDOC* objects

  • Compound abbreviations work too: 'purchase order' finds PO* objects, 'bill of material' finds BOM*

  • Separate words trigger fuzzy matching on SAP abbreviations (e.g., 'physical inventory' finds both PHYSICALINVENTORY* and PHYSINVTRY* objects)

  • Use exact SAP names only when you know the precise object name (e.g., 'I_PRODUCT', 'MARA')

  • Combine with app_component filter for targeted results (e.g., query='inventory', app_component='MM-IM')

  • Prefer singular forms: 'handling unit' not 'handling units' (plural 's' can reduce match accuracy)

  • Keep queries to 2-3 words maximum; use filters instead of adding more words

System types:

  • public_cloud (S/4HANA Cloud Public Edition): Only Level A Released APIs

  • btp (BTP ABAP Environment / Steampunk): Only Level A Released APIs (separate, smaller dataset)

  • private_cloud / on_premise: Levels A-D available, version-specific

Clean Core Levels (cumulative filter):

  • A: Released APIs only (ABAP Cloud, upgrade-safe)

  • B: + Classic APIs (upgrade-stable)

  • C: + Internal/unclassified objects

  • D: + noAPI objects (not Clean Core)

Inputs: query (required), limit, state, offset, +5 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing versions, searching objects, getting details, finding successors, listing types, statistics, and compliance checking. No overlap.

    Naming Consistency5/5

    All tool names follow a consistent 'sap_verb_noun' pattern (e.g., sap_list_versions, sap_search_objects). No deviations.

    Tool Count5/5

    7 tools is an appropriate number for this domain, covering key operations without being excessive or insufficient.

    Completeness5/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to read, write, activate, and transport ABAP code in SAP systems via ABAP ADT REST API, without needing SAP GUI.
      24
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform ABAP Development Tools operations on SAP ERP (ECC and S/4HANA) systems, including source code editing, object activation, syntax checks, and ABAP unit tests.
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to work with SAP ABAP systems through the ADT REST API, supporting repository search, source code read/write, activation, syntax checks, and transport request management.
      1
      Apache 2.0