OrganisationSAP
UI5
Capabilities
Provides
Agent access to your codeUI5Agent access to your codeLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from [MCP servers](capability:mcp-servers), which is a protocol adapter on your own running service, and from [agent guidance](capability:agent-guidance), which is knowledge handed over as files rather than read from the thing itself.Agent guidanceUI5Agent guidancePackaged knowledge you hand a coding agent so it gets a framework right unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from [agent access to your code](capability:agent-code-access), where the agent reads the real project instead of being handed a file about it.AttachmentsUI5AttachmentsStoring a file somebody uploaded next to the record it belongs to, and getting it back out — where the bytes actually live, who may read them, and what the UI shows while they are being scanned.Build and dev-server toolingUI5Build and dev-server toolingServing an app locally and building it for deployment — proxying a backend, transpiling, bundling, and shaping the result for whatever will host it.DocumentationUI5DocumentationFinding the answer in what has already been written, and writing it where it has not — first-party documentation made searchable by something other than a person scrolling it, including by an agent, and a document of custom code produced from the code itself.LintingUI5LintingCatching in the editor what would otherwise be caught at deploy time, or not at all — problems in source code and models and in the project's configuration, found by rules rather than by review.LLM integrationUI5LLM integrationCalling a language model from application code with the tenant, destination and credential handling already solved instead using an SDK call with a hand-rolled key.ThemingUI5ThemingApplying a consistent visual identity across every control, including the parameters an app may read and the custom themes an organisation may build.Touch operationUI5Touch operationOperating an app with a finger, a stylus or a gloved hand on a tablet, kiosk or shop-floor terminal: targets large enough to hit, and input that does not assume a hardware keyboard. Distinct from responsive layout, which is about the width of the screen rather than what touches it.TypeScript supportUI5TypeScript supportWriting apps and libraries in TypeScript — the type definitions, the module syntax the loader expects, and the build step that gets from one to the other.UI5 testingUI5UI5 testingProving a UI still works — unit tests over controllers and formatters, integration tests that drive real controls, and end-to-end runs against a served app.Web Components interopUI5Web Components interopUsing standards-based custom elements inside an app, and the question of which control set an app should be built from at all, two concerns that are often answered as one.
Demonstrates
Build and dev-server toolingUI5Build and dev-server toolingServing an app locally and building it for deployment — proxying a backend, transpiling, bundling, and shaping the result for whatever will host it.LintingUI5LintingCatching in the editor what would otherwise be caught at deploy time, or not at all — problems in source code and models and in the project's configuration, found by rules rather than by review.UI5 testingUI5UI5 testingProving a UI still works — unit tests over controllers and formatters, integration tests that drive real controls, and end-to-end runs against a served app.
Entries
Group by8 of 8 entries
EntrySignals
Maintains
@ui5/linter@ui5/linterSAP's static analysis tool for UI5 projects: it scans JavaScript, TypeScript, XML, JSON and other files for deprecated APIs, global variables and possible CSP violations, and fixes part of them with --fix.sap official, ui5
Static analysis tool for UI5 projects
@ui5/mcp-server@ui5/mcp-serverSAP's MCP server for UI5 development: ten tools that scaffold an app or a card, read the project in front of the agent, and run the linter and the manifest validator against it.sap official, ui5
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.
MCP server for UI5 development with ten tools
@ui5/middleware-code-coverage@ui5/middleware-code-coverageUI5 CLI server middleware that instruments a project's JavaScript files with Istanbul as the dev server sends them, and generates the coverage report from the records the OpenUI5 QUnit tests send back.sap official, ui5
UI5 CLI middleware for Istanbul code coverage
@ui5/webcomponents@ui5/webcomponentsSAP's UI elements as standard custom elements, ui5-button among them, implementing SAP Fiori design and usable from plain HTML, React, Angular or Vue.sap official, ui5
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.
SAP's UI elements as standard custom elements
@ui5/webcomponents-mcp-server@ui5/webcomponents-mcp-serverFour tools that answer an agent's questions about UI5 Web Components from the framework's own documentation — component API, integration guides, and the docs themselves.sap official, ui5
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 answering questions on UI5 Web Components
UI5 Web Components agent skillsUI5 Web Components agent skillsTwo skills shipped inside the UI5 Web Components repository itself, under skills/: one for accessibility, covering ARIA and keyboard behaviour, and one for styling through shadow parts and custom properties.sap official, ui5
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.
Two agent skills for accessibility and styling of web components
UI5/plugins-coding-agentsUI5/plugins-coding-agentsUI5's own plugins for coding agents, three of them: everyday development, modernising a legacy project, and converting one to TypeScript, each installed into Claude Code or GitHub Copilot.sap official, ui5
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.
UI5 plugins for coding agents
Maintains: samples, sketches and references
@ui5/sample-app@ui5/sample-appAn OpenUI5 sample app set up with the UI5 CLI: ESLint, UI5 linter and UI5 Test Runner checks, a standard and a self-contained build, and a UI5 workspace for developing against local UI5 libraries.sap official, ui5
OpenUI5 sample app set up with the UI5 CLI
Details
History
- UI5/plugins-coding-agentscapability:agent-guidance widened the installs_into property to the UI5 door. Each plugin's README carries two install commands, one for the Claude Code marketplace and one for the Copilot one, so both are stated outright. The skills-only route names no client, which is why nothing further is recorded.
- UI5/plugins-coding-agentsThe old sentence named one marketplace and pointed at an installation guide without saying what it contains. The plugin READMEs read on 2026-10-15 state three routes, including a Copilot marketplace the entry did not mention, and state that the skills-only route leaves the UI5 MCP server to be installed by hand. That last fact changes what a reader gets, since the entry's own warning already turns on which server reads the project.
- @ui5/webcomponentsEvery page this entry rests on was read again, with the published package at 2.27.2 and Apache-2.0 on the npm registry record: the README's custom-elements sentence, the three component packages, the components API page, the UI Theme Designer page and the `sap-ui-theme` parameter, TypeScript definitions stable since 1.19.0, cozy as the default density with `data-ui5-compact-size` and `ui5-content-density-compact` as the compact markers, FileUploader's read-only `files` property, UploadCollection listing files before and after upload, and `@ui5/webcomponents-ai` still experimental and Horizon-only. Every claim holds as written, so no edge, flavor or capability changed and only the dates moved.
- @ui5/webcomponentsThe paragraph named the three component packages and the framework, which reads as the whole of what the project publishes. Its own package table lists `@ui5/webcomponents-theming`, `@ui5/webcomponents-localization` and the `SAP-icons`, `SAP-icons-TNT` and `BusinessSuiteInAppSymbols` collections beside them, and the npm record for 2.27.2 resolves all of them as dependencies of the main package, so what an application installs is wider than the sentence said.
- @ui5/mcp-serverEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; the description is written from the project's own README and documentation rather than from the catalogue's line about it.
- @ui5/webcomponents-mcp-serverEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; the description is written from the project's own README and documentation rather than from the catalogue's line about it.
- UI5 Web Components agent skillsEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; written from the repository's own README rather than from the catalogue's line about it. Hard rule 7: skills are indexed, never authored here. Entered as its own artifact rather than as a block on the library, which the corpus does not yet hold — the same shape fiori-mcp has inside SAP/open-ux-tools.
- UI5/plugins-coding-agentsEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; written from the repository's own README rather than from the catalogue's line about it. Hard rule 7: skills are indexed, never authored here.
- First entry seenDiscovered via Added by hand, sap-ai-mcp-servers.
Profile
For your agent
- Ref
actor:ui5- JSON
- /actors/ui5.json
- MCP
- Connecting an agent