Skip to main content
Glama
gregorwolf

cloud-alm-itsm-mcp

by gregorwolf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to cloud-alm-itsm-mcp

No user-submitted related servers found.

    Related Servers

    • SAP CPI MCP Server

      premsaidaggolu
      A
      license
      B
      quality
      B
      maintenance
      MCP server for monitoring and managing SAP Cloud Integration (CPI) tenants via OData APIs, supporting multi-tenant configurations and extensive tools for message logs, integration flows, deployments, and admin operations.
      46
      MIT

    • solman-fb-mcp

      odaiadnan23-design
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for AI assistants to create and manage SAP Solution Manager Focused Build Requirements and navigate the Solution Documentation process hierarchy via SAP OData API.
      -

    • calmcp

      consetto
      A
      license
      A
      quality
      A
      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
      2
      MIT

    • SAP-MCP

      NhatPD-VNEXT
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for SAP on-premise via ADT, enabling multi-system connection, code navigation, data queries, and debugging through natural language. Includes a web admin and runtime diagnostics.
      MIT

    • sap-mcp

      Tjarliman
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for SAP S/4HANA via the ADT API, enabling querying and reading SAP systems with production write protection.
      2 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 5 tools

    Disambiguation2/5

    All five tools are variations of retrieving installations with different filter criteria. get_installations is the base list, while by_system_type, by_customer, by_product, and search_installations overlap heavily, with search_installations effectively covering the same use cases as the others.

    Naming Consistency4/5

    Most tools follow a consistent get_installations_by_X pattern, but search_installations deviates by using a different verb. Aside from this one exception, the naming is predictable and readable.

    Tool Count2/5

    Five tools are dedicated to a single read operation (listing installations) with different filters. This is over-fragmented; a single tool with flexible filter parameters would suffice. The count feels unnecessarily high for the narrow scope.

    Completeness2/5

    The server only provides read/filter capabilities for installations. There are no create, update, delete, or lifecycle operations, and the server name suggests a broader ITSM scope that the tools do not cover, leaving significant gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources