SAP Cloud ALM

Registre officiel Autres

SAP Cloud ALM: requirements, features, tests, defects, landscape; writes wait for your approval.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package cloud-alm-mcp-server
Claude Code
claude mcp add sap-cloud-alm -e 'CALM_SERVICE_KEY=<your calm_service_key>' -- npx -y cloud-alm-mcp-server@0.1.0
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "sap-cloud-alm": {
            "command": "npx",
            "args": [
                "-y",
                "cloud-alm-mcp-server@0.1.0"
            ],
            "env": {
                "CALM_SERVICE_KEY": "<your calm_service_key>"
            }
        }
    }
}

Variables d'environnement

  • CALM_SERVICE_KEY secret Path to the SAP Cloud ALM API service key (the JSON file downloaded from SAP BTP). Leave empty when `npx -y cloud-alm-mcp-server setup` saved the key.

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. SAP Cloud ALM for your AI assistant
  2. How it works
  3. 1. Get a service key
  4. 2. Install
  5. 3. Ask
  6. Skills: whole workflows
  7. Approving changes
  8. Update, rotate, uninstall
  9. Troubleshooting
  10. Security
  11. More
  12. Licence

SAP Cloud ALM for your AI assistant

Ask your SAP Cloud ALM project questions in Claude, ChatGPT-style agents, Codex, Cursor or VS Code, and let the assistant prepare changes that you approve, field by field. An open-source MCP server, cloud-alm-mcp-server.

  • "Where does the project stand, and what changed since Friday?"
  • "What blocks UAT exit? List failed tests with their defects and the requirements without a test."
  • "Prepare the fit-gap workshop for Order to Cash."
  • "Lower 3-14 to high, due Friday, and add a note that pricing fixes it." → an approval card shows the change; nothing is written until you click Approve.

Beta (0.1.0-beta.3). MIT licence. An independent open-source project, not affiliated with or endorsed by SAP. SAP and SAP Cloud ALM are trademarks of SAP SE.

How it works

  • Your key, your machine. The server runs on your computer with a service key of the SAP Cloud ALM API from your SAP BTP subaccount. No telemetry; it talks only to SAP (PRIVACY.md).
  • The key decides. A read-only key reads. A key with write scopes also lets the assistant propose changes: create, update, comment, link, tag, delete. Every change waits for your approval in a card (or your "yes" in the chat).
  • Links back to Cloud ALM. Items come with a link that opens them in the Cloud ALM UI, and you can paste a Cloud ALM link wherever an id is asked.

1. Get a service key

Someone with admin rights in the SAP BTP subaccount of your Cloud ALM tenant creates an instance of the SAP Cloud ALM API service with the scopes in scopes/read-only.json (or read-write.json), creates a binding, and downloads its JSON. Step by step, with an e-mail you can send to your BTP admin: docs/service-key.md.

2. Install

Any client, one command (needs Node.js 22+):

npx -y cloud-alm-mcp-server@beta setup

It finds the key you downloaded in ~/Downloads, checks it against SAP, saves it readable only by you, and adds the server to Claude Code, Codex, Claude Desktop and Cursor, whichever are installed. Then open a new chat (quit and reopen Claude Desktop) and ask: "Where does my Cloud ALM project stand?"

Or pick your client:

ClientHow
Claude Desktop Download, double-click, choose your key file. No terminal, no Node.js.
Claude Code/plugin install cloud-alm --marketplace DidroAI/cloud-alm-mcp-server (server and skills)
Cursor after setup saved the key
VS Code (Copilot) after setup saved the key
Codexsetup adds it; by hand: codex mcp add cloud-alm -- npx -y cloud-alm-mcp-server@beta

All channels, by hand and in detail: docs/install.md.

Or let your agent do it

Download the key, then paste this into Claude Code, Codex, Cursor's agent or any assistant with a terminal:

