FlyonUI MCP — Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

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

In der Praxis

flyonui-mcp.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren 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"
      ]
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

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

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

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

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

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

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

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

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

In context_servers hinzufügen. Zed lädt beim Speichern neu.

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

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: FlyonUI MCP

Scaffold a SaaS dashboard skeleton without writing Tailwind by hand

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

Wann einsetzen: You want a fast first version of a layout with consistent design tokens.

Voraussetzungen

Server/skill installed and authenticated — See repo README

Ablauf

Pick blocks

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

→ Names of matching blocks
Compose

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

→ One file with the four blocks stitched together

Ergebnis: A reasonable v0 dashboard layout in seconds.

Fallstricke

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.

Kombinieren mit: filesystem · 21st-dev-magic-mcp

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

flyonui-mcp + filesystem

Pair with filesystem for complementary capabilities

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

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.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
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

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: See provider docs for rate limits
Tokens pro Aufruf: Varies by tool
Kosten in €: See repo README for pricing details
Tipp: Cache tool results and avoid repeated identical calls.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: Use environment variables; never commit secrets

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

Fehlerbehebung

Häufige Fehler und Lösungen

component not found

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

Prüfen: list_components includes the name

classes don't render

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

Prüfen: Inspect element in the browser

Alternativen

FlyonUI MCP vs. andere

Alternative	Wann stattdessen	Kompromiss
21st-dev/magic-mcp	You want LLM-generated bespoke components	Less consistent; more flexible

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen