Figma vs Flow2
A side-by-side look at the Figma and Flow2 MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Figma for architecture & design work as a local process; choose Flow2 for architecture & design over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Figma 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_API_KEY. - You want tools like
list_file_variables, get_published_variables, modify_variables.
Choose Flow2 when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 60/100 · Good | 36/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | FIGMA_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 10 | 0 |
| Directory activity | 6 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Figma | View Flow2 |
Tools & capabilities
Figma tools 3
list_file_variablesget_published_variablesmodify_variables
Flow2 tools
No tool names declared yet. Check the project README from the listing page.
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.
Figma
{
"mcpServers": {
"figma-2": {
"command": "bunx",
"args": [
"figma-mcp-server"
],
"env": {
"FIGMA_API_KEY": "YOUR_FIGMA_API_KEY_HERE"
}
}
}
}
Flow2
{
"mcpServers": {
"flow2": {
"url": "https://mcp.flow2.co/"
}
}
}
Frequently asked questions
Figma is categorized under Architecture & Design and uses a local stdio subprocess. Flow2 belongs to Architecture & Design and uses a remote HTTP/SSE transport. Pick Figma for architecture & design work and Flow2 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.
Figma has no declared pricing — check the project's own site. Auth: api key required. Flow2 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 figma-2 and flow2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Figma has a quality signal of 60/100 (Good) with 6 views, 0 installs and 10 GitHub stars. Flow2 has 36/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.