Flowbite Mcp

io.github.themesbergPublished by GitHub account themesbergv1.1.3Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

Official Flowbite MCP server that gives an assistant access to Flowbite Tailwind CSS component docs, a branded theme generator, and Figma-to-code conversion.

What you can do
  • Look up Flowbite UI components, forms, typography and plugin documentation as resources
  • Generate a custom branded theme from a hex color
  • Convert a Figma node URL into Flowbite component code
  • Run locally over stdio, or as an HTTP server with Docker and health checks
When to use it
Useful when building Tailwind CSS interfaces with Flowbite and you want the assistant to pull accurate component markup and docs, produce a branded theme, or turn a Figma design into code.
Requirements
Runs locally via npx or Node.js (npm package flowbite-mcp), typically configured in a client such as Claude Desktop, Cursor or Windsurf. The Figma-to-code tool needs a Figma personal access token supplied in the FIGMA_ACCESS_TOKEN environment variable. HTTP mode uses optional MCP_TRANSPORT_MODE, MCP_PORT, MCP_HOST and MCP_CORS_ORIGINS variables.
Before you install
The Figma tool requires a personal Figma API access token (FIGMA_ACCESS_TOKEN) stored in the client configuration; treat it as a secret and scope it narrowly. Figma node URLs are sent to the Figma API. Generated code and themes should be reviewed before use in a project.

Installation

In SourceWeft

  1. Open Flowbite Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

[Image]

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

Source: README.md at commit 576676e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts