Skip to main content
Glama
marianfoo

SAP Documentation MCP Server

by marianfoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to SAP Documentation MCP Server

No user-submitted related servers found.

    Related Servers

    • ABAP MCP Server

      DXCHowardB
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides unified ABAP and RAP documentation search, document retrieval, and ABAP feature matrix lookups. It also enables local ABAP linting to streamline development and documentation workflows via the Model Context Protocol.
      -

    • mcp-abap-keyword

      yynhr
      A
      license
      A
      quality
      D
      maintenance
      Enables searching and browsing ABAP keyword documentation from SAP's official help site, including keyword lookup, glossary terms, and topic exploration.
      6
      MIT

    • DevDocs MCP Server

      JavierDevCol
      F
      license
      A
      quality
      D
      maintenance
      Provides AI models with direct access to documentation for over 600 technologies from DevDocs.io, including popular languages, frameworks, and tools. It enables comprehensive searching, content retrieval, and offline access via an intelligent local caching system.
      12
      2
      -
    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

    A4.4/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target clearly distinct resources (BTP service catalog, ABAP released objects, UI5 release diffs, ABAP feature matrix, docs), and the descriptions explicitly resolve the trickiest overlap between `search` and `sap_community_search` ('use this dedicated tool only when...'). The `sap_discovery_center_search`/`sap_discovery_center_service` and `sap_search_objects`/`sap_get_object_details` search-vs-detail pairs are clearly delineated, leaving only mild potential confusion between the general `search` and the specialized search tools.

    Naming Consistency3/5

    All names use snake_case, which is consistent, but the prefixing and verb placement are mixed: some tools carry a `sap_` domain prefix (`sap_search_objects`, `sap_get_object_details`), others carry a sub-domain prefix (`ui5_version_diff`, `abap_feature_matrix`), and the core `search`/`fetch` have no prefix at all. The conventions remain readable but there is no single predictable pattern.

    Tool Count5/5

    Nine tools is well within the ideal 3-15 range and each earns its place: coherent search+detail pairs for BTP services and ABAP objects, a docs search+fetch workflow, plus two self-contained reference tools (UI5 diff, ABAP feature matrix). No obvious redundancy or filler.

    Completeness4/5

    Core workflows are complete: docs use a search→fetch pattern, and both the BTP service catalog and ABAP object lookup have matching search + detail tools. Minor gaps exist (the standalone `ui5_version_diff` and `abap_feature_matrix` have no complementary tools, and there's no source/listing/browse operation), but agents can work around these.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources