Combien d'outils expose io.github.UI5/webcomponents-react-mcp-server ?

io.github.UI5/webcomponents-react-mcp-server expose 5 outil(s). Le coût de contexte pour les charger tous est d'environ 1916 tokens (coût unique au chargement, pas par appel).

accueil / serveurs / Dev & Code / io.github.UI5/webcomponents-react-mcp-server

io.github.UI5/webcomponents-react-mcp-server

serveur MCP (Model Context Protocol)

▸ Dev & Code

[ Vérifié ]

Verdict MCP Hub
Aucun comportement malveillant détecté au test comportemental.

npmType / transport

directAccès

~1916 tokensCoût de contexte

5Outils

Est-ce que io.github.UI5/webcomponents-react-mcp-server est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.UI5/webcomponents-react-mcp-server » est classé « Vérifié ». Aucun comportement malveillant détecté au test comportemental. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Versions auditées & empreintes

Vérifiez la version que vous utilisez : son empreinte doit correspondre à celle listée ici — sinon vous n'utilisez pas la version auditée.

[ Vérifié ] v2.27.3 audité le 2026-10-21

sha512-u54JPOd8cCpX8wgcs1BjhA0lLujpBQALyiXdzar5QjdAWXDaXHRPIn7jFTPyhke4QglwIwihvucMUL8GrNV47Q==

npm view @ui5/webcomponents-react-mcp@2.27.3 dist.integrity

[ Vérifié ] v2.27.2 audité le 2026-10-17

sha512-rtUW3fYvL8AJuTC9cbv3I2c/ZqghasoEByex5a+pbpDf9wb65BwSwr8d9GdepIZy3PAnoKyc9EJWDReSsg2LAg==

npm view @ui5/webcomponents-react-mcp@2.27.2 dist.integrity

Vous utilisez ce serveur ? Suivez-le (créez un compte) pour être alerté dès qu'une nouvelle version paraît ou que le verdict change.

Les 5 outils

create_app≈ 288 tokens
Get scaffolding instructions for a new UI5 Web Components for React application from an official template. WHEN TO USE: The user wants to create a new app, project, or starter using UI5 Web Components for React. WORKFLOW: Call this tool to get the template setup instructions, then execute them. Available templates: - `nextjs-app` — Next.js (App Router) - `nextjs-pages` — Next.js (Pages Router) - `vite-ts` — Vite.js - `preact-vite-ts` — Preact (Vite.js) - `preact-ssr-ts` — Preact (Vite.js + SSR) EXAMPLE INPUT: { "template": "vite-ts", "appName": "my-app" } EXAMPLE INPUT: { "template": "nextjs-app", "appName": "my-dashboard" }
Paramètres, retour & exemple (2)
Paramètres
- appName · string · requis
  Name for the new application directory
- template · string · requis · nextjs-app | nextjs-pages | vite-ts | preact-vite-ts | preact-ssr-ts
  Template to use. Available: nextjs-app, nextjs-pages, vite-ts, preact-vite-ts, preact-ssr-ts
