Flowbite MCP vs Figma Context MCP
A side-by-side look at the Flowbite MCP and Figma Context MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Flowbite MCP for architecture & design work as a local process; choose Figma Context MCP for architecture & design as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Flowbite MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
FIGMA_ACCESS_TOKEN, MCP_TRANSPORT_MODE, MCP_PORT, MCP_HOST, MCP_CORS_ORIGINS. - You want tools like
convert-figma-to-code, generate-theme.
Choose Figma Context MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
FIGMA_API_KEY. - You want tools like
get_figma_design, get_image_fills, render_node_images.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 61/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | FIGMA_ACCESS_TOKENMCP_TRANSPORT_MODEMCP_PORTMCP_HOSTMCP_CORS_ORIGINS | FIGMA_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 42 | 7 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 2 | 4 |
| Full listing | View Flowbite MCP | View Figma Context MCP |
Tools & capabilities
Flowbite MCP tools 2
convert-figma-to-codeFetches 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-themeGenerates 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.
Figma Context MCP tools 4
get_figma_designFetches CSS-aligned, LLM-optimized design data. Supports SVG export to custom dir.get_image_fillsRetrieves image fill URLs from a Figma filerender_node_imagesRenders Figma nodes as PNG imagesread_vector_svgReads vector node data as SVG
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Flowbite MCP
{
"mcpServers": {
"themesberg-flowbite-mcp": {
"command": "npx",
"args": [
"-y",
"flowbite-mcp"
],
"env": {
"FIGMA_ACCESS_TOKEN": "YOUR_FIGMA_ACCESS_TOKEN_HERE",
"MCP_TRANSPORT_MODE": "YOUR_MCP_TRANSPORT_MODE_HERE",
"MCP_PORT": "YOUR_MCP_PORT_HERE",
"MCP_HOST": "YOUR_MCP_HOST_HERE",
"MCP_CORS_ORIGINS": "YOUR_MCP_CORS_ORIGINS_HERE"
}
}
}
}
Figma Context MCP
{
"mcpServers": {
"figma-context-mcp": {
"command": "npx",
"args": [
"-y",
"@tmegit/figma-to-code-mcp"
],
"env": {
"FIGMA_API_KEY": "YOUR_FIGMA_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Flowbite MCP is categorized under Architecture & Design and uses a local stdio subprocess. Figma Context MCP belongs to Architecture & Design and uses a local stdio subprocess. Pick Flowbite MCP for architecture & design work and Figma Context MCP for architecture & design.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Flowbite MCP is listed as free. Auth: api key required. Figma Context MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add themesberg-flowbite-mcp and figma-context-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Flowbite MCP has a quality signal of 61/100 (Good) with 3 views, 0 installs and 42 GitHub stars. Figma Context MCP has 55/100 (Good) with 2 views, 0 installs and 7 GitHub stars.