Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
GitHub Copilot
Gemini CLI+20 moreClaude CodeCursorCodex CLIGitHub CopilotGemini CLI
OpenClaw
Manus
Grok+17 agentsFigma MCP Setup
Connect and verify Figma MCP servers with proper scoping, authentication, and design-system wiring.
Free
Figma MCP Setup
Example session with this skill installed
Connect Figma to this project. I need to be able to read designs and write code that uses our local Tailwind tokens.
- Read your context and instructions
- Compiled the figma mcp setup
- Generated the UI component
I will set up the Figma Remote MCP. First, I'll register it at the project scope so your team can use it. Then, I'll verify the connection by reading your design file. Finally, I'll create a rules file to map your Figma variables to your tailwind.config.js. Ready to authenticate?
figma-mcp-setup.tsx
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Setting up Figma MCP servers often fails because developers choose the wrong server type for their needs or register it at a scope that doesn't persist. Most issues arise from confusing the remote OAuth server with the local desktop loopback, leading to 401 errors or code that ignores your project's existing design tokens.
What it does
- Identifies whether you need the remote server for cloud/CI tasks or the desktop server for local app selection.
- Registers the server at the correct scope (user vs. project) to ensure configurations work for the whole team or just your local machine.
- Authenticates and verifies the connection with a live tool call to confirm design data is actually readable.
- Wires the project by mapping Figma components and tokens to your local codebase, preventing the agent from generating disconnected UI code.
Frameworks & tools
Supports Figma MCP (Remote and Desktop), Claude Code, Cursor, and any MCP-compliant client. Works with Figma Dev Mode and Code Connect.
Why this beats prompting it yourself
Standard prompts often lead to hardcoded file keys or tokens that leak into version control. This skill enforces a strict "verify before wiring" workflow, ensuring the agent doesn't just claim it's connected, but actually proves it can read your specific design nodes before writing a single line of code.
Use cases
- Connect a new repository to Figma to enable design-to-code automation.
- Fix "node not found" or authentication errors in existing MCP setups.
- Configure a team-wide MCP setup that works across different developer machines.
- Map Figma variables and design tokens to specific CSS or Tailwind components.
Known limitations
Desktop server requires a Dev or Full seat on a paid Figma plan and must have the app open in Dev Mode. Remote server requires OAuth via browser.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
2 installs
Downloaded by developers to date
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean 19 days ago
- Free to download with an account