In-depth architectural comparison of the Brandkit MCP and Figma Context MCP AIR 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
Brandkit MCP
Architecture & Design · Remote HTTP/SSE
Quality: 59/100 (Good) | Auth: No auth required
Figma Context MCP AIR
Architecture & Design · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Brandkit MCP if you need specialized Architecture & Design tools running via a hosted cloud SSE transport. Choose Figma Context MCP AIR 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 Brandkit MCP when:
You need dedicated capabilities in the Architecture & Design domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Brandkit MCP is categorized under Architecture & Design and uses a remote streaming HTTP/SSE transport. In contrast, Figma Context MCP AIR belongs to Architecture & Design using local stdio subprocess. Select Brandkit MCP when you need capabilities focused on architecture & design and Figma Context MCP AIR when you require tools for architecture & design.
Return the brand's differentiation document (agent/verbal/differentiation.md). Includes a taste primer.
get_concepts
Return the brand's creative concepts/directions (agent/verbal/concepts.md). Includes a taste primer.
get_voice
Return the brand's voice document (agent/verbal/voice.md). Includes a taste primer.
get_colors_and_type
Return colors and typography as CSS custom properties from agent/visual/colors_and_type.css (with optional artifact override).
get_assets
Return logos and other binary assets from agent/visual/assets/. Replaces v1 get_logos + get_textures.
get_fonts
Return font faces declared in agent/visual/fonts/ (binary files + optional fonts.yaml manifest).
get_components
Return UI component specifications from agent/visual/components/. Optionally filtered by context (base | web | product).
+6 more tools listed on main page
Figma Context MCP AIR Tools (7)
download_figma_images
Downloads PNG or SVG renders of Figma nodes to your local filesystem.
get_screenshot
Captures a Figma node as a 2x PNG and saves it to disk. Useful for visual validation.
get_metadata
Returns a sparse XML representation of the node hierarchy (depth=2). Use this for quick layer discovery before fetching full design context.
get_variable_defs
Fetches all design tokens from a Figma file — variable collections (colors, spacing, typography) and published styles (effects, text styles, fill styles). Returns data with CSS custom property syntax.
whoami
Returns the authenticated user's Figma account information (name, email, plan tier). Useful for verifying your API key is working.
create_design_system_rules
Generates a comprehensive markdown template for project-specific design system rules. Tailored to your language and framework combination. Save the output to `CLAUDE.md` or your project's AI instructions file.
get_figjam
Extracts content from a FigJam board — sticky notes, connectors, shapes, sections — as XML with screenshot URLs.