flowbite-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host binding for HTTP mode | 0.0.0.0 |
| MCP_PORT | No | Server port for HTTP mode | 3000 |
| MCP_CORS_ORIGINS | No | CORS origins (comma-separated) | |
| MCP_TRANSPORT_MODE | No | Transport mode: stdio (default) or http | stdio |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert-figma-to-codeA | Fetches a Figma node and its rendered image from the Figma API and converts it to a code block. Requires FIGMA_ACCESS_TOKEN environment variable to be set. |
| generate-themeA | Generates a custom Flowbite theme CSS file based on a brand color (hex format) and user instructions. The AI will intelligently analyze the instructions and customize ALL theme variables (border radius, spacing, colors, typography, etc.) to match the desired aesthetic. This tool creates color shades and variations, adapting the entire theme system to match your brand identity. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| flowbite_overview | Overview of the Flowbite MCP server and its capabilities. |
| flowbite_theme | The theme file that sets the Tailwind CSS variables to make UI look unique for every website. |
| flowbite_quickstart | The quickstart file that sets the Tailwind CSS variables to make UI look unique for every website. |
| flowbite_components | A list of all Flowbite UI components with links to documentation |
| flowbite_accordion | |
| flowbite_alert | |
| flowbite_avatar | |
| flowbite_badge | |
| flowbite_banner | |
| flowbite_bottom_navigation | |
| flowbite_breadcrumb | |
| flowbite_buttons | |
| flowbite_button_group | |
| flowbite_cards | |
| flowbite_carousel | |
| flowbite_chat_bubble | |
| flowbite_clipboard | |
| flowbite_datepicker | |
| flowbite_device_mockups | |
| flowbite_drawer | |
| flowbite_dropdowns | |
| flowbite_footer | |
| flowbite_forms | |
| flowbite_gallery | |
| flowbite_indicators | |
| flowbite_jumbotron | |
| flowbite_kbd | |
| flowbite_list_group | |
| flowbite_mega_menu | |
| flowbite_modal | |
| flowbite_navbar | |
| flowbite_pagination | |
| flowbite_popover | |
| flowbite_progress | |
| flowbite_qr_code | |
| flowbite_rating | |
| flowbite_sidebar | |
| flowbite_skeleton | |
| flowbite_speed_dial | |
| flowbite_spinner | |
| flowbite_stepper | |
| flowbite_tables | |
| flowbite_tabs | |
| flowbite_timeline | |
| flowbite_toast | |
| flowbite_tooltips | |
| flowbite_typography | |
| flowbite_video | |
| flowbite_checkbox | |
| flowbite_file_input | |
| flowbite_floating_label | |
| flowbite_input_field | |
| flowbite_number_input | |
| flowbite_phone_input | |
| flowbite_radio | |
| flowbite_range_input | |
| flowbite_search_input | |
| flowbite_select | |
| flowbite_textarea | |
| flowbite_timepicker | |
| flowbite_toggle | |
| flowbite_charts | |
| flowbite_datatables | |
| flowbite_wysiwyg | |
| flowbite_blockquote | |
| flowbite_headings | |
| flowbite_hr | |
| flowbite_images | |
| flowbite_links | |
| flowbite_lists | |
| flowbite_paragraphs | |
| flowbite_text |
TDQS
Scored across 2 tools
The two tools have completely different purposes: one converts Figma designs to code, the other generates a theme from a brand color. There is no overlap or ambiguity.
Both tools use snake_case and follow a verb-object pattern, though 'convert-figma-to-code' is more detailed than 'generate-theme'. The inconsistency is minor.
With only two tools, the surface feels thin for a design-to-code and theme generation server. However, the scope is narrow enough that the count is borderline acceptable.
The tools cover the core workflows of converting a design and generating a theme. Missing features like theme validation or export are minor gaps for the stated purpose.