Everything in the atlas
Type
Domain: AI & Agents
Origin
Signals: Last 6 months
More: UI5
Group by: Capability
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.
Exercises building a Fiori elements app from Figma via MCP servers
TechEd 2025 workshop driving a Fiori elements app from Figma via MCP
Agent skill built from the Fiori Design Guidelines
Agent plugin on the SAP Design System and theming parameters
Knowledge about theming, not a theme build: nothing here compiles a theme or deploys one, and it says nothing about a custom control's own parameters.
Agent skill generating a Joule Frontend Actions bridge for UI5 apps
Two agent skills for accessibility and styling of web components
Two skills, narrowly scoped: nothing here scaffolds an application or answers what a component's API is — that is [@ui5/webcomponents-mcp-server](artifact:ui5-webcomponents-mcp-server), which reads the same library's documentation.
UI5 plugins for coding agents
Guidance, not access: these are instructions handed to an agent, and what the agent can then read of your project comes from [@ui5/mcp-server](artifact:ui5-mcp-server) or the editor. A modernisation workflow that runs autonomously across a codebase is also a thing to point at a branch rather than at main.
Five MCP servers whose tools return a prebuilt UI
Neither the package manifest nor the repository tree declares a licence.
SAP's UI elements as standard custom elements
Not where the UI library itself is expected to bind data: the documentation leaves binding a component's content and events to the host framework. Not from a CDN script tag: the project publishes none, so it assumes a build step.
UI5 workshop adding Chrome's on-device AI APIs to a TypeScript app