io.github.SAPPublished by GitHub account SAPv1.15.20Updated Nov 3, 2026
SAP Fiori - Model Context Protocol (MCP) server
SAP Fiori MCP server that lets an AI assistant generate new SAP Fiori apps and modify existing ones, plus search Fiori/UI5 docs.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
@sap-ux/fiori-mcp-serverThis package includes a Model Context Protocol (MCP) server for integration with AI coding assistants.
The server helps AI models create or modify SAP Fiori applications based on prompts, such as:
Please add a SAP Fiori elements list report app to my CAP project
Generate a new CAP project and SAP Fiori app based on my_picture.png
Generate a new SAP Fiori elements list report app for odata service https://hostname:port/sap/opu/odata4/sap/my_v4_service?sap-client=000.
ℹ️This prompt requires a saved SAP system connection by using the Connection Manager for SAP Systems extension.
Add the FCL to the SAP Fiori elements app
Enable initial load for the fiori app
For the best experience we recommend using this server alongside @cap-js/mcp-server and @ui5/mcp-server.
The server uses stdio transport and is launched via npx — no global installation required. Pick the section for your MCP client below.
Note: Replace
<version>with the specific version you want to pin to (e.g.1.12.2). The current release version is shown on the npm page. Using a pinned version rather than@latestensures reproducible behaviour and prevents untested updates from being picked up automatically.
Option A — CLI (recommended):
Option B — drop a .mcp.json file in your project root:
Open the Cline extension settings and add the server under MCP Servers:
Edit (or create) the MCP config file for your scope:
~/.cursor/mcp.json.cursor/mcp.json in your project rootEdit ~/.codeium/windsurf/mcp_config.json:
For any other MCP client, use the following npx-based configuration:
If you prefer not to use npx, install the package globally first:
Then use fiori-mcp as the command (no args needed):
The following rules help guide the AI model to use the server correctly. Add them to your system prompt or rules file:
AGENTS.md or CLAUDE.md in your project root.cursorrules in your project root.windsurfrulessearch_docsSearches SAP Fiori elements, Annotations, UI5, OPA5 Guides, SAP Fiori tools documentation for the given query.
Note: the results are based on the most recent indexed version of UI5 documentation
First-use download:
search_docsuses a local text-embedding model (all-MiniLM-L6-v2, ~86 MB) for semantic search. The model is downloaded from HuggingFace Hub on first use and cached locally (location follows theHF_HOME/TRANSFORMERS_CACHEenvironment variables, defaulting to~/.cache/huggingface/hub). Subsequent starts load the model from the cache with no network access required.
list_fiori_appsScans a specified directory to find existing SAP Fiori applications that can be modified.
list_sap_systemsLists all SAP systems stored in the user's environment (e.g. SAP Fiori tools system store). Use this when the user references a SAP system by name before calling download_odata_service_metadata or generating a Fiori application.
download_odata_service_metadataDownloads the EDMX metadata of a specific OData service from a SAP system and saves it as metadata.xml. Use this before calling generate_fiori_app_odata when the user provides a SAP system reference or service URL.
generate_fiori_app_odataGenerates a new SAP Fiori UI application for OData (non-CAP) projects, for example ABAP RESTful Application Programming Model-based OData services.
generate_fiori_app_capGenerates a new SAP Fiori UI application within an existing SAP Cloud Application Programming Model (CAP) project.
list_functionality (Step 1 of 3)Gets the list of supported modification functionalities for an existing SAP Fiori application. Requires a valid absolute path to the application.
The supported modifications are:
manifest.json properties depending on the app, for example, adding a layout based on the flexibility of the programming model or enabling initial loadget_functionality_details (Step 2 of 3)Gets the required parameters and detailed information for a specific functionality to modify an existing SAP Fiori application.
execute_functionality (Step 3 of 3)Executes a specific functionality to modify an existing SAP Fiori application with provided parameters.
By default, logging is enabled at the error level. To adjust the log level or disable logging completely, you can use the env property in your configuration.
The following log levels are supported: off, error, warn, info, debug, and verbose.
The logs are stored in the file system at ~/.fioritools/fiori-mcp-server.log
If you need the MCP server to connect to an OData server using a self-signed SSL certificate, you can use one of the following methods.
This is useful when encountering errors such as: unable to get local issuer certificate
Set the NODE_EXTRA_CA_CERTS environment variable to the path of your CA certificate file. Node.js supports multiple file extensions (.pem, .crt, .cer, .cert).
Example Configuration:
Windows Example:
macOS/Linux Example:
⚠️ Security Warning: Setting
NODE_TLS_REJECT_UNAUTHORIZED=0disables all SSL certificate validation and poses a significant security risk. Only use this in non-production environments.
You can enable and disable the collection of analytics. By default, non-personally identifiable information is used to help understand how you use the product to improve the Fiori MCP Server. In case you want to opt-out there exist two ways to disable the telemetry.
Create or change the file ~/.fioritools/telemetrysettings.json:
Set enableTelemetry to false to disable telemetry collection.
Set the environment variable SAP_UX_FIORI_TOOLS_DISABLE_TELEMETRY to true:
Setting this environment variable will disable the telemetry client.
Everyone participating in this joint project is welcome as long as our Code of Conduct is being adhered to.
Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.
Source: packages/fiori-mcp-server/README.md at commit e487f7a
Search in Fiori Documentation
Searches code snippets of Fiori Elements, Annotations, SAPUI5, Fiori tools documentation for the given query. You MUST use this tool if you're unsure about Fiori APIs. Optionally returns only code blocks.
queryrequiredmaxResultsList Fiori Applications
Scans a specified directory to find existing SAP Fiori applications that can be modified. This is an optional, preliminary tool. **Use this first ONLY if the target application's name or path is not already known.** The output can be used to ask the user for clarification before starting the main 3-step workflow.
searchPathrequiredList SAP Systems
Lists all SAP systems from the user's environment. This tool should only be used if the Service Center MCP tool list systems is unavailable. **ALWAYS** use the Service Center MCP tool 'list_systems' first if it is available. This tool is a fallback for environments where the Service Center MCP tool is not available. Also use this tool when the user asks to 'list systems', 'list backends', or any equivalent phrasing. Use this tool when the user references a SAP system by name or when you need to discover available systems before calling 'download_odata_service_metadata', 'generate_adaptation_project', or generating a Fiori application.
Takes no parameters.
Download OData Service Metadata
Downloads the metadata (EDMX) of a specific OData service URL from a SAP system and saves it as metadata.xml. Note: this tool replaces the old 'fetch-service-metadata' functionality that was previously available via the 'execute_functionality' workflow — use this tool directly instead. Usage guidelines: - Use this before calling 'generate_fiori_app_odata' when the user provides a SAP system reference and a service path. - If a service name or technical id is provided instead of a service path DO NOT USE THIS TOOL. Instead use the Service Center MCP server tool to retrieve the service metadata and then pass it to 'generate_fiori_app_odata'. - If a service path is provided by the user, use it directly via servicePath parameter. - If the user provides a system name or host, use 'list_sap_systems' first to resolve it. - Pass the full URL as sapSystemQuery. - Returns host, servicePath, client, and metadataFilePath inside the result's parameters object. - Pass ALL returned fields directly into the service config of 'generate_fiori_app_odata'. Map the returned properties to the app config service property input to 'generate_fiori_app_odata'. - **Note:** This tool is only supported in VSCode. For SAP Business Application Studio, use the Service Center MCP server tool to retrieve the service metadata instead. **IMPORTANT**: On VSCode, if the service requires authentication and the system is not already stored, ask the user to store it first. Do not ask for credentials directly. **DO NOT use this tool to refresh or update service metadata in an existing Fiori application. Instead, invoke the ['sap-fiori-create-cli' skill's 'update service-metadata' section](../sap-fiori-create-cli/SKILL.md#update-service-metadata).
appPathrequiredservicePathsapSystemQueryGenerate SAP Fiori App (OData / non-CAP)
Creates (generates) a new SAP Fiori UI application either within an existing CAP project or standalone. ALWAYS read ALL of the following instructions carefully before calling this tool. 🚨 CRITICAL - TARGET FOLDER MUST NOT EXIST 🚨 The app subfolder <project.targetFolder>/<project.name> MUST NOT already exist before calling this tool. If it exists the tool will STOP and return an error — it will NOT overwrite or merge. Do NOT pre-create that subfolder. Only the parent targetFolder may exist. 🚨 CRITICAL - READ SCHEMA FIRST 🚨 Before calling this tool, you MUST: 1. Examine the inputSchema below to understand the EXACT structure required 2. The input MUST match the schema type 'GeneratorConfigOData' with these TOP-LEVEL properties: - floorplan (must be: 'FE_LROP', 'FE_OVP', 'FE_ALP', 'FE_WORKLIST', 'FE_FEOP', 'FE_FPM', 'FF_SIMPLE', required) - project (object, required) — includes name, title, description, targetFolder, ui5Version (optional), enableTypeScript (default false), namespace (optional), viewName (FF_SIMPLE only, optional) - service (object, optional) - entityConfig (object, optional) 3. DO NOT create properties like "config", or any other structure - use ONLY the properties defined in inputSchema Steps: 1. Construct the tool arguments. - **IMPORTANT** ALWAYS use the app config schema defined by the type 'GeneratorConfigOData' to create the input structure. NEVER create an input in any other format. - The input MUST use the exact property names defined in the inputSchema: floorplan, project, service, entityConfig. - **ONLY** if the Service Center MCP is NOT available and the user provided a SAP system reference or URL with a **service path**, you **MUST** first call 'download_odata_service_metadata'. - If the Service Center MCP is available and the user provided a **service name or tech
projectrequiredservicefloorplanrequiredentityConfigGenerate SAP Fiori App (CAP)
Creates (generates) a new SAP Fiori UI application within an existing CAP project. 🚨 CRITICAL - TARGET FOLDER MUST NOT EXIST 🚨 The app subfolder <project.targetFolder>/app/<project.name> MUST NOT already exist before calling this tool. If it exists the tool will STOP and return an error — it will NOT overwrite or merge. Do NOT pre-create that subfolder. Only the parent targetFolder may exist. To populate parameters, you **MUST** use the ***CDS MCP*** to search the model for service definitions, entities, associations, and UI annotations. As a fallback, only if no such tool is available, manually read and parse all .cds files in the projectPath. The configuration **MUST** be a valid JSON object matching the tool's inputSchema and based on the project files.
projectrequiredservicefloorplanrequiredentityConfigList Supported Fiori Modification Functionalities
**(Step 1 of 3) — Use this to modify an existing SAP Fiori application.** Returns the complete list of supported modification operations for a given application, including: adding or deleting pages, creating controller extensions, and changing any Fiori Elements manifest property. This is the **first mandatory step** for modifying an existing app and requires a valid absolute path to a SAP Fiori application. You MUST use a functionalityId from this tool's output in 'get_functionality_details' (Step 2). You MUST NOT use a functionalityId as a tool name. Do not guess or assume functionalityIds — only use what this tool returns. **Note: If the target application is not known, use 'list_fiori_apps' first.** **Note: To generate a new app, use 'generate_fiori_app_odata' or 'generate_fiori_app_cap' instead.** If the functionality list does not cover your goal, use 'search_docs' as a fallback.
appPathrequiredGet Fiori Functionality Details
**(Step 2 of 3)** Gets the required parameters and detailed information for a specific functionality to modify an existing SAP Fiori application. You MUST provide a functionalityId obtained from 'list_functionality' (Step 1). The output of this tool is required for the final step 'execute_functionality' (Step 3).
appPathrequiredfunctionalityIdrequiredExecute Fiori Functionality
**(Step 3 of 3)** Executes a specific functionality to modify an existing SAP Fiori application with provided parameters. This is the **final step** of the workflow and performs the actual modification. You MUST provide the exact parameter information obtained from get_functionality_details (Step 2).
appPathrequiredparametersrequiredfunctionalityIdrequired90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
claude mcp add fiori-mcp -- npx --yes @sap-ux/fiori-mcp-server@<version> fiori-mcp{ "mcpServers": { "fiori-mcp": { "type": "stdio", "timeout": 600, "command": "npx", "args": ["--yes", "@sap-ux/fiori-mcp-server@<version>", "fiori-mcp"] } }}{ "mcpServers": { "fiori-mcp": { "type": "stdio", "timeout": 600, "command": "npx", "args": ["--yes", "@sap-ux/fiori-mcp-server@<version>", "fiori-mcp"] } }}{ "mcpServers": { "fiori-mcp": { "type": "stdio", "timeout": 600, "command": "npx", "args": ["--yes", "@sap-ux/fiori-mcp-server@<version>", "fiori-mcp"] } }}{ "mcpServers": { "fiori-mcp": { "type": "stdio", "timeout": 600, "command": "npx", "args": ["--yes", "@sap-ux/fiori-mcp-server@<version>", "fiori-mcp"] } }}{ "mcpServers": { "fiori-mcp": { "type": "stdio", "timeout": 600, "command": "npx", "args": ["--yes", "@sap-ux/fiori-mcp-server@<version>", "fiori-mcp"] } }}npm install -g @sap-ux/fiori-mcp-server{ "mcpServers": { "fiori-mcp": { "type": "stdio", "timeout": 600, "command": "fiori-mcp" } }}## Rules for creation or modification of SAP Fiori elements apps
- When asked to create an SAP Fiori elements app check whether the user input can be interpreted as an application organized into one or more pages containing table data or forms, these can be translated into a SAP Fiori elements application, else ask the user for suitable input.- The application typically starts with a List Report page showing the data of the base entity of the application in a table. Details of a specific table row are shown in the ObjectPage. This first Object Page is therefore based on the base entity of the application.- An Object Page can contain one or more table sections based on to-many associations of its entity type. The details of a table section row can be shown in an another Object Page based on the associations target entity.- The data model must be suitable for usage in a SAP Fiori elements frontend application. So there must be one main entity and one or more navigation properties to related entities.- Each property of an entity must have a proper datatype.- For all entities in the data model provide primary keys of type UUID.- When creating sample data in CSV files, all primary keys and foreign keys MUST be in UUID format (e.g., `550e8400-e29b-41d4-a716-446655440001`).- When generating or modifying the SAP Fiori elements application on top of the CAP service use the Fiori MCP server if available.- When attempting to modify the SAP Fiori elements application like adding columns you must not use the screen personalization but instead modify the code of the project, before this first check whether an MCP server provides a suitable function.- When previewing the SAP Fiori elements application use the most specific `npm run watch-*` script for the app in the `package.json`.{ "mcpServers": { "fiori-mcp": { "type": "stdio", "timeout": 600, "command": "npx", "args": ["--yes","@sap-ux/fiori-mcp-server@<version>", "fiori-mcp"], "env": { "LOG_LEVEL": "debug" } } }}{ "mcpServers": { "fiori-mcp": { "type": "stdio", "timeout": 600, "command": "npx", "args": ["--yes", "@sap-ux/fiori-mcp-server@<version>", "fiori-mcp"], "env": { "NODE_EXTRA_CA_CERTS": "/path/to/your/certificate.crt" } } }}"env": { "NODE_EXTRA_CA_CERTS": "C:\\temp\\certs\\CustomCA.crt"}"env": { "NODE_EXTRA_CA_CERTS": "/Users/username/certs/Custom_CA.crt"}{ "mcpServers": { "fiori-mcp": { "type": "stdio", "timeout": 600, "command": "npx", "args": ["--yes", "@sap-ux/fiori-mcp-server@<version>", "fiori-mcp"], "env": { "NODE_TLS_REJECT_UNAUTHORIZED": "0" } } }}{ "telemetrysettings": { "telemetrySetting": { "enableTelemetry": false } }}export SAP_UX_FIORI_TOOLS_DISABLE_TELEMETRY=true