Figwright vs Flowbite MCP
A side-by-side look at the Figwright and Flowbite MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Figwright for architecture & design work as a local process; choose Flowbite 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 Figwright when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
Read, Write, Grounding.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 69/100 · Great | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Free |
| Required env vars | None listed | FIGMA_ACCESS_TOKENMCP_TRANSPORT_MODEMCP_PORTMCP_HOSTMCP_CORS_ORIGINS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,122 | 42 |
| Directory activity | 6 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 3 | 2 |
| Full listing | View Figwright | View Flowbite MCP |
Tools & capabilities
Figwright tools 3
Readselection, document and node inspection, styles, variables, components, fonts, prototype reactions and flows, motion (animation) state, screenshots, original image-fill assets, PDF export, and video export of animated frames (MP4 / GIF / WebM); plus `list_files` / `use_file` for working across more…Writecreate and edit frames, text, shapes (lines, polygons, stars, boolean operations, flattening), auto-layout, alignment and distribution, effects, images (as a new layer or into an existing layer's fill), styles, variables (including importing a team library's variables and styles, and switching a fr…Grounding`get_design_context` for faithful, de-duplicated design context, and `component_map` / `token_map` / `icon_map`, which join Figma data to your codebase so codegen reuses what you already have; plus `design_diff`, which reports what changed in a design against a saved baseline so you update only the…
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.
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.
Figwright
{
"mcpServers": {
"awdr74100-figwright": {
"command": "npx",
"args": [
"-y",
"@figwright/mcp@latest"
]
}
}
}
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"
}
}
}
}
Frequently asked questions
Figwright is categorized under Architecture & Design and uses a local stdio subprocess. Flowbite MCP belongs to Architecture & Design and uses a local stdio subprocess. Pick Figwright for architecture & design work and Flowbite 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.
Figwright is listed as free. Auth: no auth required. Flowbite MCP is listed as free. Auth: api key required. 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 awdr74100-figwright and themesberg-flowbite-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Figwright has a quality signal of 69/100 (Great) with 6 views, 0 installs and 1,122 GitHub stars. Flowbite MCP has 61/100 (Good) with 3 views, 0 installs and 42 GitHub stars.