Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Description from the maker (original English)
On-model and ghost-mannequin fashion photos from a product photo. Spends credits; needs an API key.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http fashio https://mcp.fashiolabs.com/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"fashio": {
"url": "https://mcp.fashiolabs.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"fashio": {
"type": "http",
"url": "https://mcp.fashiolabs.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain fashiolabs.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 213 ms (HTTP 401)
Needs a key or token that you copy and paste yourself
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 12 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
MCP (Model Context Protocol) server for the Fashio API — lets Claude, Cursor, and other MCP-speaking agents generate on-model fashion photos directly, as tool calls.
Fashio turns a garment or product photo into publish-ready e-commerce photography and video with AI — virtual try-on, catalog packs, background removal, upscaling, reframing, and more. This package is the official MCP client for its public v1 REST API.
It's a thin wrapper: every tool here calls the same public api.fashiolabs.com v1 REST API a curl script would. No local business logic — the API is the source of truth.
mcp.fashiolabs.com runs this same server as a hosted HTTP endpoint — nothing to install, just add the URL with your key as a bearer token:
{
"mcpServers": { "fashio": { "url": "https://mcp.fashiolabs.com/mcp", "headers": { "Authorization": "Bearer fio_live_..." } } } }
(Exact config UI/field names vary by client — Claude Desktop, Claude Code and Cursor all support adding a remote/HTTP MCP server by URL with custom headers as of 2026.)
Runs on your own machine instead of a hosted endpoint — same tools, same billing.
claude_desktop_config.json (or .mcp.json for Claude Code):
{
"mcpServers": { "fashio": { "command": "npx", "args": ["-y", "fashio-mcp"], "env": { "FASHIO_API_KEY": "fio_live_..." } } } }
git clone https://github.com/fashiolabs/fashio-mcp.git
cd fashio-mcp npm install npm run build
Then point your client's config at the built entry point instead of npx:
{
"mcpServers": { "fashio": { "command": "node", "args": ["/absolute/path/to/mcp-server/dist/index.js"], "env": { "FASHIO_API_KEY": "fio_live_..." } } } }
| Tool | Description |
|---|---|
list_models | Every valid toolId for create_generation, with input shape and fallback price. |
list_fashion_models | Browse the AI person model catalog (gender, limit). |
list_venues | Browse the venue/background catalog (limit). |
list_poses | Browse the pose catalog (type, limit). |
upload_image | Uploads a local file (jpg/png/webp, max 8MB) and returns a usable URL. |
create_generation | Starts a job — same request shape as POST /v1/generations. Returns {id, status: "processing"}. Pass templateSetId to reuse a saved style instead of picking fashion_model/venue/pose by hand. |
get_generation | Polls a job by id until status is completed or failed. |
get_account | Email, plan, diamond (credit) balance, and renewal date for the account that owns the key. |
create_template_set | Saves a completed generation's fashion_model/venue/pose/shotType/stylePreset/ratio as a named preset — reuse it on a new garment via create_generation's templateSetId. |
list_template_sets | Lists presets saved with create_template_set. |
delete_template_set | Deletes a saved preset. |
list_ready_template_sets | Browses Fashio's own curated "ready photoshoot" library (model + venue + pinned poses) — a different, larger catalogue than your own saved presets above. |
get_ready_template_set | Fetches one curated set, including its full list of shots. |
create_catalog_job | Runs your product photo through every shot (or a chosen subset) of a curated photoshoot set — one image per shot, billed per shot. Poll with get_generation. |
See docs.fashiolabs.com for the full endpoint reference these tools wrap, and docs.fashiolabs.com/llms-full.txt for a plain-text version written for an LLM to read in one pass — including which images.* fields each toolId needs.
There is no separate MCP or API plan. Every create_generation call deducts diamonds (Fashio's credit unit) from the account that owns the API key — exactly as a generation from the app or dashboard would. A failed generation refunds its diamonds automatically.
npm run dev # tsc --watch
npm run build npm start # runs dist/index.js directly (expects FASHIO_API_KEY in env)
MIT — see LICENSE.