MCP serverMCP servertypeExposes tools to a coding agent over MCP.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

ROSA

Answers whether an SAP object is released for ABAP Cloud, and what to use instead when it is not — served from SAP's own Cloudification Repository over MCP and over plain REST.

The clean-core question an agent gets wrong silently: MARA looks like a table an ABAP program may read, and in ABAP Cloud it is not one. ROSA plugs into SAP's Cloudification Repository — the published source of truth for released objects and their successors — and exposes it two ways off the same logic: MCP on POST /mcp for agents that speak it, and GET /api/* for skills, scripts and pipelines that only speak HTTP. Ask whether MARA is available and the answer comes back with I_PRODUCT as the replacement. Its public hosted instance has been retired, by the README's own account, so it runs where you put it: through npx, as a container image, or on BTP Cloud Foundry.

Facts

Last pushLicenceMIT

Where it sits

Lives in
Provides
ABAP Cloud readinessABAPABAP Cloud readinesscapabilityWhether code can run in ABAP Cloud — released APIs only, no direct table access, no obsolete statements — and what to do with the code that cannot.
Serves
Requires
Cloudification RepositoryCloudification Repositoryartifactthe catalogue of released SAP objects and their successors that ROSA searches and classifies, from the Cloudification Repository
Optional
DockerDockeroutside the atlasrunning ROSA as a self-hosted server using the published GHCR imageSAP Authorization and Trust Management serviceSAP Authorization and Trust Management serviceartifactauthenticating MCP/API clients against SAP Authorization and Trust Management service on SAP BTP@arc-mcp/xsuaa-auth@arc-mcp/xsuaa-authartifactimplementing the MCP OAuth 2.1 proxy and JWT verification used by @arc-mcp/xsuaa-auth in XSUAA modeSAP BTP, Cloud Foundry RuntimeSAP BTP, Cloud Foundry Runtimeartifactrunning ROSA as an application in SAP BTP's Cloud Foundry space

Who is behind it

Clément RingotClément RingotPersonMaintains this
In the atlas: maintains 2, contributes to 3
@ClementRingot
maintainer

Before choosing this

Conditions

PracticalFunctional boundary

It answers about the object catalogue, not about your code: nothing here reads your system, so it will tell you a table is not released and not that you used it. That check is ATC's, and this is what makes ATC's answer actionable.

What it declares

Every artifact

Type
MCP server
Origin
Independently maintained
Runtime
Node.js

As an MCP server

Runs as
central serverlocal process
Transport
stdioHTTP
Authentication
OAuth / OIDCAPI key
Guardrails
1 quoted from README show all
  • no SAP system connection required.

Connections6

ROSA connectionsROSAPROVIDES→ provides1provides stated Serves the Cloudification Repository's released-object data as tools and as a REST API, so the question "is this available in ABAP Cloud, and what replaces it" is answerable by an agent mid-task rather than looked up afterwards. ROSA — README: https://github.com/ClementRingot/ROSAABAP Cloud readinessNEEDS→ needs1needs stated the catalogue of released SAP objects and their successors that ROSA searches and classifies, from the [Cloudification Repository](artifact:sap-abap-atc-cr-cv-s4hc) rosa README: https://github.com/clementringot/rosaCloudification Repository→ optionally needs4optionally needs stated If: XSUAA auth mode is active implementing the MCP OAuth 2.1 proxy and JWT verification used by [@arc-mcp/xsuaa-auth](artifact:arc-mcp-xsuaa-auth) in XSUAA mode rosa: docs/ARCHITECTURE.md: https://raw.githubusercontent.com/ClementRingot/ROSA/main/docs/ARCHITECTURE.md@arc-mcp/xsuaa-authifoptionally needs stated If: deployed via the pre-built Docker image running ROSA as a self-hosted server using the published GHCR image rosa: docs/DEPLOYMENT.md: https://raw.githubusercontent.com/ClementRingot/ROSA/main/docs/DEPLOYMENT.mdDockerifoptionally needs stated If: HTTP transport running on SAP BTP Cloud Foundry with an xsuaa service binding (XSUAA auth mode) authenticating MCP/API clients against [SAP Authorization and Trust Management service](artifact:btp-authorization-and-trust-management) on SAP BTP rosa: docs/ARCHITECTURE.md: https://raw.githubusercontent.com/ClementRingot/ROSA/main/docs/ARCHITECTURE.mdSAP Authorization and Trust Managementserviceifoptionally needs stated If: deployed via the MTA or npm wrapper path on SAP BTP Cloud Foundry running ROSA as an application in SAP BTP's Cloud Foundry space rosa: docs/cloud-foundry-classic.md: https://raw.githubusercontent.com/ClementRingot/ROSA/main/docs/cloud-foundry-classic.mdSAP BTP, Cloud Foundry Runtimeif

