f2c-mcp
An MCP (Model Context Protocol) server that lets an MCP-supported IDE connect to Figma and use F2C to parse Figma design nodes/links and generate pixel-perfect HTML/CSS and framework-specific code (e.g., React, CSS Modules, Tailwind). It also supports localization of remote Figma images to local assets.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security posture cannot be fully verified from the provided materials. The README includes a general Data Privacy Notice about logging for usage/error reporting but does not specify what data is logged, retention periods, or how credentials are handled. Dependencies include express/cors/node-fetch/zod and a data reporter package; without lockfile/CVE data, dependency hygiene is inferred rather than confirmed. TLS usage is not stated; MCP/HTTP servers typically use HTTPS only if deployed behind TLS.
⚡ Reliability
Best When
You are using an MCP-capable IDE/agent and want to integrate Figma-to-code workflows with AI tool support, ideally with mitigation for Figma rate limits.
Avoid When
You need fine-grained programmatic control through a public HTTP API rather than MCP tool calls, or you cannot provide/handle required Figma access credentials and rate-limit constraints.
Use Cases
- • Convert specific Figma design nodes (via Figma node links/URLs) into pixel-perfect HTML/CSS
- • Generate UI code for multiple frameworks (React, Tailwind, CSS Modules) from Figma designs
- • Enable an AI coding IDE (e.g., Cursor) to fetch Figma design context and assets during development
- • Download/localize Figma images to speed up asset handling in generated code
Not For
- • Highly automated bulk migrations where Figma API rate limits will be a bottleneck without mitigation
- • Environments requiring strict, verified privacy/compliance guarantees beyond the provided statement
- • Use cases that need a standalone REST/GraphQL API for non-MCP clients
Interface
Authentication
The provided README data does not describe MCP authentication mechanisms (if any) or Figma credential handling details (API tokens/OAuth/scopes). Expect that Figma API access is required, but specifics are not observable from the supplied content.
Pricing
No pricing information was provided in the supplied README or manifest data. Figma API usage may incur platform constraints/costs depending on the Figma account plan.
Agent Metadata
Known Gotchas
- ⚠ Figma REST API rate limits may cause failures; README suggests switching to @f2c/mcp-plugin when affected.
- ⚠ MCP tool error formats and retry/idempotency behavior are not documented in the provided content; agents should expect to implement cautious retry/backoff for Figma-related requests.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for f2c-mcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.