In-depth architectural comparison of the Figma Context MCP and Brandkit MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Figma Context MCP
Architecture & Design · Local stdio
Quality: 71/100 (Great) | Auth: API Key required
Brandkit MCP
Architecture & Design · Local stdio
Quality: 64/100 (Good) | Auth: No auth required
Verdict Summary: Choose Figma Context MCP if you need specialized Architecture & Design tools running via a local process. Choose Brandkit MCP if your workspace requires Architecture & Design integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Figma Context MCP when:
You need dedicated capabilities in the Architecture & Design domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: FIGMA_API_KEY, PORT.
Provide coding agents direct access to Figma data to help them one-shot design implementation.
Expose a company's complete design system (colors, typography, logos, components, guidelines, CSS tokens) to AI tools via MCP. Auto-parses CSS / Markdown / PDF / SVG / fonts; supports marketing vs product contexts with shared overrides; ships 12 tools, 16+ resources under brandkit://, and 4 prompts; stdio + SSE + Streamable HTTP transports. Install via NPM: npx -y brandkit-mcp serve.
Category & Scope
Tools & Capabilities Breakdown
Figma Context MCP Tools (2)
get_figma_data
Get comprehensive Figma file data including layout, content, visuals, and component information
download_figma_images
Download SVG and PNG images used in a Figma file based on the IDs of image or icon nodes. Images will be saved relative to the server's image directory: /home/user
Brandkit MCP Tools (18)
get_brand_overview
High-level overview of the brand atomic system: brand name, magic_trick presence, inventory counts, contexts, and the full v2 tool list.
get_magic_trick
Return the human-authored magic_trick.md taste primer verbatim. This file is human-write-only — never write to it via any tool.
get_positioning
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Figma Context MCP is categorized under Architecture & Design and uses a local stdio subprocess. In contrast, Brandkit MCP belongs to Architecture & Design using local stdio subprocess. Select Figma Context MCP when you need capabilities focused on architecture & design and Brandkit MCP when you require tools for architecture & design.