Set up the SAP Cloud ALM MCP server for me: run `npx -y cloud-alm-mcp-server@beta setup` and follow what it prints (instructions for agents: https://github.com/DidroAI/cloud-alm-mcp-server/blob/main/docs/agent-setup.md). Never open or print my service key file.

Tested with Codex and Claude Code: they run setup, check with doctor, and tell you what to restart, without reading the key. What the agent follows.

3. Ask

You wantAsk, for example
The state of the project"Where does the project stand?"
What moved"What changed since Monday?"
Traceability"Trace REQ-04: stories, features, transports, tests, defects."
Gaps and audit"Which requirements have no passing test?"
Test readiness"Are we ready to exit UAT?"
Who"Who in the team can I assign the export defects to?"
SAP services"Is there planned maintenance on our systems?"

The tools behind these answers: docs/tools.md.

Skills: whole workflows

skills/ holds agent skills for the work of a functional consultant; the server also offers each one as an MCP prompt (pick it from your client's prompt or slash-command menu):

SkillFor
cloud-alm-exploreanswering questions: which tool for which question
cloud-alm-fit-gapfit-to-standard: fit, configuration or gap per requirement and process
cloud-alm-workshop-prepagenda, open questions and decisions for a workshop
cloud-alm-backlog-from-notesminutes or a transcript into requirements, user stories, tasks and comments
cloud-alm-daily-briefwhat moved since yesterday, what is at risk, what is due
cloud-alm-status-reporta steering committee or weekly status report
cloud-alm-test-readinessSIT/UAT entry and exit, go-live readiness, go / no-go
cloud-alm-defect-triageduplicates, priority, owner and due date of open defects
cloud-alm-test-designtest cases for what is untested

For Claude Code, copy a skill's folder to ~/.claude/skills/; for other agents, use the prompts or point the agent to the SKILL.md.

Approving changes

When the assistant wants to change Cloud ALM, the tool only proposes: you see the change field by field (before → after, what is created, what is deleted) and click Approve or Reject. In apps without cards, the assistant shows the change and waits for your "yes". Before writing, the server checks the change still matches what you saw. Details and limits: docs/tools.md#approving-writes.

Update, rotate, uninstall

npx -y cloud-alm-mcp-server@beta doctor      # check key, token, scopes, API, Node
npx -y cloud-alm-mcp-server@beta setup       # again after rotating the key
npx -y cloud-alm-mcp-server@beta uninstall   # remove it from your apps (--key: also the saved key)

Client configs run cloud-alm-mcp-server@beta, so you get updates on the next start.

Troubleshooting

  • "Cloud ALM is not set up yet" in the app's MCP log: run setup, or choose the key file in the extension or plugin settings.
  • Token or API errors: run doctor; it names the failing step. A corporate proxy or TLS inspection can block npx or SAP: set HTTPS_PROXY and NODE_EXTRA_CA_CERTS as your IT advises.
  • "not readable with this key": the key lacks a scope; ask for the scope named in the answer (docs/service-key.md).
  • Claude Desktop does not show the server: quit it fully (also from the tray / menu bar) and reopen.

Security

Reads are GET only, to *.alm.cloud.sap only. Writes go to a fixed allow-list of SAP APIs and only after your approval. The key is stored readable only by you and never printed or sent to the model. Text from Cloud ALM reaches the model marked as data. A key opens the whole tenant (SAP cannot limit it to one project): give read-only keys to whoever only reads. More: SECURITY.md, PRIVACY.md.

More

Licence

MIT: see LICENSE.

Questions fréquentes

Qu'est-ce que SAP Cloud ALM ?

SAP Cloud ALM: requirements, features, tests, defects, landscape; writes wait for your approval.

Comment installer SAP Cloud ALM ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add sap-cloud-alm -e 'CALM_SERVICE_KEY=<your calm_service_key>' -- npx -y cloud-alm-mcp-server@0.1.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour SAP Cloud ALM ?

Oui. Il attend CALM_SERVICE_KEY, à renseigner dans sa configuration.

SAP Cloud ALM est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient SAP Cloud ALM ?

Il est publié par DidroAI. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.