Install

npm add ROSA

Derived from the package name. No recipe recorded; the README has the configuration.

Where ROSA runsYour SAP BTP subaccountROSA — README, checked 2026-09-11: “ROSA runs over **stdio** (default; local MCP clients) or **HTTP** (`--http` /”stdio or HTTPdocumentedrequiresdocumentedmay needif deployed via the pre-builtDocker imagedocumentedmay needif HTTP transport running onSAP BTP Cloud Foundry with anxsuaa service binding (XSUAA aut…documentedmay needif XSUAA auth mode is activedocumentedmay needif deployed via the MTA or npmwrapper path on SAP BTP CloudFoundryYour MCP client, actorYour MCP clientDocker, SoftwareDockerSoftwareROSA, moduleROSACloudification Repository, moduleCloudificationRepository@arc-mcp/xsuaa-auth, module@arc-mcp/xsuaa-authSAP Authorization and Trust Management service, service instanceSAP Authorizationand TrustManagement serviceSAP BTP, Cloud Foundry Runtime, service instanceSAP BTP, CloudFoundry Runtime
SAPnot SAP's, or the project's ownstated in the documentdocumented onlyunder a condition

README

quoted from ClementRingot/ROSA under MIT, read
ClementRingot/ROSA/README.mdOn GitHub

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 modeProtocolUse case
MCP ServerModel Context Protocol on POST /mcpAI agents with native MCP support (Claude Desktop, Claude Code, Cline, Cursor…)
REST APIGET endpoints on /api/* returning JSONLLM 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:


Self-hosted / alternative deployments

I want to…UseOne-liner
Run locally via npx (stdio)npmnpx -y @rosa-mcp/server
Run without Node.js installedNative executabledownload from Releases
Run as a server / self-hostDockerdocker run -p 3001:3001 ghcr.io/clementringot/rosa
Deploy on a generic Node hostNode PaaSRailway / Render / Fly.io — set TRANSPORT=http
Deploy on SAP BTP Cloud FoundryMTA or npm wrappersee DEPLOYMENT
Deploy on classic Cloud Foundrycf pushsee 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
LevelMeaningUpgrade safety
AReleased APIs (ABAP Cloud)✅ Upgrade-safe
BClassic APIs⚠️ Upgrade-stable
CInternal / unclassified🟡 Manageable risk
DnoAPI (not recommended)🔴 High risk

MCP tools & REST endpoints

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

MCP toolREST endpointPurpose
sap_search_objectsGET /api/searchSearch objects, ranked by relevance, with filters
sap_get_object_detailsGET /api/objectFull details + Clean Core assessment for one object
sap_find_successorGET /api/successorSuccessor(s) of a deprecated / non-released object
sap_check_clean_core_complianceGET /api/complianceCompliance rate for a list of objects
sap_list_versionsGET /api/versionsAvailable S/4HANA PCE versions
sap_list_object_typesGET /api/typesTADIR object types with per-level counts
sap_get_statisticsGET /api/statisticsRepository 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:

ModeTrigger
Publicno auth env vars
OIDC / OAuth 2.1OAUTH_ISSUER + OAUTH_AUDIENCE
XSUAAVCAP_SERVICES xsuaa binding (SAP BTP)
API keysAPI_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

DocFor
ARCHITECTURE.mdTransports, auth modes, system diagram, MCP tools
DEPLOYMENT.mdEvery deployment option + config reference + troubleshooting
cloud-foundry-classic.mdClassic (non-BTP) Cloud Foundry
RELEASE.mdRelease train & pipeline (maintainers)
CONTRIBUTING.mdDev setup, tests, commit convention
CHANGELOG.mdNotable 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

MIT, read

History

Latest

v1.14.1

Fixes 1

Notes
Patch Changes
  • e08fa24: Report the real version from the native executables and the esbuild bundle. The version is now injected at build time (esbuild define) instead of falling back to a stale hard-coded literal, so node bundle/index.cjs and the published binaries no longer report an outdated version.

All notable changes to this project are documented here.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning. From the next release onward, entries are maintained automatically by release-please.

  1. v1.14.0

    Features 1

    Notes
    Features
    • publish as @rosa-mcp/server on npmjs (b8c5bf4)
  2. v1.13.2

    Fixes 1

    Notes
    Bug Fixes
    • ci: use explicit --output in pkg:all to produce rosa-* filenames (45f9261)
  3. v1.13.1

    Fixes 3

    Notes
    Bug Fixes
    • rename npm package to @rosa-mcp/server (54a2bb5)
    • rename npm package to @rosa-mcp/server (a85fd26)
    • resolve merge conflict - keep @rosa-mcp/server name with v1.13.0 (0d91c7f)
  4. v1.13.0

    Features 4

    Notes
    Features
    • add Docker, BTP/MTA deployment, OAuth 2.1 auth, and documentation (#4) (da9a577)
    • add npm-based Cloud Foundry / BTP deployment wrapper (b5fae0d)
    • rebrand to ROSA and ship as scoped npm package @clementringot/rosa (51d4beb)
    • ROSA rebrand, npm package, unified release pipeline & docs overhaul (2ff6ca4)
  5. v1.12.6

    Notes

    Baseline release prior to the changes above (native executables only). See the GitHub Releases for the full history up to 1.12.6.

ABAP Cloud readiness
  1. abap-cloud-guiReport-style programming model for abap2UI5 on ABAP Cloudfrom ABAP
  2. codepagePolyfill for CL_ABAP_CODEPAGE under Clean Corefrom ABAP
  3. Modernization Agents for SAP on AWSAWS agents for ABAP, PI/PO and BW modernisation workfrom ABAP
  4. Cloudification RepositorySAP's list of released APIs for SAP Cloud ERP with successorsfrom ABAP
  5. code pal for ABAP — Cloud EditionClean ABAP check set for ABAP Cloudfrom ABAP
  6. Clean-Core.ioHosted workspace redrawing custom ABAP as BPMN and grading itfrom ABAP
  7. Clean Core MeasurementReports Clean Core ATC results per system as Level A to D KPIsfrom ABAP
  8. ABAP Select ConverterConverts classic Open SQL SELECTs to released CDS entitiesfrom ABAP
  9. abap-system-fieldsInjectable wrapper for SY fields and date functions in ABAP Cloudfrom ABAP
  10. Cloudification Repository ViewerBrowser form over SAP's Cloudification Repository for ABAP Cloudfrom ABAP

Details

Sources4
sap-ai-mcp-serversdiscovered herechecked
npm registry, ROSAversion, releases, installschecked
github.com/ClementRingot/ROSAtree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesnode
discovered viasap-ai-mcp-servers
first seen in the atlas
ecosystem and domainabap, ai-and-agents
Flavors2
ABAP Cloud
“S/4HANA Cloud Public, BTP ABAP Environment, Private Cloud,” — ClementRingot/ROSA — READMEchecked
Standard ABAP
“On-Premise; PCE versions discovered dynamically.” — ClementRingot/ROSA — READMEchecked
History in the atlas3
  1. corrected against the README
  2. Triaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.
  3. First seen.
For your agent
Ref
artifact:clementringot-rosa
JSON
/artifacts/clementringot-rosa.json
MCP
Connecting an agent