{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm-sap-ux-fiori-mcp-server","slug":"sap-ux-fiori-mcp-server","name":"@sap-ux/fiori-mcp-server","type":"mcp","url":"https://github.com/SAP/open-ux-tools#readme","page_url":"https://unfragile.ai/sap-ux-fiori-mcp-server","categories":["mcp-servers"],"tags":["SAP Fiori tools","SAP Fiori elements","SAP Fiori freestyle","MCP","AI"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm-sap-ux-fiori-mcp-server__cap_0","uri":"capability://code.generation.editing.sap.fiori.project.scaffolding.and.generation.via.mcp","name":"sap fiori project scaffolding and generation via mcp","description":"Generates complete SAP Fiori application projects (elements, freestyle, and custom variants) through the Model Context Protocol, exposing SAP's internal project templates and configuration schemas as callable tools. The MCP server wraps SAP's Fiori project generators, allowing Claude and other MCP clients to invoke project creation with validated parameters (app type, namespace, data source bindings) and receive structured project artifacts including manifest files, routing configuration, and OData service bindings.","intents":["Generate a new SAP Fiori elements application with pre-configured OData service binding","Create a freestyle Fiori app scaffold with custom namespace and routing setup","Scaffold multiple Fiori projects programmatically with consistent naming and configuration","Initialize a Fiori app with specific UI5 version and library dependencies"],"best_for":["SAP developers building Fiori applications with AI assistance","Teams automating Fiori project initialization in CI/CD pipelines","Non-SAP developers learning Fiori patterns through guided generation"],"limitations":["Limited to SAP's pre-defined Fiori project templates — custom project structures require manual post-generation modification","OData service binding validation depends on connectivity to SAP backend systems or mock metadata","No support for legacy Fiori versions (pre-UI5 1.60) — targets modern Fiori/UI5 stack only","Generated projects require SAP development tools (SAP Business Application Studio or local UI5 toolchain) for local development"],"requires":["Node.js 18+","MCP client supporting tool calling (Claude 3.5+, or compatible MCP host)","SAP Fiori development environment or UI5 toolchain installed locally","Optional: SAP backend system or OData metadata for service binding validation"],"input_types":["structured JSON configuration (app type, namespace, service metadata)","text parameters (project name, description, author)"],"output_types":["generated project file tree (manifest.json, Component.js, routing config)","structured metadata (project structure, dependencies, configuration summary)"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-sap-ux-fiori-mcp-server__cap_1","uri":"capability://code.generation.editing.fiori.application.code.analysis.and.linting.via.mcp.tools","name":"fiori application code analysis and linting via mcp tools","description":"Analyzes SAP Fiori application source code (JavaScript, XML, JSON manifests) for compliance with SAP Fiori best practices, coding standards, and UI5 patterns. Exposes linting and analysis rules as MCP tools that validate manifest configurations, component structure, routing setup, and OData binding patterns, returning structured diagnostics with severity levels and remediation suggestions.","intents":["Validate a Fiori manifest.json for required properties and correct OData service binding syntax","Check a Fiori component for architectural compliance (correct lifecycle hooks, data binding patterns)","Lint routing configuration for common mistakes (missing route handlers, invalid pattern syntax)","Audit Fiori application for deprecated UI5 APIs or patterns that conflict with current best practices"],"best_for":["SAP development teams enforcing code quality standards across Fiori projects","Individual developers learning Fiori best practices through real-time feedback","CI/CD pipelines validating Fiori code before deployment"],"limitations":["Analysis limited to static code inspection — does not execute code or validate runtime behavior","OData binding validation requires access to service metadata; offline mode provides limited checks","Custom business logic validation not supported — only structural and pattern-based checks","No cross-project dependency analysis — each project analyzed in isolation"],"requires":["Node.js 18+","MCP client with tool-calling support","SAP Fiori project structure with manifest.json and Component.js","Optional: OData service metadata for binding validation"],"input_types":["source code (JavaScript, XML, JSON)","file paths or project directory","structured configuration objects"],"output_types":["diagnostic objects with severity, message, location, and remediation hints","structured compliance report (pass/fail per rule category)"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-sap-ux-fiori-mcp-server__cap_2","uri":"capability://search.retrieval.fiori.ui5.library.and.component.documentation.retrieval.via.mcp","name":"fiori ui5 library and component documentation retrieval via mcp","description":"Provides on-demand access to SAP UI5 library documentation, component APIs, and Fiori design patterns through MCP tools that query SAP's documentation index and return structured reference material. Tools support semantic search across UI5 controls, properties, events, and aggregations, as well as retrieval of Fiori design guidelines, code examples, and best-practice patterns for specific use cases.","intents":["Look up the API signature and properties of a specific UI5 control (e.g., sap.m.Table)","Find Fiori design guidelines for a specific UI pattern (e.g., master-detail layout)","Retrieve code examples for implementing a common Fiori feature (e.g., OData binding with filtering)","Search for UI5 controls that match a specific capability (e.g., 'date picker with range selection')"],"best_for":["Fiori developers needing quick API reference during coding","AI assistants generating Fiori code that requires accurate API signatures","Teams documenting custom Fiori components with reference to official patterns"],"limitations":["Documentation reflects a specific UI5 version snapshot — may lag behind latest releases","Search limited to indexed documentation — custom or third-party UI5 libraries not included","Code examples are illustrative, not executable — require adaptation for specific use cases","No real-time API validation — documentation accuracy depends on SAP's update frequency"],"requires":["Node.js 18+","MCP client with tool-calling support","Network access to SAP documentation index or local documentation cache","Optional: UI5 version specification for version-specific API queries"],"input_types":["text queries (control name, pattern description, feature keyword)","structured filters (UI5 version, library namespace, control category)"],"output_types":["structured API documentation (properties, events, methods, aggregations)","code examples (XML, JavaScript snippets)","design guidelines (text with formatting, visual references)"],"categories":["search-retrieval","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-sap-ux-fiori-mcp-server__cap_3","uri":"capability://data.processing.analysis.odata.service.metadata.parsing.and.binding.configuration.generation","name":"odata service metadata parsing and binding configuration generation","description":"Parses OData service metadata (EDMX/XML format) and generates Fiori-compatible data binding configurations, including manifest datasource entries, OData model initialization code, and binding path templates. Exposes MCP tools that accept OData metadata URLs or raw EDMX and return structured entity/property maps, suggested binding patterns, and auto-generated component code for common CRUD operations.","intents":["Parse an OData service metadata document and extract entity types, properties, and navigation properties","Generate a Fiori manifest datasource configuration for a given OData service URL","Create OData model initialization code and binding path templates for a specific entity","Validate OData binding paths against service metadata to catch typos and invalid property references"],"best_for":["Fiori developers integrating with SAP backend services (S/4HANA, C4C, SuccessFactors)","AI code generators creating data-bound Fiori components","Teams automating Fiori app generation from OData service definitions"],"limitations":["Metadata parsing limited to OData v2 and v4 standard formats — custom extensions may not be fully supported","Generated binding code assumes standard Fiori patterns — complex business logic requires manual implementation","No validation of OData service availability or authentication — assumes metadata is accessible","Binding path generation does not account for custom annotations or SAP-specific metadata extensions beyond standard OData"],"requires":["Node.js 18+","MCP client with tool-calling support","OData service metadata (EDMX URL or raw XML)","Optional: OData service authentication credentials for metadata retrieval"],"input_types":["OData metadata URL (string)","raw EDMX/XML metadata (text)","entity/property names (text)"],"output_types":["structured entity/property maps (JSON)","manifest datasource configuration (JSON)","OData model initialization code (JavaScript)","binding path templates (text)"],"categories":["data-processing-analysis","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-sap-ux-fiori-mcp-server__cap_4","uri":"capability://code.generation.editing.fiori.freestyle.and.elements.application.template.selection.and.customization","name":"fiori freestyle and elements application template selection and customization","description":"Provides MCP tools for selecting and customizing SAP Fiori application templates (elements-based, freestyle, or hybrid), with support for configuring template parameters (UI pattern, data source type, responsive behavior, theming). Tools expose template metadata, preview configurations, and generate customized project scaffolds based on selected template variants and user preferences.","intents":["Browse available Fiori application templates and their characteristics (elements vs freestyle, responsive support)","Select a template variant (e.g., 'master-detail elements app') and customize it with specific OData service and namespace","Generate a Fiori app from a template with pre-configured theming, responsive breakpoints, and navigation patterns","Compare template options (elements vs freestyle) for a specific use case and get recommendations"],"best_for":["Fiori developers choosing between elements and freestyle approaches for new projects","Non-SAP developers learning Fiori patterns through guided template selection","Teams standardizing on specific Fiori templates across projects"],"limitations":["Templates reflect SAP's recommended patterns — custom UI requirements may require post-generation modification","Template customization limited to predefined parameters — deep structural changes require manual code editing","No support for migrating existing Fiori apps to different templates","Template availability depends on SAP Fiori tooling version — older versions may have limited template options"],"requires":["Node.js 18+","MCP client with tool-calling support","SAP Fiori development environment or UI5 toolchain","Optional: OData service metadata for template-specific data binding"],"input_types":["template selection criteria (text: 'master-detail', 'list', 'form')","template customization parameters (JSON: namespace, service URL, theming options)"],"output_types":["template metadata (name, description, supported features, preview)","customized project scaffold (file tree, configuration)","template comparison report (features, use cases, recommendations)"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-sap-ux-fiori-mcp-server__cap_5","uri":"capability://code.generation.editing.fiori.application.testing.and.quality.assurance.tool.integration","name":"fiori application testing and quality assurance tool integration","description":"Integrates SAP's Fiori testing frameworks (OPA5, QUnit, integration testing tools) as MCP tools, enabling generation of test scaffolds, test case templates, and test execution configuration. Tools support generating unit tests for Fiori controllers, integration tests for UI interactions, and OPA5 test journeys, with support for mocking OData services and validating UI state.","intents":["Generate OPA5 test journey scaffolds for common Fiori UI interactions (navigation, form submission, filtering)","Create unit test templates for Fiori controllers with mocked OData services","Set up test configuration and mock data for a Fiori application","Generate assertions and test utilities for validating Fiori UI state and behavior"],"best_for":["Fiori development teams implementing automated testing practices","AI-assisted test generation for Fiori applications","Teams standardizing on OPA5 and QUnit across Fiori projects"],"limitations":["Generated tests are templates — require customization for complex business logic and edge cases","OPA5 test generation limited to standard UI interactions — custom controls may require manual test implementation","Mock data generation assumes standard OData patterns — complex service responses require manual setup","Test execution requires SAP testing infrastructure (Karma, QUnit runner) — not included in MCP server"],"requires":["Node.js 18+","MCP client with tool-calling support","Fiori project with Component.js and controller structure","Optional: OData service metadata for mock data generation"],"input_types":["Fiori component/controller code (JavaScript)","UI interaction descriptions (text: 'click button, verify table updates')","OData service metadata (for mock data generation)"],"output_types":["OPA5 test journey code (JavaScript)","QUnit test templates (JavaScript)","mock data and service stubs (JSON)","test configuration (karma.conf.js, test runner setup)"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-sap-ux-fiori-mcp-server__cap_6","uri":"capability://code.generation.editing.fiori.manifest.and.configuration.file.validation.and.auto.correction","name":"fiori manifest and configuration file validation and auto-correction","description":"Validates SAP Fiori manifest.json, Component.js, and other configuration files against SAP's schema definitions and best practices, providing structured diagnostics and auto-correction suggestions. Tools parse configuration files, validate against JSON schema, check for required properties, validate OData binding syntax, and suggest corrections for common configuration errors.","intents":["Validate a Fiori manifest.json against the official schema and identify missing or incorrect properties","Check OData datasource configuration for correct URL format and binding syntax","Validate routing configuration for missing route handlers or invalid pattern syntax","Auto-correct common manifest configuration errors (typos, missing required fields)"],"best_for":["Fiori developers debugging configuration issues","CI/CD pipelines validating Fiori app configuration before deployment","Teams enforcing consistent configuration standards across projects"],"limitations":["Validation limited to schema and syntax — does not validate runtime behavior or service connectivity","Auto-correction limited to obvious errors (typos, missing fields) — complex configuration logic requires manual review","Schema validation depends on SAP's schema definitions — custom extensions may not be recognized","No support for conditional configuration validation based on app type or target platform"],"requires":["Node.js 18+","MCP client with tool-calling support","Fiori manifest.json and configuration files","Optional: JSON schema definitions for custom validation rules"],"input_types":["manifest.json content (JSON)","Component.js content (JavaScript)","configuration file paths (text)"],"output_types":["validation diagnostics (errors, warnings, info messages with locations)","auto-corrected configuration (JSON)","remediation suggestions (text with code examples)"],"categories":["code-generation-editing","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-sap-ux-fiori-mcp-server__cap_7","uri":"capability://code.generation.editing.fiori.ui5.version.compatibility.checking.and.migration.assistance","name":"fiori ui5 version compatibility checking and migration assistance","description":"Analyzes Fiori application code for UI5 version compatibility issues, deprecated APIs, and breaking changes across UI5 versions. Exposes MCP tools that check component code against target UI5 versions, identify deprecated controls and properties, suggest migration paths, and generate compatibility reports with remediation steps.","intents":["Check a Fiori app for compatibility with a target UI5 version (e.g., upgrading from 1.84 to 1.120)","Identify deprecated UI5 controls and APIs used in a Fiori component","Generate a migration guide for upgrading a Fiori app to a newer UI5 version","Validate that a Fiori app uses only supported APIs for a specific UI5 version"],"best_for":["Fiori development teams planning UI5 version upgrades","Teams maintaining legacy Fiori applications with outdated UI5 versions","CI/CD pipelines validating compatibility before version upgrades"],"limitations":["Compatibility checking limited to static code analysis — does not execute code or validate runtime behavior","Migration suggestions are automated recommendations — complex refactoring may require manual implementation","Deprecated API detection depends on SAP's API change documentation — custom or third-party extensions not covered","No support for custom UI5 libraries or extensions — only standard UI5 controls and APIs"],"requires":["Node.js 18+","MCP client with tool-calling support","Fiori application source code","UI5 version compatibility database (included or fetched from SAP)"],"input_types":["source code (JavaScript, XML)","current UI5 version (text: '1.84')","target UI5 version (text: '1.120')"],"output_types":["compatibility report (JSON: issues, deprecated APIs, breaking changes)","migration guide (text with code examples and remediation steps)","refactored code suggestions (JavaScript, XML)"],"categories":["code-generation-editing","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":40,"verified":false,"data_access_risk":"high","permissions":["Node.js 18+","MCP client supporting tool calling (Claude 3.5+, or compatible MCP host)","SAP Fiori development environment or UI5 toolchain installed locally","Optional: SAP backend system or OData metadata for service binding validation","MCP client with tool-calling support","SAP Fiori project structure with manifest.json and Component.js","Optional: OData service metadata for binding validation","Network access to SAP documentation index or local documentation cache","Optional: UI5 version specification for version-specific API queries","OData service metadata (EDMX URL or raw XML)"],"failure_modes":["Limited to SAP's pre-defined Fiori project templates — custom project structures require manual post-generation modification","OData service binding validation depends on connectivity to SAP backend systems or mock metadata","No support for legacy Fiori versions (pre-UI5 1.60) — targets modern Fiori/UI5 stack only","Generated projects require SAP development tools (SAP Business Application Studio or local UI5 toolchain) for local development","Analysis limited to static code inspection — does not execute code or validate runtime behavior","OData binding validation requires access to service metadata; offline mode provides limited checks","Custom business logic validation not supported — only structural and pattern-based checks","No cross-project dependency analysis — each project analyzed in isolation","Documentation reflects a specific UI5 version snapshot — may lag behind latest releases","Search limited to indexed documentation — custom or third-party UI5 libraries not included","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.5254690741041596,"quality":0.26,"ecosystem":0.55,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.902Z","last_scraped_at":"2026-05-03T14:04:47.472Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":21199,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=sap-ux-fiori-mcp-server","compare_url":"https://unfragile.ai/compare?artifact=sap-ux-fiori-mcp-server"}},"signature":"oR1RGOUJMm4QlHU2rBSQX9ku4azichmTO8/SZ/O52cpg1B69mKzxB4+O63uRIh+aT/1MweG36IrYnjctf6m4Cg==","signedAt":"2026-06-21T15:57:33.885Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/sap-ux-fiori-mcp-server","artifact":"https://unfragile.ai/sap-ux-fiori-mcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=sap-ux-fiori-mcp-server","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}