- Accordion
- Attachment
- Avatar
- Badge
- Breadcrumb
- Button
- Button Group
- Card
- Checkbox
- Code Block
- Collapsible
- Dialog
- Dropdown Menu
- Empty
- Field
- Hover Card
- Input
- Input Group
- Input OTP
- Item
- Label
- Marker
- Message
- Number Flow
- Pagination
- Popover
- Progress
- Radio Group
- Select
- Slider
- Sonner
- Spinner
- Switch
- Tooltip
- Separator
- Sheet
- Tabs
- Textarea
- Toggle
- Toggle Group
- Trace
npx -y @frakment/mcp. No install, no config file, just a working MCP server
on stdio.
Frakment ships an MCP server that exposes the registry as tools. Agents call the tools instead of scraping HTML or writing custom HTTP glue.
Quick start
$ bunx --bun -y @frakment/mcp$ npx -y @frakment/mcp$ pnpm dlx -y @frakment/mcp$ yarn dlx -y @frakment/mcp
$ bun add --save-dev @frakment/mcp npx @frakment/mcp$ npm install --save-dev @frakment/mcp npx @frakment/mcp$ pnpm add --save-dev @frakment/mcp npx @frakment/mcp$ yarn add --save-dev @frakment/mcp npx @frakment/mcp
Tools at a glance
Tools
list_components
Returns every component with name and description.
Input: none
Output: text list of components.
view_component
Returns the full source of one component.
| Prop | Type | Default | Description |
|---|---|---|---|
name* | string | — | Component slug from /r/index.json. |
Output: markdown with file contents, npm dependencies, and registry dependencies.
search_components
Case-insensitive substring search across name and description.
| Prop | Type | Default | Description |
|---|---|---|---|
query* | string | — | Free-text search term. |
Output: matching components with descriptions.
get_install_command
Returns the exact CLI command.
| Prop | Type | Default | Description |
|---|---|---|---|
name* | string | — | Component slug. |
Output: npx frakment@latest add <name>
list_scenarios
Returns the built-in compositions available for common UI scenarios. No parameters.
Output: a list of scenario names with one-line descriptions.
compose
Returns the components, resolved dependencies, and install command for a scenario.
| Prop | Type | Default | Description |
|---|---|---|---|
scenario* | string | — | Scenario key from `list_scenarios`. |
Output: scenario name, description, components, install command, and a note about transitive dependencies.
Supported scenarios: chat, agent-timeline, code-output, login-form, settings-panel, empty-state, search-input, status-dashboard.
Client configuration
Frakment MCP speaks stdio. Launch it from any MCP client that spawns subprocesses.
Claude Desktop
Config lives at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, or %APPDATA%\Claude\claude_desktop_config.json on Windows.
{
"mcpServers": {
"frakment": {
"command": "npx",
"args": ["-y", "@frakment/mcp"]
}
}
}Cursor
Config lives at ~/.cursor/mcp.json:
{
"mcpServers": {
"frakment": {
"command": "npx",
"args": ["-y", "@frakment/mcp"]
}
}
}Generic stdio
Any client that spawns stdio processes:
$ bunx --bun @frakment/mcp$ npx @frakment/mcp$ pnpm dlx @frakment/mcp$ yarn dlx @frakment/mcp
Environment
| Prop | Type | Default | Description |
|---|---|---|---|
FRAKMENT_REGISTRY | string | https://www.arrafi.dev/frakment/r | Override the registry base URL. Useful for local dev against http://localhost:3000. |
Troubleshooting
The component name does not exist in the registry. Call list_components
first to get a valid slug.
The registry is unreachable. Check FRAKMENT_REGISTRY or your network. For
local dev, run FRAKMENT_REGISTRY=http://localhost:3000 npx @frakment/mcp.
Verify the client config JSON parses, and that npx -y @frakment/mcp runs
from a terminal without errors.
Source
The MCP server lives in the mcp/ directory of the Frakment repo. It is a thin wrapper over the registry JSON with no interpretation logic. Browse the source on GitHub.