UI5 Web Components for React MCP
Official MCP server for UI5 Web Components for React: component APIs, documentation and Fiori app templates for the agent
- 544 ★ on the repository
- Last commit
- Apache-2.0
Minimal access
Why this level
- The server reads only bundled documentation and does not touch your code, data or the network
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/ui5-web-components-for-react-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The server reads only bundled documentation and does not touch your code, data or the network
This is third-party code. Review the repository files before installing.
What it does
UI5 Web Components for React is an implementation of UI5 components for React that is compliant with the SAP Fiori user experience. The `@ui5/webcomponents-react-mcp` package gives an agent a reference for this library: component APIs, documentation and app templates. The server is local and needs no network: documentation and API data are already bundled into the package for a specific release. Five tools cover different tasks. `create_app` scaffolds an app from an official template (Vite with TypeScript, Next.js App Router or Pages Router) and returns setup steps through `degit`. `list_components` lists components by category and package. `get_component_api` returns props with types, events, ref methods, CSS parts for shadow DOM and subtypes. `get_documentation` searches by section and keyword: styling, i18n, SSR, slots, accessibility. `get_public_utils` describes utilities from the base package. There is also an `llms.txt` resource with an index.
Who it is for. Frontend developers building SAP Fiori-style interfaces in React who want the agent to stop inventing component props.
Good fit when
- The agent picks AnalyticalTable props and events from the current API instead of from memory
- A new project with UI5 components is created from a Vite or Next.js template with one command
- You need to understand how slots and styling through CSS `::part()` work in shadow DOM
- The project pins a specific library version and the reference must match it
Not a fit when
- The interface uses another component library: the server knows only UI5 for React
- You need to operate an SAP application or backend data: the server is a component reference and calls nothing in a system
- The library version in the project is older than 2.21.3: the server appeared in that version
Example request
Show the API of the AnalyticalTable component: props, events and how to define columns, then create an example pageMCP
- Transport
- stdio, http
- Authentication
- not required
Limitations
The server is available from `@ui5/webcomponents-react` 2.21.3 and shares the library's version number: it bundles the documentation and API of that release, so after upgrading the library you update the pinned server version too. To pin it in a project use `npx @ui5/webcomponents-react-mcp@$(node -p "require('@ui5/webcomponents-react/package.json').version")`, which needs the library in `node_modules`. The charts package `@ui5/webcomponents-react-charts` is marked deprecated. HTTP mode starts with the `--http` flag, listens on `localhost:7427` and runs statelessly.
How to disable. Remove the server from the client config, for example `claude mcp remove ui5-wcr`. The package is fetched through `npx` and leaves no separate files.
FAQ
How do I connect the UI5 MCP server to Claude Code?
Run `claude mcp add ui5-wcr -- npx @ui5/webcomponents-react-mcp@latest`. For VS Code and Cursor add a `ui5-wcr` server to `.vscode/mcp.json` with the `npx` command and the argument `@ui5/webcomponents-react-mcp@latest`.
Should I pin the server version?
It is advisable: the server bundles the documentation of a specific release, and pinning to the library version gives a reference that matches your code. Add `@<version>` after the package name.
Is internet required?
No, documentation is read from local package files. The network is needed only to download the package through `npx`.
Which templates does create_app produce?
Vite with TypeScript, Next.js App Router and Next.js Pages Router. The tool returns step-by-step setup instructions through `degit`.
How do I run the server over HTTP?
With `npx @ui5/webcomponents-react-mcp@latest --http`. It listens on http://localhost:7427/mcp and the port is changed with the `--port` flag or the `PORT` variable.
Discussion
No questions or reviews yet.
Related
MCP serversUI5 MCP Server helps an agent scaffold SAP UI5 apps, validate the manifest and code with a linter and read the current API.
SAP's MCP server gives an agent a catalog of 1,000 Fundamental NGX components with API data, examples, comparisons and setup guides
MCP server of a React component library for agent interfaces: the agent finds a component and adds it to your project
Shadcn UI MCP Server
Shadcn UI v4 MCP Server
An MCP server that gives the agent shadcn/ui component source, demos and blocks for React, Svelte, Vue and React Native
The hosted Watermelon UI MCP searches free React and Tailwind components, blocks and dashboards and returns source code.
MCP server for the UI Beats catalog of animated React components: search, props, source code and install command for an agent
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| UI5 Web Components for React MCP (this card) | yes | not required | 544 | |
| Ant Design Components MCP | no | not required | 247 | documentation and API of Ant Design components rather than UI5 and SAP Fiori |
| Context7 | yes | API key | 64,735 | a general documentation service for thousands of libraries rather than a reference for a specific UI5 release |
README in short
The repository's main text lists the library packages, requirements (React 18 or higher, Node.js LTS, TypeScript 4.7 or newer) and installation. The server is described in `packages/mcp-server/README.md`: setup, version pinning, two transports and five tools.