UI5 Web Components for React MCP Server

What it does

This server answers questions about UI5 Web Components for React, the React wrapper around SAP's UI5 Web Components. It is published from the library's own repository by the UI5 team, and each release carries the same version number as the library and bundles that release's documentation and API data. A coding assistant can list the components (filtered by category or by package, including the charts and AI component packages), pull the full API of one component (props with types and defaults, event detail fields, ref methods, CSS ::part selectors), read the guides and knowledge-base pages, look up the helper utilities from @ui5/webcomponents-react-base, and get setup steps for a new Vite or Next.js project from an official template.

The docs are read from files shipped inside the package, so lookups need no network access. Pinning the server version to the library version in your project keeps answers matched to the APIs you actually use.

It speaks stdio by default. With --http, or with the environment variable MCP_TRANSPORT=http (which the README does not mention, see src/index.ts), it serves Streamable HTTP at http://localhost:7427/mcp; the port changes with --port or PORT. In HTTP mode the listener is fixed to 127.0.0.1 in the code and requests with a different Host header or a foreign browser Origin are refused (src/http.ts). It also offers an llms.txt resource as a documentation index.

What it needs

Node.js with npx. Nothing else: no account, key or network access to the docs. To pin the server to the library version in your project with the README's one-line command, @ui5/webcomponents-react must be installed in that project's node_modules. The server exists from library version 2.21.3 onward.

Limits

It covers only UI5 Web Components for React and the packages around it; it does not inspect or edit your project's code. create_app returns setup instructions (using degit) rather than creating files itself. Answers match the bundled version: an unpinned @latest may describe newer APIs than your project uses, and a pinned version must be bumped by hand after you update the library. HTTP mode cannot be reached from other machines, as it always binds to 127.0.0.1.

Who it suits

React developers building SAP Fiori-style interfaces with UI5 Web Components for React who want their assistant to quote the real props, events and styling hooks of the version they use instead of guessing. It runs locally, needs no sign-in and changes nothing, so it fits locked-down machines and offline work. It is not useful for other UI libraries, or for plain UI5 (non-React) projects beyond what the wrapper docs cover.