About flowbite-mcp
flowbite-mcp is the official MCP server for Flowbite, giving AI assistants access to its Tailwind CSS component library and a theme generator. It is aimed at front-end developers building UI with AI tools in their editors. The server can also turn a Figma node URL into code when a Figma access token is set.
Key features
- 01Access to 60+ Flowbite UI component resources
- 02Theme file generation from a brand hex color
- 03Figma node URL to code conversion
- 04stdio and HTTP Streamable transports
- 05Docker support with a health check endpoint
Use cases
- 01Building interface sections with Flowbite components inside an AI editor
- 02Generating a Tailwind CSS theme from a brand color
- 03Converting Figma designs into Flowbite-style code
MCP support
The project runs as an MCP server, exposing Flowbite component resources and theme and Figma-to-code tools to clients such as Cursor and Claude.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y flowbite-mcpFIGMA_ACCESS_TOKENSecretYour personal access token for the Figma APILocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
2Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| figmaNodeUrl | string | Yes | The URL of the Figma node (e.g., https://www.figma.com/design/fileKey/fileName?node-id=123-456) |
Details
From the project README
Official MCP server for Flowbite to leverage AI for UI creation and theme generation
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:
- 📦 60+ UI components - Complete access to the Flowbite UI components
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:
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.
// 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:
{
"mcpServers": {
"flowbite": {
"command": "npx",
"args": ["-y", "flowbite-mcp"],
"env": {
"FIGMA_ACCESS_TOKEN": "YOUR_PERSONAL_FIGMA_ACCESS_TOKEN"
}
}
}
}
Cursor editor
Update the mcp.json file and add the following configuration:
{
"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:
{
"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:
# 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:
node build/index.js --mode http --port 3000
This will make the MCP server available at 'http://localhost:3000/mcp'.
Local development
# Clone the repository
git clone https://github.com/themesberg/flowbite-mcp.git
cd flowbite-mcp
# Install dependencies
npm install
# Build the project
npm run build
# Run in stdio mode (for Claude Desktop, Cursor)
npm start
# Run inspector
npm 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:
# Using npx
npx flowbite-mcp --mode http --port 3000
# Using Docker Compose
docker-compose up -d
# Health check
curl http://localhost:3000/health
Hosting variables
Configure the server behavior with these environment variables:
# Transport mode: stdio (default) or http
MCP_TRANSPORT_MODE=http
# Server port for HTTP mode
MCP_PORT=3000
# Host binding for HTTP mode
MCP_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
# Build and run with Docker Compose (recommended)
docker-compose up -d
# Check health
curl http://localhost:3000/health
# View logs
docker-compose logs -f
# Stop
docker-compose down
MCP inspector
Use the MCP Inspector for interactive debugging:
npm run inspector
Logging
Check server logs for detailed information:
# stdio mode logs to console
node build/index.js
# HTTP mode includes HTTP request logs
MCP_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.
- Fork the repository
- Create your feature branch (
git checkout -b feature/AmazingFeature) - Commit your changes (
git commit -m 'Add some AmazingFeature') - Push to the branch (
git push origin feature/AmazingFeature) - 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
- 🎨 Flowbite Documentation
- 📦 Flowbite Components
- 🌐 Model Context Protocol
- 🚀 Tailwind CSS v4 Docs
- 💬 GitHub Issues
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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.