Skip to main content
Glama
pmankineni

mcp-sac-tools

by pmankineni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to mcp-sac-tools

No user-submitted related servers found.

    Related Servers

    • odata-mcp-proxy

      lemaiwo
      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

    • SAP Datasphere MCP Server

      LiChenStuttgart
      A
      license
      Not graded
      quality
      C
      maintenance
      Production-ready MCP server enabling AI assistants to interact with SAP Datasphere for real tenant data discovery, metadata exploration, analytics operations, ETL data extraction, database user management, data lineage analysis, and column-level data profiling.
      MIT

    • SAP ADT MCP Server

      ethanhan2014
      F
      license
      B
      quality
      Not graded
      maintenance
      An MCP server that enables AI assistants to interact with SAP systems via the ABAP Development Tools (ADT) REST API. It allows users to read ABAP source code, inspect DDIC objects, and execute SQL queries directly.
      66
      -

    • SAP Datasphere MCP Server

      MarioDeFelipe
      A
      license
      A
      quality
      A
      maintenance
      Production-ready MCP server that enables AI assistants to seamlessly interact with SAP Datasphere environments for real tenant data discovery, metadata exploration, analytics operations, ETL data extraction, database user management, data lineage analysis, and column-level data profiling.
      39
      34 npm
      98 PyPI
      48
      MIT

    • abap-mcp

      joaodelapace
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects AI assistants to SAP systems via the ADT REST API, enabling read, write, syntax-check, and activation of ABAP code directly from the chat.
      3
      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

    A3.6/5.0

    Scored across 34 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, with descriptive names and descriptions that avoid overlap. For instance, story tools are split into get_story (metadata), get_story_detail (structure), and export tools (export pipeline), while import tools cover the full staging-to-execution workflow.

    Naming Consistency5/5

    All tools follow the consistent pattern 'sac_verb_noun' (e.g., sac_list_users, sac_create_team, sac_read_fact_data). Verbs are standard and descriptive, making tool purpose immediately clear.

    Tool Count4/5

    With 34 tools, the set is comprehensive but slightly above the typical range for a single-purpose server. However, the count is justified by the variety of domains covered (users, teams, stories, models, imports, resources, audits, utilities).

    Completeness4/5

    The tool surface covers core CRUD for users and teams, story export and detail inspection, model data access and import pipeline, plus resource listing and diagnostics. Missing are story update/delete and permission management, but the primary data operations are well-covered.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources