Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
作者提供的说明(英文原文)
Generate image, video, music and speech through Chutes and save assets into your project.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
CHUTES_API_KEY标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"chutes-media": {
"command": "npx",
"args": [
"-y",
"chutes-media-mcp"
],
"env": {
"CHUTES_API_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add chutes-media --env CHUTES_API_KEY=your-value -- npx -y chutes-media-mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"chutes-media": {
"command": "npx",
"args": [
"-y",
"chutes-media-mcp"
],
"env": {
"CHUTES_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"chutes-media": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"chutes-media-mcp"
],
"env": {
"CHUTES_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 TheStreamCode 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:CHUTES_API_KEY
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(2.1.0)于7天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 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、图片和脚本已被移除。链接会离开本站。
Generate image, video, music, and speech through Chutes from any coding agent, with the asset saved straight into the project you are working on.
Chutes Media MCP is a Model Context Protocol (MCP) server and command-line interface (CLI) that give coding agents access to Chutes media models. It ships as an MCP server on standard input/output (stdio), a thin CLI for agents without MCP support, and a bundled Agent Skill for the describe-then-generate workflow.
Instead of hardcoding a payload per model, the server fetches the model's live schema and validates each request before spending a GPU call, then writes the asset and a provenance record into your workspace. It works with Claude Code, Cursor, Cline, Windsurf, Codex, OpenCode, and Claude Desktop.
This is an independent community project. It is not affiliated with, sponsored by, or endorsed by Chutes.
Run the server from npm without installing it globally:
npx -y chutes-media-mcp
Install it globally to put both binaries on your path:
npm install -g chutes-media-mcp
Register the server with Claude Code:
claude mcp add chutes-media --env CHUTES_API_KEY=cpk_your_key -- npx -y chutes-media-mcp
For Cursor, Cline, Windsurf, OpenCode, and Claude Desktop, add the mcpServers entry documented in docs/mcp-and-cli.md. Running from GitHub instead of npm is supported with npx -y github:TheStreamCode/chutes-media-mcp. Upgrading from 1.x? See docs/migration-2.0.md.
assets/chutes/image/. The returned path is ready to reference from your code.The same describe-then-generate flow is available from a shell through the chutes-media CLI. See docs/mcp-and-cli.md for the tool reference, CLI examples, and image editing.
img2img or inpaint.overwrite is explicitly set.| Variable | Required | Default | Purpose |
|---|---|---|---|
CHUTES_API_KEY | Yes | none | Chutes API key. Read from the environment; never written to disk. |
CHUTES_AUTH_SCHEME | No | raw | How the key is sent in Authorization: raw (the key as-is) or bearer (value prefixed with Bearer and a space). On a 401, try the other value. |
CHUTES_API_BASE_URL | No | https://api.chutes.ai | Management API base URL. HTTPS is required except for loopback development; custom endpoints never receive the Chutes API key. |
CHUTES_OUTPUT_DIR | No | assets/chutes | Output directory inside the agent's working directory. A / subfolder is appended. |
CHUTES_WARMUP | No | true | Warm models up before invoking them. Set to false to skip warmup. |
CHUTES_COLD_START_RETRIES | No | 4 | Retries when a cold model returns 503 no-instances. 0 disables retries. |
CHUTES_COLD_START_BACKOFF_MS | No | 8000 | Base backoff between cold-start retries; it grows per attempt. |
CHUTES_MAX_ASSET_MB | No | 512 | Maximum response or local input asset size kept in memory. The maximum is 4096. |
CHUTES_PROGRESS_INTERVAL_MS | No | 5000 | How often progress heartbeats are emitted while a call blocks. |
CHUTES_ALLOW_UNKNOWN_PARAMS | No | false | When true, accept parameters that are not in the model schema. The default rejects them so a renamed field fails loudly. |
CHUTES_PROVENANCE | No | true | Write a .json sidecar with model, cord, params, and schema hash. Set to false to disable. |
Generated assets are saved under ./assets/chutes/ /, relative to wherever the agent runs, so they land inside the project. Output traversal and symlink escapes are rejected, and existing files are preserved unless overwrite is enabled.
The API key is read from CHUTES_API_KEY and kept in memory. Credential-bearing requests go only to HTTPS Chutes hosts, remote asset URLs are screened against private-network destinations, and file access is contained to the workspace. Query strings and fragments are removed from network-error messages so signed asset URLs do not end up in logs. The project collects no telemetry. See SECURITY.md for reporting.
The key is missing, invalid, or sent with the wrong authentication scheme. Confirm CHUTES_API_KEY is set for the process that launches the server, then set CHUTES_AUTH_SCHEME to bearer or raw, whichever differs from the current value.
The model is scaled to zero and Chutes has no instance ready. The server retries automatically; raise CHUTES_COLD_START_RETRIES and CHUTES_COLD_START_BACKOFF_MS if the delay is too short, or pick another model of the same kind.
The live model schema changed or the parameter name is wrong. Call describe_media_model again and rebuild the payload from the current schema. CHUTES_ALLOW_UNKNOWN_PARAMS=true is a temporary workaround, not a fix.
Every input and output path must resolve inside the current workspace, and an existing file is not replaced implicitly. Pass the explicit overwrite option (or --overwrite in the CLI) after checking the target path.
Requirements: Node.js ^20.19.0, >= 22.13.0, or >= 24 with npm.
git clone https://github.com/TheStreamCode/chutes-media-mcp
cd chutes-media-mcp npm ci npm run check npm run verify:mcp npm run release:check
npm run check runs the format check, lint, type check, coverage tests, and the build. npm run verify:mcp starts the built stdio server with a placeholder key and validates the MCP handshake, the instructions and the three tool definitions without calling Chutes. npm run release:check keeps package.json, CHANGELOG.md, CITATION.cff and server.json on the same version. CONTRIBUTING.md covers the Windows path caveat and the opt-in live tests.
Ask usage questions in GitHub Discussions, report reproducible defects in GitHub Issues, and report vulnerabilities privately as described in SECURITY.md.
See CONTRIBUTING.md. Pull requests must pass the required CI checks.
MIT — see LICENSE. Third-party notices are in NOTICE.
Maintained by Michael Gasperini (Mikesoft). If this project is useful to you, consider sponsoring its maintenance.