Fiori MCP Server

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/sap-fiori-mcp-server

About

Use cases: frontend-development, code-generation

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

7 read · 2 write · 6 delete

Secrets

None asked for

Install scripts

None found

Runs as

Node.js package

Tools (15)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• adp_controller_extensionADP Controller Extensioncan change or delete data

  Processes AI-generated controller extensions and fragments for SAPUI5 Adaptation Projects. This tool: - Validates that the project is an adaptation project (has manifest.appdescr_variant) - Reads manifest.appdescr_variant to determine layer and namespace requirements - Extracts files from the AI response (markdown code blocks with **Path:** markers) - Writes controller extension files, fragments, and other code files - Does NOT write change files (.change) - these are handled separately CRITICAL: The 'aiResponse' parameter must contain …

• download_odata_service_metadataDownload 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.…

• execute_functionalityExecute Fiori Functionalitycan change or delete data

  **(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).

• generate_adaptation_projectGenerate Adaptation Projectcan change or delete data

  Generates a new SAP Fiori adaptation project by calling the @sap-ux/adp generator. This tool requires: - system: The name of the SAP system (from list_sap_systems) - application: The application ID to adapt - appPath: The current working directory — the project subfolder is created INSIDE this folder The generated project folder will be at: <appPath>/<projectName> (default: <appPath>/app.variant) Optional parameters: projectType, targetFolder (overrides appPath), projectName, namespace, applicationTitle, client, importKeyUserChanges. …

• generate_fiori_app_capGenerate SAP Fiori App (CAP)can change or delete data

  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. …

• generate_fiori_app_odataGenerate SAP Fiori App (OData / non-CAP)can change or delete data

  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 thi…

• get_functionality_detailsGet Fiori Functionality Detailsread-only

  **(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).

• list_fiori_appsList Fiori Applicationsread-only

  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.

• list_functionalityList Supported Fiori Modification Functionalitiesread-only

  **(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). …

• list_sap_systemsList SAP Systemsread-only

  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 …

• lookup_ui5_documentationLook up UI5 Documentationread-only

  Looks up UI5 control documentation from a library's designtime api.json. This tool: - Reads ui5.yaml (discovered from the provided appPath) to resolve the configured UI5 base URL and version, falling back to the public https://ui5.sap.com when none is found - Fetches (and caches) the control's api.json and extracts the requested piece of documentation - Currently supports lookupType "aggregation" (type, cardinality, visibility, since, description), "property" (type, defaultValue, group, bindable, visibility, since, description), and "event" (parameters, visibil…

• open_adaptation_editorOpen Adaptation Editor

  Starts the adaptation editor server by running 'npx fiori run /test/adaptation-editor.html' in the adaptation project directory. This tool: - Spawns the editor server process in the background - Extracts the server URL and editor path from the command output - Returns the full editor URL and process ID - Provides instructions on how to stop the editor process The editor server will run independently in the background. Use the returned process ID or port to stop it if needed.

• read_odata_metadata_adpRead OData Metadata for Adaptation Projectread-only

  Reads the OData metadata for the specified Adaptation Project. This tool: - Reads the SAP system connection details from the provided appPath (using ui5.yaml configuration) - Connects to the SAP system and retrieves the OData metadata - Returns the OData metadata of the merged app descriptor for the Adaptation Project Use this tool when you need to read the OData metadata for an Adaptation Project.

• run_rta_workflow_stepRun RTA Workflow Stepcan change or delete data

  Drives Runtime Authoring (RTA) in the SAP Fiori adaptation editor through a dispatched step protocol. Each call advances one step of the workflow; steps must be called in sequence. `site` is the editor URL from `open_adaptation_editor` — pass it on every step. Steps: - **start** — `site` (required, top-level), `frameId` (required, top-level, always `"preview"`). Launches the editor URL, starts RTA, returns `{ site, frameId?, rtaStarted: true }`. Echo `site` and `frameId` back on every subsequent step. - **get_overlays** — site + optional frameId. Returns `{ overlays: O…

• search_docsSearch in Fiori Documentationread-only

  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.

Signals

Stars

159

Forks

70

Open issues

221

Contributors

91

Last commit (this folder)

Oct 23, 2026 (5 days ago)

Last release

Oct 23, 2026 (5 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.SAP/fiori-mcp-server

Version

1.15.15

Auth

No auth

Packages

npm @sap-ux/fiori-mcp-server

License

Apache-2.0

Repository

github.com/SAP/open-ux-tools

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql