{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-ui5mcp-server","slug":"npm-ui5mcp-server","name":"@ui5/mcp-server","type":"mcp","url":"https://www.npmjs.com/package/@ui5/mcp-server","page_url":"https://unfragile.ai/npm-ui5mcp-server","categories":["mcp-servers"],"tags":["openui5","sapui5","ui5","development","mcp"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-ui5mcp-server__cap_0","uri":"capability://tool.use.integration.sapui5.openui5.project.introspection.and.metadata.extraction","name":"sapui5/openui5 project introspection and metadata extraction","description":"Exposes UI5 project structure, component hierarchies, and manifest metadata through MCP protocol endpoints. Parses manifest.json files, analyzes component dependencies, and extracts control definitions to provide LLM-accessible project context without requiring direct filesystem access. Uses MCP resource and tool abstractions to surface UI5-specific metadata as structured data.","intents":["I need to understand the structure of an existing UI5 project before generating new components","I want to query what controls and libraries are available in my UI5 application","I need to extract component dependencies and hierarchy to understand code organization"],"best_for":["UI5 developers using Claude or other MCP-compatible LLMs for code generation","Teams building AI-assisted UI5 development workflows","Developers migrating legacy UI5 projects and needing automated documentation"],"limitations":["Requires valid UI5 project structure with manifest.json — non-standard projects may not be fully introspectable","Metadata extraction depth depends on manifest completeness — incomplete manifests yield partial context","No real-time project change detection — requires server restart to reflect new components or dependencies"],"requires":["Node.js 16+","Valid SAPUI5 or OpenUI5 project with manifest.json","MCP-compatible client (Claude, Cline, or other MCP host)"],"input_types":["project path (string)","component name (string)","library identifier (string)"],"output_types":["JSON (manifest structure)","structured metadata (component hierarchy)","control definitions (control properties and aggregations)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-ui5mcp-server__cap_1","uri":"capability://code.generation.editing.ui5.control.and.component.code.generation.with.manifest.awareness","name":"ui5 control and component code generation with manifest awareness","description":"Generates SAPUI5/OpenUI5 component code, controllers, and views with awareness of project manifest, available libraries, and component dependencies. Leverages extracted project metadata to suggest appropriate controls, namespaces, and library imports. Integrates with LLM code generation to produce UI5-compliant XML views, JavaScript controllers, and component definitions that match project conventions.","intents":["Generate a new UI5 component that follows my project's library versions and naming conventions","Create a controller with data binding and event handlers for an existing view","Generate a form view using the correct controls available in my UI5 library version"],"best_for":["UI5 developers using Claude with MCP to scaffold new components","Teams standardizing UI5 component structure across projects","Developers accelerating UI5 development with AI-assisted code generation"],"limitations":["Code generation quality depends on LLM's UI5 knowledge — may require manual refinement for complex patterns","Does not validate generated code against UI5 linting rules — requires separate validation step","Limited to component/view/controller generation — does not generate tests or documentation"],"requires":["Node.js 16+","MCP server running with project context loaded","LLM client with code generation capability (Claude 3+, etc.)"],"input_types":["component name (string)","control types (string array)","data model schema (JSON)"],"output_types":["XML (UI5 views)","JavaScript (controllers, components)","JSON (manifest fragments)"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-ui5mcp-server__cap_2","uri":"capability://tool.use.integration.mcp.tool.registry.and.function.calling.for.ui5.operations","name":"mcp tool registry and function calling for ui5 operations","description":"Exposes UI5 development operations (component creation, manifest updates, control queries) as MCP tools with schema-based function calling. Implements MCP tool protocol to allow LLM clients to invoke UI5-specific functions with structured arguments and receive JSON responses. Handles tool invocation routing, argument validation, and error handling within the MCP server lifecycle.","intents":["I want my LLM to be able to query UI5 controls and components as function calls","I need the LLM to invoke UI5 operations (create component, update manifest) directly","I want structured, schema-validated tool calls for UI5 development tasks"],"best_for":["Developers building AI agents for UI5 development","Teams integrating UI5 tooling with LLM-based IDEs (Cline, Cursor, etc.)","Organizations standardizing on MCP for AI-assisted development workflows"],"limitations":["Tool execution is synchronous — long-running operations (large project analysis) may timeout","No built-in transaction support — concurrent tool calls may cause race conditions on shared project files","Tool schemas must be manually maintained in sync with implementation — schema drift can cause validation failures"],"requires":["Node.js 16+","MCP-compatible client with tool calling support","Valid UI5 project structure"],"input_types":["JSON (tool arguments matching schema)"],"output_types":["JSON (tool results)","error responses (structured error objects)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-ui5mcp-server__cap_3","uri":"capability://data.processing.analysis.ui5.manifest.json.parsing.and.validation","name":"ui5 manifest.json parsing and validation","description":"Parses and validates SAPUI5/OpenUI5 manifest.json files to extract application metadata, library dependencies, component definitions, and configuration. Implements manifest schema validation to ensure compliance with UI5 manifest specifications. Exposes parsed manifest data through MCP endpoints for LLM access, enabling context-aware code generation and project analysis.","intents":["I need to understand what libraries and versions my UI5 app depends on","I want to validate that my manifest.json is correctly structured","I need to extract routing, data sources, and component configuration from the manifest"],"best_for":["UI5 developers analyzing project dependencies and configuration","Teams validating manifest compliance in CI/CD pipelines","Developers using LLMs to understand or modify UI5 application configuration"],"limitations":["Validation is schema-based only — does not check semantic correctness (e.g., missing library versions)","Does not resolve library versions from registries — requires manifest to explicitly declare versions","Limited to manifest.json format — does not parse .ui5.yaml or other configuration formats"],"requires":["Node.js 16+","Valid manifest.json file in UI5 project root"],"input_types":["manifest.json file path (string)"],"output_types":["JSON (parsed manifest)","validation results (error array)"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-ui5mcp-server__cap_4","uri":"capability://search.retrieval.ui5.library.and.control.discovery.with.property.introspection","name":"ui5 library and control discovery with property introspection","description":"Discovers available UI5 libraries, controls, and their properties by parsing library metadata and control definitions. Provides LLM-accessible queries to list available controls, retrieve control properties/aggregations, and identify compatible libraries for a given UI5 version. Implements caching of library metadata to optimize repeated queries and reduce filesystem I/O.","intents":["I want to know what controls are available in sap.m library for my UI5 version","I need to find the correct property names and types for a specific control","I want to discover which libraries provide a particular control or functionality"],"best_for":["UI5 developers using LLMs to discover available controls and APIs","Teams building UI5 code generation tools with control awareness","Developers validating control usage against available properties"],"limitations":["Library metadata discovery depends on installed UI5 libraries — missing libraries will not be discoverable","Control property introspection is static — does not reflect runtime property changes or extensions","Caching may become stale if libraries are updated without server restart"],"requires":["Node.js 16+","UI5 libraries installed in project node_modules or accessible via npm","MCP server running with library metadata loaded"],"input_types":["library name (string, e.g., 'sap.m')","control name (string, e.g., 'Button')","UI5 version (string, optional)"],"output_types":["JSON (control definitions with properties)","array (list of available controls)","metadata (property types and aggregations)"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-ui5mcp-server__cap_5","uri":"capability://automation.workflow.mcp.server.lifecycle.management.and.resource.exposure","name":"mcp server lifecycle management and resource exposure","description":"Implements MCP server initialization, resource registration, and lifecycle management for UI5 development context. Exposes UI5 project resources (components, views, controllers, manifests) through MCP resource protocol, allowing LLM clients to read and reference project files. Handles server startup, configuration loading, and graceful shutdown with proper resource cleanup.","intents":["I want to start an MCP server that exposes my UI5 project to Claude","I need the LLM to be able to read and reference files in my UI5 project","I want to configure which project directories and resources are exposed to the LLM"],"best_for":["Developers integrating UI5 projects with MCP-compatible LLM clients","Teams setting up AI-assisted development environments for UI5","Organizations deploying MCP servers for multiple UI5 projects"],"limitations":["Resource exposure is read-only by default — write operations require explicit tool implementation","No built-in authentication or access control — assumes trusted LLM client environment","Server configuration is static at startup — requires restart to expose new projects or resources"],"requires":["Node.js 16+","npm or yarn package manager","MCP-compatible client (Claude, Cline, etc.)"],"input_types":["configuration file (JSON or YAML)","project path (string)"],"output_types":["MCP server instance","resource URIs (for LLM access)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-ui5mcp-server__cap_6","uri":"capability://code.generation.editing.context.aware.code.completion.and.suggestion.for.ui5.patterns","name":"context-aware code completion and suggestion for ui5 patterns","description":"Provides context-aware code suggestions and completions for UI5-specific patterns (data binding syntax, control hierarchies, event handler patterns) by analyzing project context and manifest metadata. Integrates with LLM code generation to suggest appropriate UI5 idioms, control usage patterns, and best practices based on project configuration and available libraries.","intents":["I want the LLM to suggest the correct data binding syntax for my UI5 view","I need code completions for event handlers that follow my project's patterns","I want suggestions for control hierarchies and nesting that match UI5 best practices"],"best_for":["UI5 developers using LLMs for code generation with pattern awareness","Teams standardizing UI5 coding patterns across projects","Developers accelerating UI5 development with intelligent code suggestions"],"limitations":["Suggestions depend on LLM's UI5 knowledge — may not reflect latest UI5 versions or features","Context injection adds latency to code generation — larger projects may see slower completions","No validation of suggested patterns — requires manual review for correctness"],"requires":["Node.js 16+","MCP server with project context loaded","LLM client with code generation capability"],"input_types":["partial code (string)","file context (string)","project metadata (JSON)"],"output_types":["code suggestions (string array)","pattern recommendations (structured data)"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":39,"verified":false,"data_access_risk":"high","permissions":["Node.js 16+","Valid SAPUI5 or OpenUI5 project with manifest.json","MCP-compatible client (Claude, Cline, or other MCP host)","MCP server running with project context loaded","LLM client with code generation capability (Claude 3+, etc.)","MCP-compatible client with tool calling support","Valid UI5 project structure","Valid manifest.json file in UI5 project root","UI5 libraries installed in project node_modules or accessible via npm","MCP server running with library metadata loaded"],"failure_modes":["Requires valid UI5 project structure with manifest.json — non-standard projects may not be fully introspectable","Metadata extraction depth depends on manifest completeness — incomplete manifests yield partial context","No real-time project change detection — requires server restart to reflect new components or dependencies","Code generation quality depends on LLM's UI5 knowledge — may require manual refinement for complex patterns","Does not validate generated code against UI5 linting rules — requires separate validation step","Limited to component/view/controller generation — does not generate tests or documentation","Tool execution is synchronous — long-running operations (large project analysis) may timeout","No built-in transaction support — concurrent tool calls may cause race conditions on shared project files","Tool schemas must be manually maintained in sync with implementation — schema drift can cause validation failures","Validation is schema-based only — does not check semantic correctness (e.g., missing library versions)","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.5194776000810745,"quality":0.24,"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.483Z","last_scraped_at":"2026-05-03T14:23:31.667Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":19786,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-ui5mcp-server","compare_url":"https://unfragile.ai/compare?artifact=npm-ui5mcp-server"}},"signature":"IEmNYFT2hmjYdxXiRDgKaaq5gOz9WYo/8++kb/1EvZB/luzyPl5mLCBMVAJAIAeKWyph/nmHPXJEVD8yj770DA==","signedAt":"2026-06-22T09:20:55.140Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-ui5mcp-server","artifact":"https://unfragile.ai/npm-ui5mcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=npm-ui5mcp-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"}}