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)
Generate image, video, music and speech through Chutes and save assets into your project.
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.
CHUTES_API_KEYValues 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 …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"chutes-media": {
"command": "npx",
"args": [
"-y",
"chutes-media-mcp"
],
"env": {
"CHUTES_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add chutes-media --env CHUTES_API_KEY=your-value -- npx -y chutes-media-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"chutes-media": {
"command": "npx",
"args": [
"-y",
"chutes-media-mcp"
],
"env": {
"CHUTES_API_KEY": "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": {
"chutes-media": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"chutes-media-mcp"
],
"env": {
"CHUTES_API_KEY": "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 one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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 with the GitHub account TheStreamCode, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 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: CHUTES_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (2.1.0) reached the registry 7 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
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.
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.