Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
作者提供的说明(英文原文)
On-model and ghost-mannequin fashion photos from a product photo. Spends credits; needs an API key.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
在终端中运行这条命令
claude mcp add --transport http fashio https://mcp.fashiolabs.com/mcp --header 'Authorization: your-value'运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"fashio": {
"url": "https://mcp.fashiolabs.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"fashio": {
"type": "http",
"url": "https://mcp.fashiolabs.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
Authorization 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 fashiolabs.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 213 毫秒内响应(HTTP 401)
需要你自己复制粘贴密钥或令牌
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.1.1)于12天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有: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、图片和脚本已被移除。链接会离开本站。
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.