Figma
Let agents pull Figma exports, design tokens, comments, and project metadata while implementing UI from real design files.
Overview
com.mcparmory/figma is a MCP server for the Build phase that exports Figma files, reads design data, and manages projects, comments, and team assets for coding agents.
What is this MCP server?
- Export files and access structured design data from Figma via MCP
- Manage projects, comments, and team assets from agent sessions
- Install with mcparmory-figma on uvx or ghcr.io/mcparmory/figma:1.0.6 Docker
- stdio transport for design-aware coding workflows
- com.mcparmory/figma version 1.0.6 from mcparmory/registry
- Version 1.0.6 on schema 2025-12-11
- 5 capability areas in description: export, design data, projects, comments, team assets
- 2 packages: PyPI mcparmory-figma and OCI ghcr.io/mcparmory/figma:1.0.6
Community signal: 25 GitHub stars.
What problem does it solve?
Agents guess at UI from screenshots when they cannot read live Figma structure, comments, and exports.
Who is it for?
Builders who design in Figma and want Claude Code or Cursor to align components, copy, and assets with the canonical file.
Skip if: Code-only projects with no Figma workflow, or designers who need in-Figma plugins instead of agent-side API access.
What do I get? / Deliverables
Your agent can query and export Figma resources over MCP so frontend implementation tracks the real design source.
- Agent-accessible Figma exports and design metadata
- Comment and project context inside coding sessions
- Reduced manual copy-paste between Figma and IDE
Recommended MCP Servers
Journey fit
Figma access matters when translating design into code during frontend build, not during early idea research alone. frontend is the canonical shelf for MCP servers that feed layout, assets, and design-system context into implementation agents.
How it compares
Figma REST capabilities as MCP tools, not a Figma plugin or standalone design skill.
Common Questions / FAQ
Who is com.mcparmory/figma for?
Solo builders and small teams implementing UI from Figma who want agents to access exports, comments, and project data via MCP.
When should I use com.mcparmory/figma?
Use it during frontend build when you need agent-assisted implementation, asset export, or comment triage tied to Figma files.
How do I add com.mcparmory/figma to my agent?
Add stdio MCP using uvx mcparmory-figma or Docker ghcr.io/mcparmory/figma:1.0.6 and configure Figma authentication per mcparmory registry docs.