{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-sap-uxfiori-mcp-server","slug":"npm-sap-uxfiori-mcp-server","name":"@sap-ux/fiori-mcp-server","type":"mcp","url":"https://www.npmjs.com/package/@sap-ux/fiori-mcp-server","page_url":"https://unfragile.ai/npm-sap-uxfiori-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_npm-sap-uxfiori-mcp-server__cap_0","uri":"capability://tool.use.integration.sap.fiori.project.scaffolding.and.generation.via.mcp","name":"sap fiori project scaffolding and generation via mcp","description":"Generates SAP Fiori project structures (Elements, Freestyle, Worklist templates) through MCP protocol by exposing SAP UX tooling as callable tools. Implements MCP server pattern to translate AI tool-calling requests into SAP project generators, handling template selection, parameter validation, and file structure creation without requiring direct CLI invocation.","intents":["Generate a new SAP Fiori Elements application with OData service binding","Create a Freestyle Fiori project with custom UI5 components","Scaffold a Worklist template with data binding and navigation","Automate Fiori project initialization from AI agent workflows"],"best_for":["SAP developers building Fiori UIs within AI-assisted coding workflows","Teams automating SAP application scaffolding in CI/CD pipelines","AI agents orchestrating multi-step SAP development tasks"],"limitations":["Requires SAP UX tooling (@sap-ux/cli or equivalent) to be installed locally; MCP server acts as adapter, not replacement","Template customization limited to parameters exposed by underlying SAP generators; deep customization still requires manual editing","No built-in validation of OData service URLs or manifest configurations; downstream validation required","Project generation is synchronous; large projects may block MCP message processing"],"requires":["Node.js 16+","@sap-ux/cli or @sap-ux/generators package installed","MCP client implementation (Claude Desktop, custom agent framework, etc.)","Valid SAP development environment context (optional but recommended for OData binding)"],"input_types":["structured JSON parameters (project name, template type, OData service URL)","text descriptions of project requirements (parsed by MCP client into tool parameters)"],"output_types":["file system artifacts (generated project directory structure)","structured metadata (project configuration, manifest.json contents)","status messages and error logs"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-sap-uxfiori-mcp-server__cap_1","uri":"capability://tool.use.integration.mcp.tool.schema.generation.for.sap.fiori.generators","name":"mcp tool schema generation for sap fiori generators","description":"Introspects SAP UX generator APIs and exposes them as MCP-compliant tool schemas with parameter validation, descriptions, and type information. Converts SAP generator options (template types, naming conventions, OData bindings) into structured tool definitions that MCP clients can discover and invoke, handling schema serialization and parameter mapping.","intents":["Discover available SAP Fiori project templates and their configuration options","Expose SAP generator parameters as callable tools to Claude or other MCP clients","Enable AI agents to understand valid parameter combinations for Fiori scaffolding","Validate user input against SAP generator requirements before execution"],"best_for":["MCP client developers integrating SAP Fiori tooling into AI assistants","SAP development teams exposing internal generators as AI-accessible services","Builders creating multi-tool AI agents that include SAP development tasks"],"limitations":["Schema generation depends on SAP generator API stability; breaking changes in @sap-ux packages require server updates","Complex nested parameter dependencies (e.g., conditional fields based on template type) may not fully serialize into MCP schema constraints","No runtime parameter validation beyond schema type checking; semantic validation (e.g., valid OData service URLs) deferred to generator execution","Schema discovery is static at server startup; dynamic generator registration not supported"],"requires":["Node.js 16+","@sap-ux/generators or equivalent SAP UX package","MCP client with tool discovery support (Claude Desktop 0.4.0+, custom MCP implementations)","Read access to SAP generator package metadata and type definitions"],"input_types":["introspection of SAP generator APIs at server initialization"],"output_types":["MCP tool schema JSON (name, description, input_schema with JSON Schema format)","parameter metadata (required fields, enums, defaults, descriptions)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-sap-uxfiori-mcp-server__cap_2","uri":"capability://code.generation.editing.fiori.elements.template.aware.code.generation","name":"fiori elements template-aware code generation","description":"Generates SAP Fiori Elements applications with awareness of OData service contracts, manifest configurations, and UI5 component hierarchies. Implements template-driven code generation that maps OData entity properties to UI controls, creates data binding expressions, and scaffolds controller logic with proper lifecycle hooks, reducing boilerplate and ensuring SAP best practices.","intents":["Generate a Fiori Elements List Report with automatic OData binding and filtering","Create Object Page layouts with field groups and form controls bound to OData properties","Scaffold controller code with event handlers for Create, Update, Delete operations","Generate manifest.json with correct data source and routing configurations"],"best_for":["SAP developers building data-driven Fiori UIs with OData backends","Teams standardizing Fiori Elements patterns across multiple applications","AI agents automating CRUD application scaffolding for SAP systems"],"limitations":["OData service introspection requires live access to service metadata; offline generation uses template defaults","Complex OData scenarios (navigation properties, function imports, deep hierarchies) may require manual post-generation adjustments","Generated code follows SAP conventions but lacks project-specific customizations (branding, custom validators, business logic)","No support for non-OData data sources (REST APIs, custom services) without manual controller modifications"],"requires":["Node.js 16+","@sap-ux/generators with Fiori Elements templates","OData service metadata URL (optional; defaults to template structure if unavailable)","UI5 version compatibility information (1.96+)"],"input_types":["OData service metadata (XML or JSON format)","project configuration (app name, namespace, template type)","entity/property selection (which OData entities to expose in UI)"],"output_types":["generated XML view files (List Report, Object Page, Form layouts)","JavaScript controller code with data binding and event handlers","manifest.json with routing, data sources, and component configuration","i18n property files with generated labels and messages"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-sap-uxfiori-mcp-server__cap_3","uri":"capability://code.generation.editing.freestyle.fiori.ui5.component.scaffolding","name":"freestyle fiori ui5 component scaffolding","description":"Generates custom SAP Fiori Freestyle applications with UI5 component hierarchies, XML view definitions, and controller logic. Supports component composition, event binding, and model initialization patterns specific to UI5 development, enabling rapid creation of custom UI layouts without boilerplate while maintaining SAP architectural standards.","intents":["Create a custom Fiori Freestyle app with multiple views and navigation","Generate UI5 component definitions with proper lifecycle and aggregation handling","Scaffold XML views with control hierarchies and event bindings","Initialize models (JSON, OData, resource) with proper binding contexts"],"best_for":["SAP developers building custom Fiori UIs beyond Elements templates","Teams needing rapid prototyping of UI5 applications with standard patterns","AI agents generating multi-view Fiori applications with complex navigation"],"limitations":["Generated code provides structural scaffolding; complex business logic and custom validators require manual implementation","No built-in support for advanced UI5 features (routing with parameters, lazy loading, dynamic view creation) without post-generation edits","Component composition limited to simple hierarchies; deeply nested component structures may require manual refactoring","Styling and theming not generated; requires manual CSS/LESS configuration"],"requires":["Node.js 16+","@sap-ux/generators with Freestyle Fiori templates","UI5 SDK or CDN reference (1.96+)","Understanding of UI5 component model and XML view syntax"],"input_types":["project metadata (app name, namespace, component structure)","view definitions (names, control hierarchies, event handlers)","model configuration (type, data source, binding paths)"],"output_types":["Component.js with lifecycle methods and aggregation definitions","XML view files with control hierarchies and bindings","Controller files with event handler stubs and model initialization","manifest.json with routing, models, and component metadata"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-sap-uxfiori-mcp-server__cap_4","uri":"capability://tool.use.integration.mcp.protocol.server.lifecycle.management","name":"mcp protocol server lifecycle management","description":"Implements MCP server initialization, tool registration, request routing, and error handling according to MCP specification. Manages bidirectional communication with MCP clients (Claude Desktop, custom agents), handles tool invocation requests, and streams responses back through MCP protocol, abstracting transport details from SAP generator logic.","intents":["Start an MCP server that exposes SAP Fiori generators to Claude Desktop","Handle tool discovery requests from MCP clients and return available generators","Route tool invocation requests to appropriate SAP generators and return results","Manage server lifecycle (startup, shutdown, error recovery) in AI agent environments"],"best_for":["Developers integrating SAP Fiori tooling into Claude Desktop or custom MCP clients","Teams deploying SAP development tools as AI-accessible services","Builders creating multi-tool AI agents that include SAP capabilities"],"limitations":["MCP protocol version locked to specification version at server build time; client version mismatches may cause compatibility issues","No built-in authentication or authorization; relies on MCP client security model and file system permissions","Server runs in single process; concurrent tool invocations may block if generators are not async-safe","Error handling limited to MCP protocol error responses; detailed SAP generator errors may be truncated or abstracted"],"requires":["Node.js 16+","MCP client implementation (Claude Desktop 0.4.0+, or custom MCP SDK)","@sap-ux/fiori-mcp-server package installed and configured","Valid MCP server configuration (stdio or SSE transport)"],"input_types":["MCP protocol messages (tool discovery, tool invocation, resource requests)"],"output_types":["MCP protocol responses (tool schemas, invocation results, error messages)","structured data (project artifacts, metadata, status information)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-sap-uxfiori-mcp-server__cap_5","uri":"capability://code.generation.editing.manifest.and.configuration.file.generation","name":"manifest and configuration file generation","description":"Generates SAP Fiori manifest.json files with proper data source definitions, routing configurations, model initialization, and component metadata. Validates configuration against SAP schema, ensures routing paths match view hierarchies, and creates i18n property files with generated labels, reducing configuration errors and ensuring consistency across generated applications.","intents":["Generate manifest.json with OData data sources and routing configuration","Create i18n property files with labels for generated UI controls","Configure models (JSON, OData, resource) with proper binding contexts","Validate manifest configuration against SAP schema before project creation"],"best_for":["SAP developers automating Fiori application configuration","Teams standardizing manifest patterns across multiple applications","AI agents generating complete, deployable Fiori projects with valid configurations"],"limitations":["Manifest schema validation depends on SAP schema version; updates to manifest format require server updates","Complex routing scenarios (dynamic routes, lazy loading, deep linking) may require manual manifest adjustments","i18n generation limited to control labels and standard messages; custom business messages require manual addition","No validation of OData service URLs or data source availability; runtime errors may occur if services are unavailable"],"requires":["Node.js 16+","@sap-ux/generators or manifest schema definitions","Project metadata (app name, namespace, routing structure, data sources)"],"input_types":["project configuration (app name, namespace, version)","routing definitions (routes, targets, views)","data source configuration (OData service URLs, model types)","i18n labels and messages"],"output_types":["manifest.json (SAP Fiori application descriptor)","i18n property files (en.properties, de.properties, etc.)","validation reports (schema compliance, routing consistency)"],"categories":["code-generation-editing","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":38,"verified":false,"data_access_risk":"high","permissions":["Node.js 16+","@sap-ux/cli or @sap-ux/generators package installed","MCP client implementation (Claude Desktop, custom agent framework, etc.)","Valid SAP development environment context (optional but recommended for OData binding)","@sap-ux/generators or equivalent SAP UX package","MCP client with tool discovery support (Claude Desktop 0.4.0+, custom MCP implementations)","Read access to SAP generator package metadata and type definitions","@sap-ux/generators with Fiori Elements templates","OData service metadata URL (optional; defaults to template structure if unavailable)","UI5 version compatibility information (1.96+)"],"failure_modes":["Requires SAP UX tooling (@sap-ux/cli or equivalent) to be installed locally; MCP server acts as adapter, not replacement","Template customization limited to parameters exposed by underlying SAP generators; deep customization still requires manual editing","No built-in validation of OData service URLs or manifest configurations; downstream validation required","Project generation is synchronous; large projects may block MCP message processing","Schema generation depends on SAP generator API stability; breaking changes in @sap-ux packages require server updates","Complex nested parameter dependencies (e.g., conditional fields based on template type) may not fully serialize into MCP schema constraints","No runtime parameter validation beyond schema type checking; semantic validation (e.g., valid OData service URLs) deferred to generator execution","Schema discovery is static at server startup; dynamic generator registration not supported","OData service introspection requires live access to service metadata; offline generation uses template defaults","Complex OData scenarios (navigation properties, function imports, deep hierarchies) may require manual post-generation adjustments","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.5254690741041596,"quality":0.22,"ecosystem":0.45,"match_graph":0.25,"freshness":0.6,"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:24.482Z","last_scraped_at":"2026-05-03T14:23:32.233Z","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=npm-sap-uxfiori-mcp-server","compare_url":"https://unfragile.ai/compare?artifact=npm-sap-uxfiori-mcp-server"}},"signature":"k/7ymQdDWpAO/gC+roPF++uZv7r/pcEnzyN8LnMVdZr5QsVOs26w3iIO8QX6WmKvUJyOb38oqyRkPzr8Bz6eDw==","signedAt":"2026-06-20T17:44:59.606Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-sap-uxfiori-mcp-server","artifact":"https://unfragile.ai/npm-sap-uxfiori-mcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=npm-sap-uxfiori-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"}}