Everything in UI5
Type: 3
Domain
Origin
Signals
More
Group by: Capability
Distributed through
Generates
Run with
MCP server for creating and editing Fiori applications
MCP server for UI5 development with ten tools
It reads a UI5 project and the framework's own documentation, not a running system or a backend: a question about the service behind the app is answered somewhere else. Node.js v20.17 or v22.9 and above.
Hosted MCP server of developers.sap.com tutorials and missions
CDS plugin and UI5 controls for AI text features via SAP AI Core
It is text processing, not an agent: there is no tool calling, no retrieval and no conversation. It needs SAP AI Core, and the backend half needs [@sap-ai-sdk/orchestration](artifact:sap-ai-sdk-orchestration) installed alongside it — an optional peer, so a frontend-only install stays lean.
Yeoman generator for Application Frontend config in UI5 libraries
It targets the Application Frontend service only — not the HTML5 application repository — fixes authentication to IAS, and always creates new service instances, so reusing existing ones means editing the generated `mta.yaml` afterwards. Version 0.1.0 is the only release.
npm-init wrapper for the Easy-UI5 Yeoman generator
npm initializer adding wdi5 testing to an existing UI5 app
Yeoman meta-generator for scaffolding UI5 projects
Yeoman generator for UI5 tooling-extension projects
Release and repository quiet for 33 months.
Easy-UI5 generator scaffolding a new UI5 application
Yeoman generator for UI5 custom controls distributed via npm
No published releases; repository quiet for 67 months.
Easy-UI5 generator scaffolding a new UI5 library
Yeoman generator for UI5 libraries wrapping UI5 Web Components
No published releases; repository quiet for 35 months.
Yeoman generator for UI5 projects holding several applications
Not for a single-application project with no deployment configuration: for that the README points to [generator-ui5-app](artifact:ui5-community-generator-ui5-app) instead.
Yeoman generator for a UI5 app that loads a React app
Quiet Release and repository quiet for 39 months.
Functional boundary The scaffold is JavaScript and not TypeScript, and `react-router-dom` and UI5 Web Components are not included; its README leaves both for the project to add.
Easy-UI5 generator scaffolding a TypeScript UI5 application
Generator for a TypeScript UI5 FlexibleColumnLayout app on OData
Easy-UI5 generator scaffolding a TypeScript UI5 library
Yeoman generator scaffolding wdi5 test configuration into a UI5 app
No published releases; repository quiet for 27 months.
Command line generator of UI5 custom controls from html
Release and repository quiet for 29 months.
MCP server for UI5 development with ten tools
It reads a UI5 project and the framework's own documentation, not a running system or a backend: a question about the service behind the app is answered somewhere else. Node.js v20.17 or v22.9 and above.
Chrome extension generating OPA5 or wdi5 tests from recorded journeys
Command line generator of UI5 custom controls from html
Release and repository quiet for 29 months.
Easy-UI5 generator scaffolding a Fiori Launchpad plugin
Easy-UI5 generator for a TypeScript Fiori launchpad plugin
MCP server answering questions on UI5 Web Components
It answers from documentation and never opens your project, so it cannot tell you whether the component you are asking about is the one your application already uses. Node.js v20.17 or v22.9 and above; on Windows the command needs a `cmd /c` prefix.
MCP server searching seventeen SAP documentation repositories
It reads documentation, never a system: nothing in it opens a package.json, a CDS model or an ABAP client, so a question about what your own project does has to be answered elsewhere. The offline half is only as fresh as the submodules the last build pinned, and the index answers where something is written down rather than which of two packages fits a task.
Playback-only SAP Companion (Help4) workarea served from CAP
Not behind a managed approuter: SAP Build Work Zone does not expose the `/$companion/**` routes, so Companion never reaches CAP, and the README names managed approuter and Work Zone as out of scope for v1. Not where help has to be authored in a browser, since the editor, the producer and writes are absent and content lives in files the plugin compiles.