Skip to main content
Glama
Raistlin82

SAP OData to MCP Server

by Raistlin82

Related Servers

Alternatives to SAP OData to MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Transforms SAP S/4HANA or ECC systems into conversational AI interfaces by exposing all OData services as dynamic MCP tools. Enables natural language interactions with ERP data for querying, creating, updating, and deleting business entities through SAP BTP integration.
      29 npm
      137
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Transforms SAP S/4HANA or ECC systems into conversational AI interfaces by exposing OData services as dynamic MCP tools. Enables natural language interactions with ERP data for querying, creating, updating, and deleting business entities.
      29 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A config-driven MCP server that exposes OData and REST APIs as MCP tools, enabling AI assistants to query, manage, and monitor SAP backends through natural language.
      54 npm
      32
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants like Claude, ChatGPT, and Copilot to access SAP Business One, S/4HANA Cloud, and Concur data through MCP tools for partners, orders, invoices, expense reports, and more.
      AGPL 3.0

    TDQS

    C2.6/5.0

    Scored across 19 tools

    Disambiguation3/5

    The tool set has clear distinctions in some areas, such as authentication, service discovery, and UI components, but there is significant overlap and ambiguity in others. For example, 'business-intelligence-insights', 'business-process-insights', and 'smart-data-analysis' all involve AI-powered analysis of SAP data, making it difficult for an agent to choose the right one without deeper context. Similarly, 'kpi-dashboard-builder' and 'ui-dashboard-composer' both handle dashboard creation, leading to potential confusion.

    Naming Consistency2/5

    The naming conventions are inconsistent and chaotic, with no discernible pattern across the tools. There is a mix of styles, such as hyphenated names (e.g., 'business-intelligence-insights'), snake_case (e.g., 'check-sap-authentication' uses hyphens but resembles snake_case), and varied verb usage (e.g., 'discover-service-entities' vs. 'search-sap-services'). Some tools use descriptive phrases rather than clear verb_noun patterns, making the set hard to navigate predictably.

    Tool Count3/5

    With 19 tools, the count is borderline high for a server focused on SAP OData integration, as it includes both core data operations and extensive UI components, which might be better split into separate servers. While the scope is broad, the number feels heavy and could overwhelm an agent, especially given the overlaps. A more streamlined set of 10-15 tools might be more appropriate for this domain.

    Completeness4/5

    The tool surface is largely complete for the SAP OData domain, covering authentication, service discovery, CRUD operations, query building, analytics, and UI components. However, there are minor gaps, such as no explicit tool for deleting or updating data in a natural language context (relying on 'execute-entity-operation' with OData syntax), and the UI tools might be overly detailed for a data-focused server. Overall, agents can work around these gaps, and core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues