SAP Fiori MCP Server

Official SAP MCP server that lets AI coding assistants create and modify SAP Fiori applications, pages, and manifest properties via natural language.

Developer Tools by SAP None active

GitHub Docs npm: @sap-ux/fiori-mcp-server

Overview

The SAP Fiori MCP server (@sap-ux/fiori-mcp-server) is an official, open-source Model Context Protocol server published by SAP as part of the open-ux-tools monorepo. It enables AI coding assistants like Claude Code, Cursor, Cline, and Windsurf to generate new SAP Fiori applications, modify existing ones, and manage pages, controllers, and manifest properties in both SAP Cloud Application Programming Model (CAP) projects and standalone OData service projects.

The server exposes five tools: documentation search across SAP Fiori elements, Annotations, UI5, and SAP Fiori tools docs; discovery of existing Fiori apps in a directory; and a three-step functionality workflow (list_functionalities, get_functionality_details, execute_functionality) that the AI uses to plan and apply changes safely. It is designed to be used alongside SAP's complementary @cap-js/mcp-server (CAP data model and services) and @ui5/mcp-server (UI5 control and library knowledge).

The server is currently labeled experimental by SAP and is subject to rapid change. It runs locally over stdio, optionally integrates with the "Connection Manager for SAP Systems" extension for OData service access, and supports configurable logging, custom CA certificates, and telemetry opt-out.

Tools

Tool	Description
`search_docs`	Searches SAP Fiori elements, Annotations, UI5, and SAP Fiori tools documentation for relevant guidance.
`list_fiori_apps`	Scans a specified directory to identify existing SAP Fiori applications that can be modified.
`list_functionalities`	Step 1 of 3. Lists the supported functionalities available for creating new or modifying existing SAP Fiori applications.
`get_functionality_details`	Step 2 of 3. Returns the required parameters and schema for a specific functionality before execution.
`execute_functionality`	Step 3 of 3. Executes the selected functionality with the supplied parameters to generate or modify the Fiori application.

Setup Guide

Prerequisites

Node.js with npx available on PATH
Optional: SAP Cloud Application Programming Model (CAP) for CAP-based app generation
Optional: Access to an OData v4 or ABAP RESTful Application Programming Model service
Optional: "Connection Manager for SAP Systems" extension if you need to bind apps to saved SAP system connections

Installation

Recommended (Claude Code CLI):

claude mcp add fiori-mcp -- npx --yes @sap-ux/fiori-mcp-server@latest fiori-mcp

Or install globally with npm:

npm install -g @sap-ux/fiori-mcp-server

MCP client config

Add the following to your MCP client configuration (Claude Desktop, Cursor, Cline, Windsurf, etc.):

{
  "mcpServers": {
    "fiori-mcp": {
      "type": "stdio",
      "timeout": 600,
      "command": "npx",
      "args": ["--yes", "@sap-ux/fiori-mcp-server@latest", "fiori-mcp"]
    }
  }
}

Optional environment variables

LOG_LEVEL: one of off, error, warn, info, debug, verbose
NODE_EXTRA_CA_CERTS: path to a custom CA certificate file (.pem, .crt, .cer, .cert)
NODE_TLS_REJECT_UNAUTHORIZED=0: disables SSL validation (not recommended)
SAP_UX_FIORI_TOOLS_DISABLE_TELEMETRY=true: disables analytics collection

Server logs are written to ~/.fioritools/fiori-mcp-server.log.

Recommended companions

For the best experience, install alongside SAP's other official MCP servers:

@cap-js/mcp-server for CAP project and data model support
@ui5/mcp-server for SAPUI5 control and library knowledge

Use Cases

Scaffold a new SAP Fiori elements list report or object page app inside an existing CAP project from a natural language prompt
Discover all Fiori apps in a monorepo and apply consistent manifest or page configuration changes across them
Look up SAP Fiori elements annotations or UI5 control documentation inline while an AI agent is editing code
Add or modify pages, controllers, and navigation in an existing Fiori app without hand-writing manifest.json edits
Bootstrap a Fiori UI on top of an OData v4 or ABAP RAP service through an AI coding assistant

Example Prompts

"Add a SAP Fiori elements list report app to my CAP project bound to the Books service."
"List all the Fiori apps in this workspace and tell me which ones use Fiori elements."
"Search the SAP Fiori docs for how to configure a quick filter on a list report."
"Add an object page for the Authors entity to the existing Fiori app under apps/library."
"Show me the parameters required to generate a new freestyle SAPUI5 app, then create one called inventory-ui."

Pros

Officially built and maintained by SAP, published in the SAP/open-ux-tools monorepo
Three-step functionality workflow (list then details then execute) gives the AI a safe, schema-driven path to making project changes
Works with any standard MCP client (Claude Code, Cursor, Cline, Windsurf) over stdio
Designed to compose with @cap-js/mcp-server and @ui5/mcp-server for full-stack SAP AI development

Limitations

Labeled experimental by SAP and subject to rapid breaking changes
Telemetry is enabled by default and must be explicitly disabled via env var or config
OData service binding requires the separate "Connection Manager for SAP Systems" extension and pre-saved system connections

Alternatives

@ui5/mcp-server: SAP's official MCP server for SAPUI5 control and library knowledge
@cap-js/mcp-server: SAP's official MCP server for the Cloud Application Programming Model
Community SAP MCP collections such as marianfoo/sap-ai-mcp-servers that aggregate multiple SAP-focused servers