Skip to main content
Glama
cloud-alm-mcp-server

cloud-alm-mcp-server

by DidroAI

Related Servers

Alternatives to cloud-alm-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that bridges AI assistants to SAP Cloud ALM, exposing read APIs through four intent-based tools. It runs locally over stdio or remotely over Streamable HTTP, and can be deployed to SAP BTP Cloud Foundry.
      4
      6
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to read, review, and test ABAP code stored as abapGit files without an SAP system. Agents can list and outline objects, check Clean ABAP conventions, run full static analysis, and execute ABAP Unit tests locally on a laptop.
      5
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      ABAPilot by Crimson Consulting connects AI coding assistants to SAP ECC and on-premise S/4HANA through MCP. Use SAP source and dictionary context for ABAP explanation, review and development. Available operations depend on the deployed version and enabled endpoints. The external connector is MIT-licensed; a licensed SAP-side ABAPilot backend is required.
      49
      6
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI coding assistants to connect directly to SAP ABAP systems via ABAP Development Tools, so they can retrieve and manage source code for programs, classes, interfaces, functions, tables, and CDS views. Also supports RAP development, running unit tests and coverage checks, inspecting transports and version history, and working across multiple SAP systems.
      65
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read and write OpenText ALM Octane and Core Software Delivery Platform data — work items, backlog triage, manual and Gherkin tests, suites, runs, attachments, traceability and release status — using entity names and natural-language filters instead of numeric IDs. Accepts names for phases, users, releases and list values, translates filters into Octane OQL, returns compact output, and can be run read-only to hide all write tools.
      MIT