SAP Cloudification Repository

@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 — Hosted instance (recommended)

ROSA is publicly hosted — no install, no server to run. Connect your AI agent directly:

MCP (Claude Desktop, Claude Code, Cursor, Cline…)

Claude Code (.mcp.json) / Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "rosa": {
      "type": "url",
      "url": "https://sap-released-objects-server-production.up.railway.app/mcp"
    }
  }
}

Cursor (~/.cursor/mcp.json or .cursor/mcp.json):

{
  "mcpServers": {
    "rosa": {
      "type": "url",
      "url": "https://sap-released-objects-server-production.up.railway.app/mcp"
    }
  }
}

REST API

All endpoints are GET, return JSON, and support CORS:

curl "https://sap-released-objects-server-production.up.railway.app/api/search?query=purchase+order"
curl "https://sap-released-objects-server-production.up.railway.app/api/object?object_type=TABL&object_name=MARA"
curl "https://sap-released-objects-server-production.up.railway.app/api/compliance?object_names=MARA,BSEG,I_PRODUCT"

For LLM-skill usage, two ready-made skills expose the full API reference:

• skills/sap-released-objects/SKILL.md — points at the hosted public instance; use as-is.
• skills/rosa-global/SKILL.md — for your own self-hosted deployment: copy it and replace the {{ROSA_BASE_URL}} placeholder with your instance URL.

---

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