Skip to content
Guides / Getting started

Introduction

Fabrials components, shims and components from other libraries.

Fabrials UI is the design system behind the Fabrials products, published as a shadcn registry. It gives an app three kinds of component, all installed as source you own:

  • Fabrials components. The controls Fabrials products use (from @fabrials/ui and @fabrials/ai-ui) and the WebMCP and MCP blocks for interfaces people and agents share.
  • Shims. shadcn primitives such as button, dialog or select, backed by the Fabrials controls. Code written for shadcn keeps working and looks like the rest of the app.
  • Components from other libraries. Open-source components from libraries such as Magic UI and Kibo UI, copied at a reviewed snapshot, with their license checked and their origin kept. See how a library gets in.

Start

Two protocols, one interface

WebMCP exposes functionality inside a browser page. A person and an agent use the same application state and business logic. The human interface remains fully usable without browser support.

MCP connects a client to a server that advertises tools, resources and prompts. The components here let you connect, inspect those capabilities, and run tools with visible results.

These integrations have separate providers. Visual components accept props and callbacks, so you can also use them with your own state management or transport.

The foundation

React 19, TypeScript, Tailwind CSS 4, Base UI and the official MCP TypeScript SDK v2. Fabrials components are MIT licensed; components from other libraries keep their own permissive license, printed at the top of every file. Nothing you install calls a Fabrials service.