io.github.themesberg/flowbite-mcp
NPM · FLOWBITE-MCP · SCANNED SEP 20
MCP server to convert Figma designs to Flowbite UI components in Tailwind CSS
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 258 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability43
- 6% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 864 tokens (~11/item across 74 items; 2 tools + 72 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.themesberg/flowbite-mcp server?
io.github.themesberg/flowbite-mcp runs locally as an npm package, launched with npx -y flowbite-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · flowbite-mcp
claude mcp add themesberg-flowbite-mcp -- npx -y flowbite-mcp
{
"mcpServers": {
"themesberg-flowbite-mcp": {
"command": "npx",
"args": [
"-y",
"flowbite-mcp"
]
}
}
} {
"servers": {
"themesberg-flowbite-mcp": {
"command": "npx",
"args": [
"-y",
"flowbite-mcp"
]
}
}
} codex mcp add themesberg-flowbite-mcp -- npx -y flowbite-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"themesberg-flowbite-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"flowbite-mcp"
],
"enabled": true
}
}
} openclaw mcp add themesberg-flowbite-mcp --command npx --arg -y --arg flowbite-mcp
mcp_servers:
themesberg-flowbite-mcp:
command: "npx"
args: ["-y", "flowbite-mcp"] {
"McpServers": {
"themesberg-flowbite-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"flowbite-mcp"
]
}
}
} assistant mcp add themesberg-flowbite-mcp -t stdio -c npx -a -y flowbite-mcp
{
"mcpServers": {
"themesberg-flowbite-mcp": {
"command": "npx",
"args": [
"-y",
"flowbite-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 18 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 17 Sept 26 −2
- Stability: pass → 0.83 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/flowbite-mcp@1.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
convert-figma-to-code ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| figmaNodeUrl | string | yes | The URL of the Figma node (e.g., https://www.figma.com/design/fileKey/fileName?node-id=123-456) |
No output schema declared.
No examples provided.
generate-theme ~229
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brandColor | string | yes | The primary brand color in hex format (e.g., #3B82F6, #FF5733). This will be used as the base for generating all brand color variations. |
| fileName | string | – | Optional filename for the generated theme (e.g., "my-brand-theme.css"). Defaults to "custom-theme.css" |
| instructions | string | yes | Natural language instructions describing the desired theme aesthetic and customizations. The AI will interpret these instructions to modify all relevant theme variables. Examples: "Make it modern and… |
No output schema declared.
No examples provided.
What is the io.github.themesberg/flowbite-mcp server?
io.github.themesberg/flowbite-mcp is listed in the public MCP registry as io.github.themesberg/flowbite-mcp. MCP server to convert Figma designs to Flowbite UI components in Tailwind CSS. This page covers its npm package (flowbite-mcp).
Is the io.github.themesberg/flowbite-mcp server safe to use?
io.github.themesberg/flowbite-mcp scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.themesberg/flowbite-mcp server expose?
io.github.themesberg/flowbite-mcp exposes 2 tools: convert-figma-to-code, generate-theme. Their descriptions and schemas cost roughly 314 tokens of context every time the server is loaded.
Is the io.github.themesberg/flowbite-mcp server still maintained?
io.github.themesberg/flowbite-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.themesberg/flowbite-mcp server under?
io.github.themesberg/flowbite-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.