Figma vs StyleKit
A side-by-side look at the Figma and StyleKit 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 StyleKit 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 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 StyleKit when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 60/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| 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 | 649 |
| Directory activity | 8 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Figma | View StyleKit |
Tools & capabilities
Figma tools 3
list_file_variablesget_published_variablesmodify_variables
StyleKit 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"
}
}
}
}
StyleKit
{
"mcpServers": {
"stylekit": {
"command": "npx",
"args": [
"-y",
"shadcn"
]
}
}
}
Frequently asked questions
Figma is categorized under Architecture & Design and uses a local stdio subprocess. StyleKit belongs to Architecture & Design and uses a local stdio subprocess. Pick Figma for architecture & design work and StyleKit 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. StyleKit 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 stylekit 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 8 views, 0 installs and 10 GitHub stars. StyleKit has 52/100 (Good) with 3 views, 0 installs and 649 GitHub stars.