Skip to main content
Glama
oliverluette

coBWeb

by oliverluette
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to coBWeb

No user-submitted related servers found.

    Related Servers

    • bw-modeling-mcp

      dnic-dev
      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.
      129
      267 npm
      75
      MIT

    • BW-Modeeling-mcp

      shreemanrs6
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that enables AI assistants like Claude to work directly inside SAP BW/4HANA systems — reading, creating and modifying BW modeling objects via the internal REST API used by Eclipse BWMT.
      267 npm
      MIT

    • SAP BusinessObjects MCP Server

      alexraio
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to administer, inspect, and troubleshoot BI Platform 4.3 SP5 through REST Web Services, including Web Intelligence documents, universes, CMS security, schedules, and repository hierarchy.
      46
      1
      Apache 2.0

    • ADT MCP Server

      YahorNovik
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with SAP ABAP systems through ABAP Development Tools (ADT), providing access to repository objects, source code, where-used analysis, and SQL queries with support for both on-premise and BTP systems.
      3
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    The six tools have mostly distinct roles: search finds names, read returns object definitions, context shows relationships, describe returns write-spec metadata, transport lists transport requests, and system reports environment details. The main ambiguity is that bw_describe and bw_transport both reference a missing bw_write, so an agent may wonder how their outputs are actually meant to be used.

    Naming Consistency4/5

    All tools use a consistent bw_ prefix and lowercase snake_case, which is predictable and readable. The suffix convention mixes nouns (bw_system, bw_transport, bw_context) with verbs (bw_search, bw_read, bw_describe), though this is a minor deviation rather than a serious inconsistency.

    Tool Count4/5

    Six tools is a reasonable, well-scoped count for a BW metadata and inspection server. However, the set feels slightly thin for a domain whose own tool descriptions assume an available write operation.

    Completeness2/5

    The surface is read-heavy and severe gaps exist: bw_write is repeatedly referenced but absent, and there are no create, update, delete, or transport-release operations. This will cause dead ends for any agent trying to follow the documented workflow of inspecting then modifying BW objects.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources