Developer-tools MCP server
SAP Fiori MCP
Version history of discovered tools, schemas, and declared agent authority.
OBSERVED INTERFACE
Capability surface
Modelara’s observed declarations are shown separately from its derived effect classifications.
- 5
- 1
- 3
- 0
Unknown means Valyd could not determine the capability's effect confidently from the declared interface and static evidence. It is not treated as safe.
- Package
- @sap-ux/fiori-mcp-server@1.16.3
- Registry
- npm
- Published
- Nov 13, 2026
- Integrity
sha512-ggALNzWPvb4eFKx94jhBj2wwO+rUUCzBDuAMECO9s4SSwWSqt2pSSh+WRPMrX/m/UIGmneakMh5h2dCErrabzA==- Analyzer
- modelara v0.1.8 · policy not recorded
- Repository
- https://github.com/SAP/open-ux-tools
9 capabilities
| Capability | Type | Derived effect | First observed in Valyd coverage | Last changed |
|---|---|---|---|---|
download_odata_service_metadatasap-fiori:tool:download_odata_service_metadataObserved interface and hashesDownloads 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). Input schemasha256:755042caddef45f1e5858950a7356d004a009a50b8d686f469c409ec92552d21Output schemasha256:70eb3ee3918d63cb56f185f45606fed6f096bb2d1cef0ed6a943aaf7945c0159Description hash: Interface hash: Other observed Modelara metadata | tool | 1.16.1 | No change observed | |
execute_functionalitysap-fiori:tool:execute_functionalityObserved interface and hashes**(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). Input schemasha256:eff4c93ba3e72bcc5bbec426c5d6901c273e0c97be28ca0f728eb3c5ea4cd019Output schemasha256:c33d9ce2186b70f7e7dad576dec4ade4db74399a9770b4382582f11432d25626Description hash: Interface hash: Other observed Modelara metadata | tool | 1.16.1 | No change observed | |
generate_fiori_app_capsap-fiori:tool:generate_fiori_app_capObserved interface and hashesCreates (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. Input schemasha256:1623765f3ed3fdb66c2e6082fd9217f09f8d9243ff4299a0869f047261782873Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.16.1 | No change observed | |
generate_fiori_app_odatasap-fiori:tool:generate_fiori_app_odataObserved interface and hashesCreates (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 technical service id**, you **MUST** call the Service Center MCP server tool to retrieve the metadata and properties required for the service property of the input. - Use the data returned to provide the required values (host, servicePath, client, destination, metadataFilePath) directly in the service property of the input. - If the Service Center MCP was used both host and destination **MUST** be passed in the service property of the input. - If Fiori MCP 'download_odata_service_metadata' was used and returns a host URL — pass it as service.host. If the host is not provided, you **MUST** ask for it. - **IMPORTANT**: On VSCode, if the service requires authentication and is not already stored, ask the user to store it first. Never ask for credentials directly. 2. Parse the metadata.xml to understand the data model (entities, associations). Set mainEntity to the entity that best matches the user's request. If that entity has to-many navigation properties, set navigationEntity using the most relevant child EntitySet and navigation property Name. 3. Generate the application once the config is complete and valid. Example of CORRECT input structure (ui5Version is optional — omit to let the MCP server resolve the latest stable version from ui5.sap.com): { "floorplan": "FE_LROP", "project": { "name": "my-travel-app", "title": "My Travel App", "description": "Travel management application", "targetFolder": "/home/user/projects", "enableTypeScript": false, "namespace": "com.mycompany" }, "service": { "host": "https://my-system.example.com", "servicePath": "<full-odata-service-path>", "client": "000", "metadataFilePath": "/home/user/projects/metadata.xml", "destination": "MY_DESTINATION" }, "entityConfig": { "mainEntity": { "entityName": "Travel" }, "navigationEntity": { "EntitySet": "Booking", "Name": "_Booking" }, "generateFormAnnotations": true, "generateLROPAnnotations": true } } Input schemasha256:e054f8adc188918f545dd963e2e7e9a572ae2ee99e1859f8b7f12c7649c73902Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.16.1 | No change observed | |
get_functionality_detailssap-fiori:tool:get_functionality_detailsObserved interface and hashes**(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). Input schemasha256:3b77bdea023be70eb4dde7f8ec217cca511de7fd3f09caee36784a3b20c97327Output schemasha256:7475a6ee9d4d2718f2c4132796e84a1a52323495eb74ddc36c1af5f9f7b858baDescription hash: Interface hash: Other observed Modelara metadata | tool | 1.16.1 | No change observed | |
list_fiori_appssap-fiori:tool:list_fiori_appsObserved interface and hashesScans 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. Input schemasha256:1eb679b84e0c656a6c086fd8995bebc2d64c66d26a7dac9a623003c180a2a24bOutput schemasha256:d2fe9954efb8c0a4bc620d9aaa26f0cf953c176d39a3cd905b848e3bb51d0b11Description hash: Interface hash: Other observed Modelara metadata | tool | 1.16.1 | No change observed | |
list_functionalitysap-fiori:tool:list_functionalityObserved interface and hashes**(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. Input schemasha256:0086c9a1bfa9c2a176ed4d0b5051eade58f3c8c6e48340a184d3f342159b6e56Output schemasha256:644586acaec8f21f0271bc0af43901c6e2bbb38882c1471e65d0759b6657abb5Description hash: Interface hash: Other observed Modelara metadata | tool | 1.16.1 | No change observed | |
list_sap_systemssap-fiori:tool:list_sap_systemsObserved interface and hashesLists 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. Input schemasha256:3178d649f32f96ea850da50c27c062f5c20cbef86dec2f5af0587dff56ebdb67Output schemasha256:2fd0c091c2af5e0c73714183abbcfd8615187b3bc04fe71fadba261c5837e95fDescription hash: Interface hash: Other observed Modelara metadata | tool | 1.16.1 | No change observed | |
search_docssap-fiori:tool:search_docsObserved interface and hashesSearches 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. Input schemasha256:c9c5b305164bb1d0fb5f5438ff65a8eba8505e08f907cb2da992e8e7f96c49b0Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.16.1 | No change observed |
No capabilities match these filters.
STATIC COMPARISONS
Release history
- 1.16.2 1.16.3PASS0 added0 removed0 schema0 write0 destructive0 unknown
- 1.16.1 1.16.2PASS0 added0 removed0 schema0 write0 destructive0 unknown