Webcomponents React Mcp Server

io.github.UI5Published by GitHub account UI5v2.28.2Updated Oct 29, 2026

MCP server for UI5 Web Components for React - Developer documentation and API assistance

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local MCP server that gives an AI assistant UI5 Web Components for React documentation, component APIs and utilities, plus app scaffolding.

What you can do
  • Scaffold new apps from official Vite, Next.js App Router and Next.js Pages Router templates with step-by-step setup instructions
  • Browse components by category or package, with descriptions and import examples
  • Read full component API docs: props with TypeScript types and defaults, event detail fields, ref methods, CSS part selectors and sub-types
  • Search and read bundled documentation and knowledge base sections, with line-range support for long pages
  • Look up public utilities from the base package, such as device detection, i18n and viewport hooks, and theming parameters
When to use it
Useful when building or maintaining a React front end with UI5 Web Components for React and you want the assistant to answer component, styling, slot or API questions from version-matched local docs instead of guessing. Also handy for starting a new project from an official template.
Requirements
Runs locally as a Node.js process, typically launched with npx from the npm package; Node.js is needed. No accounts, API keys or environment variables are declared. Default transport is stdio; an optional HTTP mode listens on localhost only, with the port set by a flag or the PORT variable. Documentation is bundled, so no network access is needed at query time.
Before you install
The create_app tool returns scaffolding instructions rather than writing files itself, but following them runs commands such as degit in your project. Pin the server version to match the installed library version, since it bundles docs for one release and must be updated when the library is. HTTP mode is stateless and localhost-only; keep it that way rather than exposing the port.

Installation

In SourceWeft

  1. Open Webcomponents React Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

UI5 Web Components for React MCP Server

MCP server providing development assistance and API documentation for UI5 Web Components for React.

What is this?

This MCP server gives AI assistants direct access to UI5 Web Components for React documentation, component APIs, and utility information. It helps developers get accurate, up-to-date information about the library without leaving their IDE.

Setup

This server is available in the MCP Registry, which allows compatible clients to install it directly.

Claude Code

bash
claude mcp add ui5-wcr -- npx @ui5/webcomponents-react-mcp@latest

VS Code / Cursor

Add to .vscode/mcp.json:

json
{  "servers": {    "ui5-wcr": {      "command": "npx",      "args": ["@ui5/webcomponents-react-mcp@latest"]    }  }}

Pinning a Specific Version

The MCP server is available since @ui5/[email protected]. It shares the same version number and bundles documentation and API data for that specific release. Pinning the version to match your project ensures the AI assistant provides accurate information for the components and APIs you are actually using.

Append @<version> to install a specific version. Note that after updating @ui5/webcomponents-react, you need to update the pinned MCP server version accordingly.

bash

To match the version of @ui5/webcomponents-react installed in your project, run from the project root:

This requires @ui5/webcomponents-react to be installed in the project's node_modules.

bash
npx @ui5/webcomponents-react-mcp@$(node -p "require('@ui5/webcomponents-react/package.json').version")

Transport

The server supports two transports. Both run locally on the developer's machine.

stdio (default)

Used by the Setup configurations above. The client spawns the server as a subprocess and communicates over stdin/stdout. No flags are required.

HTTP (Streamable HTTP)

Some MCP clients connect over HTTP instead. Start the server with the --http flag to enable the Streamable HTTP transport:

bash
npx @ui5/webcomponents-react-mcp@latest --http

The server listens on http://localhost:7427/mcp. Change the port with --port (or the PORT environment variable):

bash
npx @ui5/webcomponents-react-mcp@latest --http --port 7500

It runs statelessly and binds to localhost only — reachable over a local HTTP port, but otherwise the same local-only, version-pinned server as the stdio mode. Point your HTTP-based client at the endpoint:

json
{  "servers": {    "ui5-wcr": {      "url": "http://localhost:7427/mcp"    }  }}

Features

Tools

  1. create_app - Scaffold a new application from an official template

    • Vite (TypeScript), Next.js App Router, Next.js Pages Router
    • Returns step-by-step setup instructions using degit
  2. list_components - Browse all available components

    • Filter by category (Data Display, Layouts & Floorplans, Inputs, Modals & Popovers, User Feedback, Charts, AI Components, Web Components)
    • Filter by package (@ui5/webcomponents-react, @ui5/webcomponents-react-charts, @ui5/webcomponents-ai-react)
    • Includes descriptions and import examples
  3. get_component_api - Full component API documentation

    • Props with TypeScript types, descriptions, and defaults
    • Event detail parameters (fields available on e.detail)
    • Ref methods and return types
    • CSS ::part() selectors for shadow DOM styling
    • Sub-type documentation for complex props (e.g. AnalyticalTable column definitions)
    • Upstream documentation links for components with complex behavioral logic
    • Case-insensitive component name matching
    • Returns structured JSON output
  4. get_documentation - Documentation, guides, and knowledge base

    • Browse by section name or search by keyword across all docs
    • Getting Started, Knowledge Base (styling, i18n, SSR, slots, FAQ, accessibility, and more), project templates
    • Full content read from bundled local files (no network required)
    • Line-range support (startLine/endLine) for large documents
  5. get_public_utils - Public utilities from @ui5/webcomponents-react-base

    • Device API (device detection, responsive breakpoints, resize/orientation handlers)
    • useI18nBundle hook (internationalization)
    • useViewportRange hook (responsive breakpoint detection)
    • ThemingParameters (CSS variables in JavaScript)

Resources

  • llms.txt - LLM-friendly documentation index with scope, key concepts, and quick-reference links

Usage

Once configured, your AI assistant will have access to the tools. You can ask questions like:

Create:

  • "Create a new Vite app with UI5 Web Components for React"
  • "Scaffold a Next.js app with a simple dashboard"

Documentation:

  • "How do I style components?"
  • "How do slots work?"

Components:

  • "List all available components"
  • "Show me chart components"
  • "What layout components are available?"
  • "Show me the API for AnalyticalTable"
  • "How do I use the DynamicPage component?"

Contributing

See CONTRIBUTING.md for development setup, scripts, architecture, and build pipeline details.

Source: packages/mcp-server/README.md at commit 7a09746

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

7
  1. v2.28.2LatestOct 29, 2026
  2. v2.28.1Oct 22, 2026
  3. v2.28.0Oct 22, 2026
  4. v2.27.3Oct 9, 2026
  5. v2.27.2Sep 29, 2026
  6. v2.27.1Sep 25, 2026
  7. v2.26.3Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts