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: Environment variables Currently you only need the Figma personal access token if you want to enable the Figma to code generation tool. 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: Cursor editor Update the mcp.json file and add the following configuration: Windsurf editor Update the mcp_config.json file and add the following configuration: Glama.ai Local Transport Modes Standard I/O (stdio) The default mode for local development and CLI integrations: 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: This will make the MCP server available at 'http://localhost:3000/mcp'. Local development Production deployment (HTTP Mode) For production servers with multiple clients: Hosting variables Configure the server behavior with these environment variables: Docker Configuration The project includes a production-ready Docker setup with multi-stage builds for optimal performance. Quickstart with Docker MCP inspector Use the MCP Inspector for interactive debugging: Logging Check server logs for detailed information: File structure 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.