Figma MCP for free users — no rate limits, full read/write, text to designs, designs to code
1.3k
Stars
195
Forks
31
Open issues
7
Contributors
AI Analysis
A Figma MCP server written in Go that enables AI tools (Claude, Cursor, GitHub Copilot) to read and write Figma designs without hitting API rate limits—targeting free users and cost-conscious teams who need design automation, text-to-design, and design-to-code capabilities. Best suited for AI-driven design workflows and developers integrating Figma into AI agent automation; not a general-purpose Figma API client.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Go-based Figma MCP bypassing official API to offer unlimited free design automation
figma-mcp-go is a Model Context Protocol server that enables AI tools (Claude, Cursor, GitHub Copilot) to read and write Figma designs without using the official REST API, thereby avoiding Figma's strict rate limits (6 calls/month on free plans). Built in Go and distributed via npm, it bundles a Figma plugin to bridge commands. Targets AI-native design workflows where free-tier users hit rate limits quickly. Acquired 1,231 stars in 3 months with 67 new stars in the last 7 days, suggesting active community interest in the rate-limit workaround.
Created 2026-03-26, less than 3 months old at analysis date. Part of a recent wave of Figma MCP servers (competitors include southleft/figma-console-mcp, GLips/Figma-Context-MCP with 15k+ stars, and grab/cursor-talk-to-figma-mcp with 6.8k stars). Emerged specifically because the creator lacked budget to pay for higher Figma API rate limits and built a workaround.
Rapid adoption from near-zero, likely driven by: (1) free tier users experiencing rate limit frustration on Figma's official API, (2) popularity of MCP-compatible AI tools (Cursor, Claude) in 2026, (3) clear, single-value proposition (no rate limits), and (4) low friction setup via npx. 67 stars/week velocity suggests sustained interest rather than launch spike, but 3-month window makes long-term trend unclear.
adoption not verified — no case studies, testimonials, or documented production deployments mentioned in README. Star count and npm package presence indicate some real usage, but scale and depth unknown. High recent velocity (67 stars/7 days) suggests experimental adoption among AI tool users, but verifiable production usage metrics absent.
Appears to be a Go binary distributed as npm package, wrapping a Figma plugin (manifest.json in releases). README documents 73 tools spanning read operations (get_design, list_nodes, export_as_code) and write operations (create_frame, set_text, set_fills, etc.). Likely uses plugin-to-server IPC to bypass official API. No implementation details visible in README; cannot verify Go code quality, error handling, or concurrency patterns.
not documented in README
Last push 2026-06-27, 3 days before analysis date — highly recent. MIT license, npm package published. Issue/PR activity not visible from metadata. Project is extremely young (3 months); 'active' status is confirmed by recency but insufficient history to assess long-term maintainability. README is detailed and well-formatted, suggesting care in presentation.
ADOPT IF: you are a free-tier Figma user building AI-driven design workflows (text-to-design, bulk edits) and willing to tolerate a community tool with 3-month track record. AVOID IF: you require enterprise-grade support, SLA guarantees, or cannot risk using a workaround that could be affected by Figma plugin policy changes. MONITOR IF: you are considering this as a paid-tier alternative — the rate-limit motivation disappears at higher plan tiers, and official API may offer better long-term stability.
Independent dimensions
Mainstream potential
4/10
Technical importance
6/10
Adoption evidence
3/10
- Figma could restrict or disable plugin-based API access or issue ToS policy updates that treat this workaround as violating the platform's terms; no legal review documented.
- 3-month project history means insufficient data on maintenance burden, long-term bug fixes, or community support capacity — creator maintenance sustainability unknown.
- Competitors with 5–12x higher star counts (grab/cursor-talk-to-figma-mcp, GLips/Figma-Context-MCP) already occupy similar space; unclear what sustainable differentiation figma-mcp-go offers.
- Go runtime and npm package distribution may create platform compatibility or dependency management issues for users unfamiliar with Go binaries; support requests likely high.
- No adoption metrics (users, production deployments, revenue) visible; growth signal (67 stars/week) cannot confirm actual usage depth or retention.
Likely to remain a niche but stable tool for free-tier AI users in 2026–2027, assuming no Figma policy action. Growth may plateau as competitive landscape saturates and initial rate-limit pain is absorbed by user base (early adopters). Could fade rapidly if Figma closes the plugin workaround or offers official free-tier rate limit increases. Most probable trajectory: modest, sustained userbase (~500–2000 active users within 12 months) serving a specific segment, not mainstream consolidation.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
No language breakdown available.
Information
- Language
- Go
- License
- MIT
- Last updated
- 2w ago
- Created
- 4mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
No commit data available.
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
No open issues — clean slate.
Open pull requests
No open pull requests.
Top contributors
Contributor data not available yet.
Recent releases
No releases published yet.
Similar repos
figma/mcp-server-guide
The Figma MCP server guide enables AI agents to integrate Figma design files...
southleft/figma-console-mcp
Figma Console MCP is a Model Context Protocol server that integrates AI...
GLips/Figma-Context-MCP
This is an MCP (Model Context Protocol) server that connects Figma design files...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
vkhanhqui/figma-mcp-go
this
|
1.3k | +41 | Go | 8/10 | 2w ago |
|
figma/mcp-server-guide
|
1.7k | — | Python | 8/10 | 22h ago |
|
southleft/figma-console-mcp
|
2k | — | TypeScript | 8/10 | 1d ago |
|
GLips/Figma-Context-MCP
|
15.4k | — | TypeScript | 8/10 | 7d ago |
 grab/cursor-talk-to-figma-mcp
|
6.9k | — | JavaScript | 7/10 | 2mo ago |
15,257 stars (12x larger); TypeScript; both are MCP servers. Figma-Context-MCP's adoption scale is dramatically higher, though rate-limit workaround claim is unique to figma-mcp-go.
6,870 stars (5.6x larger); JavaScript; also targets Cursor ecosystem. figma-mcp-go's Go runtime and no-API-token claim may differentiate in specific niches.
1,901 stars (1.5x larger); TypeScript; similar age/scope. figma-mcp-go is newer and claims superior rate limit story.
1,677 stars; official Figma guidance. figma-mcp-go may face risk of Figma issuing plugin policy warnings if the workaround is deemed ToS-violating.
Not a competitor in spirit; figma-mcp-go exists because official API rate limits are prohibitive for free users. Projects that can afford paid seats may prefer official API for stability/support.
