Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
제작자가 쓴 설명(영어 원문)
MCP server for the Frame-Relay design kit: components, tokens and live Figma selections.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"frame-relay": {
"command": "npx",
"args": [
"-y",
"@frame-relay/cli"
]
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add frame-relay -- npx -y @frame-relay/cli프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"frame-relay": {
"command": "npx",
"args": [
"-y",
"@frame-relay/cli"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"frame-relay": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@frame-relay/cli"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 GitHub 계정 Joseph-Brendan 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.1.0-beta.0)은 29일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.
같은 카테고리에는: Figma Context MCP, Claude Real Video, Figma MCP Server
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Let any LLM watch a video locally — and search everything it has ever watched.
The Figma MCP server brings Figma design context directly into your AI workflow.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Turn your Figma components into a design kit your AI coding agent follows.
New to this? Follow the step-by-step setup guide for designers.
Status: public beta. Commands below install the beta tag of the CLI. Expect rough edges and tell us what you find with the beta feedback form.
Frame-Relay is for designers who already work with AI coding tools like OpenCode or Antigravity, and for small teams that want their Figma system to stay the source of truth while AI writes the UI. You keep designing in Figma. Your agent gets exact components, tokens and rules instead of guessing from screenshots.
Live mode is the optional fifth step: pair Figma with your agent and let it read the layer you have selected. See Live mode. Export mode always works without it.
# 1. Create a React + TypeScript app (Vite shown here; any React app works)
npm create vite@latest my-app -- --template react-ts cd my-app
npm install tailwindcss @tailwindcss/vite
@import "tailwindcss"; to src/index.css.npx @frame-relay/cli@beta init --yes npx @frame-relay/cli@beta sync --from ~/Downloads/frame-relay-kit-my-file.zip
npx @frame-relay/cli@beta doctor
Open the folder in OpenCode (or your AI tool), then ask: "Build a settings page with the kit components." The agent calls the MCP server for the component list, props and tokens, and builds.
Getting the Figma plugin: Frame-Relay is coming to Figma Community. Until it is approved, open Figma desktop, go to Plugins, Development, Import plugin from manifest, and pick packages/plugin/manifest.json from this repo.
Full walkthrough: Getting started. Ideas first: Concepts.
These steps are written for a designer who has never used a terminal. A terminal is a window where you type short commands to your computer. Your AI coding tool has one built in.
Step 1. Install Node.js. Go to nodejs.org, download the LTS version, and install it like any other app. _Why:_ Frame-Relay runs on Node.js. Without it, your computer can't run the commands below.
Step 2. Install an AI coding tool. Pick one: Cursor, Antigravity, OpenCode or Claude Code. Install it and sign in. _Why:_ This is the AI that will build your app. Frame-Relay teaches it to use your designs.
Step 3. Add the Frame-Relay plugin to Figma. Open Figma, search for "Frame-Relay" in Community plugins, and click Install. Until the listing is live, download the plugin zip from the latest GitHub release and follow these import steps. _Why:_ The plugin is how your designs leave Figma and reach your AI.
Step 4. Design your components. Build your buttons, inputs and cards as Figma components. Follow the simple naming rules in the naming contract, such as naming a variant "Size=Large" or "State=Hover", and use Figma variables for your colors and spacing. _Why:_ Clear names let Frame-Relay understand your design. Variables let it carry your exact colors and sizes into code.
Step 5. Check your file. Run the Frame-Relay plugin and open the Lint tab. Click Check file. Fix anything it lists, then check again. _Why:_ It's like spell-check for your design file. It catches problems before they turn into messy code.
Step 6. Export your kit. Open the Export tab and click Export kit. A zip file downloads. _Why:_ This zip is your whole design system packed into one box: colors, sizes, components and a picture of each one.
Step 7. Create a project folder. Make a new folder on your computer, for example my-app. Use dashes, not spaces, in the name. Open the folder in your AI tool. _Why:_ Your app's code needs a home.
Step 8. Ask your AI to set up the app. Paste this into your AI tool:
Set up a Vite + React + TypeScript app in this folder, with Tailwind CSS v4 and the "@/" path alias pointing to src. Then run npm run build to confirm it works.
_Why:_ This creates an empty app that Frame-Relay knows how to work with.
Step 9. Set up Frame-Relay. Open the terminal in your AI tool and type:
npx @frame-relay/cli@beta init
Answer yes to its questions. _Why:_ It looks at your app and gets it ready to receive your designs.
Step 10. Bring in your designs. Type this, with a space at the end:
npx @frame-relay/cli@beta sync --from
Then drag your zip file from Step 6 into the terminal and press Enter. _Why:_ This opens the box. It turns your Figma components into real code, and writes rules telling your AI: "Always use these. Never invent your own."
Step 11. Run a health check.
npx @frame-relay/cli@beta doctor
You should see green ticks. _Why:_ It's like the warning lights in a car. It confirms everything is connected before you start building.
Step 12. Ask your AI to build a screen. Start a new chat in your AI tool and ask for what you need, for example: "Build a login page using my design kit." _Why:_ The AI now looks up your components before it builds, so it uses your buttons and inputs instead of making up its own.
Step 13. See your app. In the terminal, type:
npm run dev
Open the link it shows, usually http://localhost:5173, in your browser. _Why:_ You see the page the AI built and can compare it with your Figma design.
Step 14. Check the AI's work.
npx @frame-relay/cli@beta check
_Why:_ It catches any place the AI broke your rules, such as using a random color. If it finds something, ask the AI: "Fix the issues frame-relay check found."
Step 15. Use live mode (optional). Ask your AI: "Start Frame-Relay live mode." It gives you a 6-digit code. In Figma, open the plugin's Live tab, type the code and click Connect. Now select anything in Figma and ask your AI: "Build something that matches my Figma selection." _Why:_ Your AI sees what you select in Figma right away, so you can build from a design you haven't exported yet.
Step 16. When you change your designs. Repeat Steps 5, 6 and 10: check, export and sync again. _Why:_ Your code stays matched to your latest Figma design. If you edited a generated component by hand, Frame-Relay keeps your edit and saves the new version beside it, so you never lose work.
sync writes the setup for each tool it finds, so the agent can start using the kit right away.
| Tool | What sync writes |
|---|---|
| Antigravity | .agents/mcp_config.json and .agents/rules/frame-relay.md |
| OpenCode | opencode.json (merged, other keys kept) and AGENTS.md |
| Cursor | .cursor/mcp.json and .cursor/rules/frame-relay.mdc |
| Claude Code | .mcp.json and CLAUDE.md |
Until the stable release, the package is published with the beta tag only. The simplest setup is to install it as a dev dependency once: npm install -D @frame-relay/cli@beta. Sync then writes a command that uses the local install, and the MCP server starts without changes.
| Page | What it covers |
|---|---|
| Getting started | First-time walkthrough from an empty folder to an AI-built page. |
| Concepts | The kit, sync, rules files, MCP, check, doctor and live mode. |
| CLI commands | Every command, its flags and the files it writes. |
| Figma plugin | The Lint, Export and Live tabs, plus warnings and the icon rule. |
| Live mode | Pairing, the Live tab, live tools, security and troubleshooting. |
| MCP server | The 10 tools your agent calls, resources and client setup. |
| Kit format | Folder layout and every field in the kit JSON files. |
| Converter | How Figma data maps to kit specs, including every warning code. |
| Figma naming contract | The naming rules that keep exports clean. |
| JSON schemas | Stable URLs for the manifest, tokens and component schemas. |
The same docs are published at https://joseph-brendan.github.io/Frame-Relay/.
Setup, commands, branch naming and release notes are in CONTRIBUTING.md. Security reports: SECURITY.md. What we collect: nothing, see PRIVACY.md.
MIT, copyright (c) 2026 Joseph Brendan.