MCP server

MCP UI Components Server by Flowbite

The MCP UI Components server by Flowbite renders interactive widgets, such as charts, tables and selection prompts, inside a chat client instead of raw JSON text.

Run
git clone https://github.com/themesberg/mcp-ui-components.git
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the MCP UI Components server?

MCP UI Components is an open-source Express and React server that gives AI chat clients widget-based output: basic text, radio and checkbox groups, a line chart, an e-commerce product list, a QR code, and a data table. It is built on the Flowbite UI framework and the SkyBridge framework, and it exposes an MCP endpoint a client reaches through a tunnel.

MCP UI Components is an open-source library of UI widgets for MCP applications, built on the Flowbite UI framework together with the SkyBridge framework. Instead of a chat client showing a tool's raw JSON result, the server renders that result as an interactive widget.

It ships as an Express server with an MCP endpoint plus a React application for the widgets themselves, so the same project both serves the protocol and renders what a client displays.

What it changes in your workflow

  • A tool result that would otherwise print as raw JSON instead renders as a line chart, a data table, or a selection prompt the person can interact with.
  • Radio and checkbox group widgets turn a decision point in a conversation into a clickable prompt instead of a typed answer.
  • The project supports several predefined themes, including default, minimal, enterprise, playful and mono, so the rendered widgets can match a brand's look.
  • Because the server runs locally and is reached through a tunnel, a developer can iterate on a new widget and see it rendered in a real client quickly.

Setup at a glance

MCP UI Components server
Local startnpm install, then npm run dev on port 3000
Remote reachA tunnel such as ngrok, with /mcp appended to the forwarding address
Node versionNode.js 24 or newer
Clients namedChatGPT, Claude Web, Claude Code, Gemini CLI, Cursor, VS Code, Mistral AI, Windsurf, Codex

Who it is for

Best for

  • Teams building an MCP app that wants its tool output to render as a widget instead of plain text or JSON.
  • Prototyping a selection prompt, chart or table widget before building a custom one from scratch.
  • Developers already using Flowbite and Tailwind who want matching widgets inside a chat client.

Not for

  • If the deliverable is production React chart code for a real web app rather than a chat widget, the Data Visualization Mastery skill picks from over 50 chart types with real library code.
  • When only visualization design guidance is needed rather than a rendered widget, Generative UI MCP loads chart and diagram design rules on demand.
  • Go with a WordPress-page route when the task is editing a live Elementor page rather than a chat widget, MCP Abilities Elementor inspects and edits a page's own widgets instead.
  • Choose a hosted design-system server when charts and components should come from Carbon rather than a chat widget set, Carbon MCP gives direct access to Carbon's own charts and components.

Use it with UiChemy

This server renders widgets inside a chat client, a different surface from a web page. UiChemy's Composer builds the WordPress page itself inside Elementor or Gutenberg, so the two cover separate parts of a product's interface.