Skip to main content
Glama
SAP BusinessObjects MCP Server

SAP BusinessObjects MCP Server

by alexraio

Related Servers

Alternatives to SAP BusinessObjects MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to read, create, and modify SAP BW/4HANA modeling objects via the internal REST API, including aDSOs, InfoObjects, transformations, DTPs, queries, and more.
      131
      339 npm
      80
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to discover SAP B1 entities, inspect their schemas, and perform authenticated CRUD operations through natural language, translating requests into Service Layer API calls.
      316 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables language models to model SAP BW/4HANA through the BW Modeling Tools REST interface, with intent-based tools for searching, reading, writing, activating, querying data, monitoring, runtime actions, and transports. It uses compact schemas and safe-by-default permissions to complete changes in few calls.
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to access and work with an SAP ABAP system through the ABAP Development Tools (ADT) REST API. It supports searching and browsing the repository, reading, writing, activating and deleting source code and objects, running syntax checks, unit tests, ATC and SQL queries or classes, inspecting short dumps, and managing transport requests.
      222 PyPI
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to integrate with SAP systems via OData REST APIs for querying entity sets, performing CRUD operations, and executing function imports. It features automatic service discovery, CSRF token management, and smart connection handling without requiring the SAP RFC SDK.
      11
      13
      MIT

    TDQS

    B3.1/5.0

    Scored across 46 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource+action (universe metadata vs. structure, document details vs. properties vs. parameters, each data-provider aspect separately). A few boundaries blur, notably get_documents vs. get_webi_docs and get_reports (sheets) which could momentarily confuse, but descriptions disambiguate them adequately.

    Naming Consistency4/5

    Strong, predictable verb_noun snake_case throughout with consistent prefixes (get_universe_*, get_doc_*, get_dp_*, create_*, delete_*, refresh_*). Minor deviations like cms_query (noun_verb) and verbless login/logout are the only irregularities.

    Tool Count2/5

    46 tools is very high even for a complex BI platform, and several thin getters (e.g. get_dp_details, get_dp_sql, get_universe_connection_id) could be consolidated into richer calls. The surface is heavy enough that tool selection becomes a burden for an agent.

    Completeness4/5

    Broad lifecycle coverage across universes, documents, data providers, folders, users/groups, sessions, schedules, instances, and raw CMS queries. Gaps remain (no user/group creation, no document creation or schedule triggering, no comment posting), but core workflows are well supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues