Flowbite Mcp

io.github.themesberg由 GitHub 账号 themesberg 发布v1.1.3更新于 Oct 24, 2026

MCP server to convert Figma designs to Flowbite UI components in Tailwind CSS

已验证STDIO仅桌面开发者工具媒体与设计

概览

AI 生成的概览

Flowbite 官方 MCP 服务器,让助手访问 Flowbite 的 Tailwind CSS 组件文档、生成品牌主题,并把 Figma 设计转换为代码。

可以做什么
  • 查询 Flowbite 的 UI 组件、表单、排版与插件文档资源
  • 根据任意品牌十六进制颜色生成自定义主题文件
  • 把 Figma 节点链接转换为 Flowbite 组件代码
  • 以 stdio 本地运行,或以 HTTP 模式配合 Docker 与健康检查部署
适用场景
适合在使用 Flowbite 构建 Tailwind CSS 界面时,让助手获取准确的组件代码与文档、生成品牌主题,或把 Figma 设计稿转成代码。
运行要求
通过 npx 或 Node.js 本地运行(npm 包 flowbite-mcp),通常在 Claude Desktop、Cursor、Windsurf 等客户端中配置。Figma 转代码工具需要 Figma 个人访问令牌,通过环境变量 FIGMA_ACCESS_TOKEN 提供。HTTP 模式可选使用 MCP_TRANSPORT_MODE、MCP_PORT、MCP_HOST 和 MCP_CORS_ORIGINS。
安装前请注意
Figma 工具需要 Figma API 个人访问令牌(FIGMA_ACCESS_TOKEN),需写入客户端配置,应视为机密并尽量缩小权限范围。Figma 节点链接会发送给 Figma API。生成的代码与主题在用于项目前应先行检查。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Flowbite Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

[Flowbite - Tailwind CSS components]
Official MCP server for Flowbite to leverage AI for UI creation and theme generation

[Discord] [Total Downloads] [Latest Release] [License]

[Install MCP Server]

An MCP server that enables AI assistants to access the Flowbite library of Tailwind CSS components—including UI elements, forms, typography, and plugins—while offering an intelligent theme generator for creating custom branded designs within AI-driven development environments.

MCP Features

Tools:

  • 🎨 [NEW] Figma to code - Copy the Figma node url and generate code (video demo)
  • 🎯 Theme file generator - Create custom branded themes from any branded hex color

Resources:

Server:

  • 🌐 Dual transport support - Standard I/O (stdio) for CLI or HTTP Streamable for server deployments
  • ⚡ Production ready - Docker support with health checks and monitoring

Quickstart

Using NPX

The simplest way to use Flowbite MCP Server:

bash
npx flowbite-mcp

Environment variables

Currently you only need the Figma personal access token if you want to enable the Figma to code generation tool.

bash
// other options"env": {  "FIGMA_ACCESS_TOKEN": "YOUR_PERSONAL_FIGMA_ACCESS_TOKEN"}

You set this variable in your MCP client configuration file.

Integration examples

Use the following configuration examples to install the Flowbite MCP server in popular clients such as Cursor, Claude, Windsurf, and others.

Claude desktop

Update the claude_desktop_config.json file and add the following configuration:

json
{  "mcpServers": {    "flowbite": {      "command": "npx",      "args": ["-y", "flowbite-mcp"],      "env": {        "FIGMA_ACCESS_TOKEN": "YOUR_PERSONAL_FIGMA_ACCESS_TOKEN"      }    }  }}

Cursor editor

[Install MCP Server]

Update the mcp.json file and add the following configuration:

json
{  "mcpServers": {    "flowbite": {      "command": "npx",      "args": ["-y", "flowbite-mcp"],      "env": {        "FIGMA_ACCESS_TOKEN": "YOUR_PERSONAL_FIGMA_ACCESS_TOKEN"      }    }  }}

Windsurf editor

Update the mcp_config.json file and add the following configuration:

json
{  "mcpServers": {    "flowbite": {      "command": "npx",      "args": ["-y", "flowbite-mcp"],      "env": {        "FIGMA_ACCESS_TOKEN": "YOUR_PERSONAL_FIGMA_ACCESS_TOKEN"      }    }  }}

Glama.ai

[图片]

Local Transport Modes

Standard I/O (stdio)

The default mode for local development and CLI integrations:

bash
# Start in stdio mode (default)node build/index.js
{  "mcpServers": {    "flowbite": {      "command": "node",      "args": ["/path/to/flowbite-mcp/build/index.js"],      "env": {        "FIGMA_ACCESS_TOKEN": "YOUR_PERSONAL_FIGMA_ACCESS_TOKEN"      }    }  }}

Learn how to get the Figma personal access token to enable the Figma to code generation tool.

HTTP server

HTTP-based transport for production and multi-client scenarios:

bash
node build/index.js --mode http --port 3000

This will make the MCP server available at 'http://localhost:3000/mcp'.

Local development

bash
# Clone the repositorygit clone https://github.com/themesberg/flowbite-mcp.gitcd flowbite-mcp
# Install dependenciesnpm install
# Build the projectnpm run build
# Run in stdio mode (for Claude Desktop, Cursor)npm start
# Run inspectornpm run start inspector
# Run in HTTP server mode (for production/multi-client)MCP_TRANSPORT_MODE=http npm start

Production deployment (HTTP Mode)

For production servers with multiple clients:

bash
# Using npxnpx flowbite-mcp --mode http --port 3000
# Using Docker Composedocker-compose up -d
# Health checkcurl http://localhost:3000/health

Hosting variables

Configure the server behavior with these environment variables:

bash
# Transport mode: stdio (default) or httpMCP_TRANSPORT_MODE=http
# Server port for HTTP modeMCP_PORT=3000
# Host binding for HTTP modeMCP_HOST=0.0.0.0
# CORS origins (comma-separated)MCP_CORS_ORIGINS=http://localhost:3000,https://myapp.com

Docker Configuration

The project includes a production-ready Docker setup with multi-stage builds for optimal performance.

Quickstart with Docker

bash
# Build and run with Docker Compose (recommended)docker-compose up -d
# Check healthcurl http://localhost:3000/health
# View logsdocker-compose logs -f
# Stopdocker-compose down

MCP inspector

Use the MCP Inspector for interactive debugging:

bash
npm run inspector

Logging

Check server logs for detailed information:

bash
# stdio mode logs to consolenode build/index.js
# HTTP mode includes HTTP request logsMCP_TRANSPORT_MODE=http node build/index.js

File structure

flowbite-mcp/├── src/│   ├── index.ts              # Main server entry point│   └── server-runner.ts      # Express HTTP Streamable transport├── data/│   ├── components/           # 60+ component markdown files│   ├── forms/                # Form component documentation│   ├── typography/           # Typography elements│   ├── plugins/              # Plugin documentation│   ├── theme.md              # Theme variable reference│   └── quickstart.md         # Getting started guide├── build/                    # Compiled JavaScript output├── package.json├── tsconfig.json└── README.md

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/AmazingFeature)
  3. Commit your changes (git commit -m 'Add some AmazingFeature')
  4. Push to the branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

License

This project is licensed under the MIT License License - see the LICENSE file for details.

Credits

  • Flowbite - For the amazing Tailwind CSS component library
  • Anthropic - For the Model Context Protocol specification
  • Tailwind CSS - For the utility-first CSS framework

Resources

Roadmap

  • Complete component resource access
  • AI-powered theme generator
  • Dual transport support (stdio + HTTP)
  • Flowbite Pro blocks integration (with license authentication)
  • Figma to code conversion tool
  • Enhanced theme customization options
  • Component search and filtering
  • Real-time component preview generation

来源:README.md,提交 576676e

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v1.1.3最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分