Exemple d'appel
```
{"name": "create_app", "arguments": {"appName": "texte", "template": "nextjs-app"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_component_api≈ 309 tokens
Get comprehensive API documentation for a UI5 Web Components React component including props, ref methods, types, event detail parameters, and CSS parts for shadow DOM styling. WHEN TO USE: You need exact prop names, types, default values, method signatures, event detail fields, or CSS part selectors for a specific component. DO NOT USE FOR: General guidance on styling, events, or architecture — use get_documentation instead. To discover component names — use list_components first. WORKFLOW: Use list_components to find the correct component name, then this tool for full API details. LIMITS: Returns data for one component per call. Returns all props and methods for that component. EXAMPLE INPUT: { "componentName": "Dialog" } **Output Format (JSON):** ```typescript { package: string,
Paramètres, retour & exemple (1)
Paramètres
- componentName · string · requis
  Component name (e.g., "Button", "AnalyticalTable"). Case-insensitive. Must match a component from @ui5/webcomponents-react, @ui5/webcomponents-react-charts, or @ui5/webcomponents-ai-react.
Exemple d'appel
```
{"name": "get_component_api", "arguments": {"componentName": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_documentation≈ 741 tokens
Retrieve UI5 Web Components for React documentation, guides, and knowledge base articles. Documentation is bundled locally for instant offline access. WHEN TO USE: You need guidance on how to use the library — setup, styling, event handling, SSR, slots, i18n. DO NOT USE FOR: Looking up specific component props or methods — use get_component_api instead. For public utilities/hooks from @ui5/webcomponents-react-base — use get_public_utils. WORKFLOW: Call without parameters to see all available sections. Use section parameter for direct access, query for search. LIMITS: When fetchContent is true, full content is returned for at most 3 matching sections to control output size. EXAMPLE INPUT: { "section": "Knowledge Base > Styling", "fetchContent": true } EXAMPLE INPUT: { "query": "i18n", "fe
Paramètres, retour & exemple (5)
Paramètres
- query · string · optionnel
  Free-form search query to find relevant documentation. Searches across section names, descriptions, tags, and content topics. Examples: "styling", "migration", "i18n", "ssr", "slots", "forms". Use this for exploratory search when you're not sure which section you need. Mutually exclusive with section parameter.
- endLine · integer · optionnel
  End line number (1-based, inclusive) for reading a portion of the documentation. Requires fetchContent: true. If omitted with startLine, reads to end of file.
- section · string · optionnel · Getting Started | Project Templates & Examples | Knowledge Base > Bring Your Own Web Components | Knowledge Base > Common CSS | Knowledge Base > FAQ | Knowledge Base > Handling Slots | Knowledge Base > IDs via dataset | Knowledge Base > Internationalization
  Specific documentation section to retrieve by exact name. Use this for direct access when you know which section you need. Examples: "Getting Started", "Migration Guide", "Knowledge Base > Styling", "Knowledge Base > Internationalization". Mutually exclusive with query parameter.
- startLine · integer · optionnel
  Start line number (1-based, inclusive) for reading a portion of the documentation. Requires fetchContent: true. Useful for large documents like the Change Log or Migration Guide.
- fetchContent · boolean · optionnel
  Whether to include the full documentation markdown content. Set to true to retrieve full documentation text in addition to metadata. Content is read from bundled local files (no network required). Useful when you need detailed information beyond the summary.
Exemple d'appel
```
{"name": "get_documentation", "arguments": {"query": "texte", "endLine": 1, "section": "Getting Started", "startLine": 1, "fetchContent": true}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_public_utils≈ 280 tokens
Get documentation for public utilities and hooks from @ui5/webcomponents-react-base. Covers Device API, ThemingParameters, useI18nBundle, useViewportRange, and withWebComponent. WHEN TO USE: You need to use device detection, theme-aware CSS variables in JS, internationalization hooks, responsive breakpoints, or wrap your own custom web components. DO NOT USE FOR: Looking up component props — use get_component_api. For general styling guidance — use get_documentation with section "Knowledge Base > Styling". LIMITS: Returns documentation for one utility per call, or an overview of all 5 utilities. EXAMPLE INPUT: { "name": "ThemingParameters" } EXAMPLE INPUT: { "name": "withWebComponent" } EXAMPLE INPUT: {} (returns overview of all utilities)
Paramètres, retour & exemple (1)
Paramètres
- name · string · optionnel · Device | ThemingParameters | useI18nBundle | useViewportRange | withWebComponent
  Specific utility/hook name. Omit to see all available utilities.
Exemple d'appel
```
{"name": "get_public_utils", "arguments": {"name": "Device"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
list_components≈ 328 tokens
Browse all 217 available UI5 Web Components for React components across 4 packages with descriptions, categories, and import statements. WHEN TO USE: You need to discover which components exist, find the right component for a use case, or verify a component name before calling get_component_api. DO NOT USE FOR: Getting detailed props or methods — use get_component_api after finding the component name here. LIMITS: Returns all matching components at once (up to 217). Filter by category or package to reduce output size. EXAMPLE INPUT: { "category": "Inputs" } EXAMPLE INPUT: { "package": "@ui5/webcomponents-react-charts" } EXAMPLE INPUT: {} (returns all components)
Paramètres, retour & exemple (2)
Paramètres
- package · string · optionnel · @ui5/webcomponents-react | @ui5/webcomponents-react-charts | @ui5/webcomponents-ai-react
  Filter components by npm package name. Omit to show all packages.
- category · string · optionnel · Data Display | Layouts & Floorplans | Inputs | Modals & Popovers | User Feedback | Charts | AI Components | Web Components (Wrapped)
  Filter components by category. Omit to show all categories.
Exemple d'appel
```
{"name": "list_components", "arguments": {"package": "@ui5/webcomponents-react", "category": "Data Display"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```

Badge pour votre README

Ce serveur a passé le pentest comportemental. Le badge porte son nom et renvoie à cette fiche — la preuve, c'est la fiche (verdict live qu'on contrôle), pas l'image.

Markdown

[![Vérifié par MCP Hub](https://dokore.fr/badge/io.github.ui5--webcomponents-react-mcp-server.svg)](https://dokore.fr/serveur/io.github.ui5--webcomponents-react-mcp-server)

HTML

<a href="https://dokore.fr/serveur/io.github.ui5--webcomponents-react-mcp-server"><img src="https://dokore.fr/badge/io.github.ui5--webcomponents-react-mcp-server.svg" alt="Vérifié par MCP Hub" height="20"></a>

Réévalué en continu : si le comportement change, le verdict tombe et le badge disparaît. Un badge qui ne pointe pas vers une fiche dokore.fr ne prouve rien. Comment ça marche

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

@ui5/webcomponents-react-mcp@2.27.3