Skip to main content
Glama
par4987

@pired/sap-fiori-mcp-server

by par4987
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @pired/sap-fiori-mcp-server

No user-submitted related servers found.

    Related Servers

    • MCP SAPUI5 Server

      santiagosanmartinn
      A
      license
      C
      quality
      D
      maintenance
      A specialized MCP server for SAPUI5 and Fiori development that enables code generation, project analysis, and refactoring for JavaScript-based applications. It provides comprehensive tools for managing OData features, validating code compatibility, and searching official SAPUI5 SDK and MDN documentation.
      51
      MIT

    • UI5 MCP Server

      yan252
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for SAP UI5/OpenUI5 development, enabling creation of UI5 apps, API reference, guidelines, manifest validation, and code linting.
      63,675 npm
      Apache 2.0

    • abap-config-mcp

      OCA-BE
      A
      license
      Not graded
      quality
      D
      maintenance
      A standalone MCP server for SAP ABAP development and customizing that connects directly to your SAP system via ADT REST API, enabling AI assistants to search, read, write, activate, transport, debug, and run quality checks on ABAP code, as well as manage customizing/IMG configurations with governed transport recording.
      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.9/5.0

    Scored across 27 tools

    Disambiguation4/5

    Each tool maps to a distinct resource/action (apps, systems, destinations, CAP models, OData services), and the descriptions clarify boundaries. A few pairs like get_guidelines/search_docs or generate_fiori_app_odata/create_ui5_app could be momentarily confused, but the descriptions disambiguate them well.

    Naming Consistency4/5

    Almost all tools follow snake_case verb_noun naming (list_*, get_*, run_*, query_*). Minor deviations: create_ui5_app vs generate_fiori_app_*, btp_login is noun_verb, and list_functionality is singular while other list_* tools are plural.

    Tool Count2/5

    27 tools exceeds the 25+ threshold and feels heavy for an MCP surface, even for a broad SAP Fiori domain. Several guideline, validation, and connection tools could be consolidated into parameterized tools, so the count is more likely to overwhelm agents than help them.

    Completeness4/5

    The tool surface covers the main lifecycle: discover/create/modify Fiori apps, query OData/CAP data, fetch metadata, validate/lint, and access documentation. Missing build/deploy/test operations and full CRUD for CAP entities or destinations are minor gaps given the server's stated scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources