FlyonUI MCP — Install & Live Demo

Why use it

Key features

Catalog of FlyonUI components (alerts, cards, forms, navbars, dashboards)
Returns ready-to-paste HTML + Tailwind classes
Variant control (size, theme, color)
Block composition — full sections, not just primitives
Works with any frontend framework that consumes Tailwind

Live Demo

What it looks like in practice

flyonui-mcp.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "flyonui-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@flyonui/mcp"
      ]
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "flyonui-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@flyonui/mcp"
      ]
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "flyonui-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@flyonui/mcp"
      ]
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "flyonui-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@flyonui/mcp"
      ]
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "flyonui-mcp",
      "command": "npx",
      "args": [
        "-y",
        "@flyonui/mcp"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "flyonui-mcp": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@flyonui/mcp"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add flyonui-mcp -- npx -y @flyonui/mcp

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use FlyonUI MCP

Scaffold a SaaS dashboard skeleton without writing Tailwind by hand

👤 Frontend devs starting a new project ⏱ ~15 min intermediate

When to use: You want a fast first version of a layout with consistent design tokens.

Prerequisites

Server/skill installed and authenticated — See repo README

Flow

Pick blocks

List FlyonUI dashboard blocks. I want a sidebar, top nav, stats cards row, and a data table.✓ Copied

→ Names of matching blocks
Compose

Compose them into one HTML file. Use the slate theme.✓ Copied

→ One file with the four blocks stitched together

Outcome: A reasonable v0 dashboard layout in seconds.

Pitfalls

FlyonUI's class names track DaisyUI versions. If you mix with shadcn or vanilla Tailwind, components may visually clash. — FlyonUI's class names track DaisyUI versions. If you mix with shadcn or vanilla Tailwind, components may visually clash.

Combine with: filesystem · 21st-dev-magic-mcp

Combinations

Pair with other MCPs for X10 leverage

flyonui-mcp + filesystem

Pair with filesystem for complementary capabilities

Use this server together with filesystem to complete a multi-step task.✓ Copied

flyonui-mcp + 21st-dev-magic-mcp

Pair with 21st-dev-magic-mcp for complementary capabilities

Use this server together with 21st-dev-magic-mcp to complete a multi-step task.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
list_components	category	Browse available components	free
get_component	name, variant	Fetch one component as code	free
get_block	name	Get a full section (hero, pricing, etc.)	free

Cost & Limits

What this costs to run

API quota: See provider docs for rate limits
Tokens per call: Varies by tool
Monetary: See repo README for pricing details
Tip: Cache tool results and avoid repeated identical calls.

Security

Permissions, secrets, blast radius

Credential storage: Use environment variables; never commit secrets

Data egress: Tool calls go to the provider's API as documented

Troubleshooting

Common errors and fixes

component not found

Use list_components to confirm the exact name (e.g. 'card-bordered' vs 'card').

Verify: list_components includes the name

classes don't render

Make sure your Tailwind config includes DaisyUI as a plugin and FlyonUI's class paths.

Verify: Inspect element in the browser

Alternatives

FlyonUI MCP vs others

Alternative	When to use it instead	Tradeoff
21st-dev/magic-mcp	You want LLM-generated bespoke components	Less consistent; more flexible

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills