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)
Create images, videos, music, voices, sound effects and 3D with any AI model, plus AI video clips.
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.
CUTPRO_API_KEY, CUTPRO_WORKSPACE_IDValues 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 …”.
Works in Claude on the web, desktop and mobile:
https://mcp.cut.proOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"cutpro": {
"command": "npx",
"args": [
"-y",
"@cutpro/mcp"
],
"env": {
"CUTPRO_API_KEY": "your-value",
"CUTPRO_WORKSPACE_ID": "your-value"
}
}
}
}Run this in your terminal
claude mcp add --transport http cutpro https://mcp.cut.proclaude mcp add cutpro --env CUTPRO_API_KEY=your-value --env CUTPRO_WORKSPACE_ID=your-value -- npx -y @cutpro/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cutpro": {
"url": "https://mcp.cut.pro"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cutpro": {
"command": "npx",
"args": [
"-y",
"@cutpro/mcp"
],
"env": {
"CUTPRO_API_KEY": "your-value",
"CUTPRO_WORKSPACE_ID": "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": {
"cutpro": {
"type": "http",
"url": "https://mcp.cut.pro"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"cutpro": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cutpro/mcp"
],
"env": {
"CUTPRO_API_KEY": "your-value",
"CUTPRO_WORKSPACE_ID": "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.
ChatGPT connects only to servers on the internet:
https://mcp.cut.proMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
CUTPRO_WORKSPACE_ID envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
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 6, 2026
The registry name was verified with the GitHub account getcutpro, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
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 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: CUTPRO_API_KEY
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (3.0.3) reached the registry 5 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.
A Model Context Protocol (MCP) server for AI generation of every kind, AI characters and clips. It exposes the full CutPro API as tools, so an LLM can:
Ask in any language. Some things people do with it:
server/discover, cacheable lists, multi round-trip requests) and every earlier revision, on the same endpoint.Most clients use the same JSON. Add your API key under env:
{
"mcpServers": { "cutpro": { "command": "npx", "args": ["-y", "@cutpro/mcp@latest"], "env": { "CUTPRO_API_KEY": " " } } } }
After installing via a button, add your CUTPRO_API_KEY to the server's env.
Claude Code
claude mcp add cutpro --env CUTPRO_API_KEY=<your-api-key> -- npx -y @cutpro/mcp@latest
Claude Desktop
Add to claude_desktop_config.json (Settings, Developer, Edit Config):
{
"mcpServers": { "cutpro": { "command": "npx", "args": ["-y", "@cutpro/mcp@latest"], "env": { "CUTPRO_API_KEY": " " } } } }
Cursor / Windsurf / VS Code (manual)
Add the standard config above to the client's MCP settings (mcp.json / mcpServers).
Cline
Open the MCP Servers panel, choose Configure, and add the standard config above.
Gemini CLI
gemini mcp add cutpro npx -y @cutpro/mcp@latest -e CUTPRO_API_KEY=<your-api-key>
Codex
Add to ~/.codex/config.toml:
[mcp_servers.cutpro]
command = "npx" args = ["-y", "@cutpro/mcp@latest"] env = { "CUTPRO_API_KEY" = " " }
ChatGPT and Claude.ai (hosted, no install)
Use the hosted server. Add a custom connector pointing to:
https://mcp.cut.pro
You sign in to cut.pro, pick the workspace and approve the connection, so no API key and no local setup are needed. Any CutPro plan can connect; jobs use the workspace's credits. Disconnect at any time in Settings, under Connected apps.
Claude Code plugin
The plugin bundles the hosted server with a skill that teaches Claude the CutPro workflows:
claude plugin marketplace add getcutpro/mcp
claude plugin install cutpro@cutpro
Every install stays current on its own:
https://mcp.cut.pro, the Claude plugin and the ChatGPT app): always the latest release, nothing to do.npx -y @cutpro/mcp@latest): on start the server checks npm and, when a newer release exists, hands the session to it. This works even for a pinned version or a stale npx cache. Set CUTPRO_MCP_AUTO_UPDATE=0 to stay on the installed version; the server then tells the model an update is available.Every release is listed with its notes in Releases and CHANGELOG.md.
The server is configured with environment variables.
| Variable | Description | Required |
|---|---|---|
CUTPRO_API_KEY | Your CutPro API key. | Yes (stdio) |
CUTPRO_WORKSPACE_ID | Selects the workspace for multi-workspace keys. | No |
CUTPRO_API_URL | Override the API base URL. Defaults to https://api.cut.pro/api/v1. | No |
CUTPRO_MCP_AUTO_UPDATE | 0 keeps the installed version instead of switching to the newest release. | No |
Self-hosting the remote (Streamable HTTP + OAuth)
| Variable | Description |
|---|---|
MCP_TRANSPORT=http / PORT | Serve Streamable HTTP at the root instead of stdio. |
MCP_OAUTH=1 | Enable the full OAuth 2.1 layer (discovery, DCR, PKCE) for browser clients. |
MCP_PUBLIC_URL | Public endpoint, e.g. https://mcp.cut.pro. Its origin becomes the OAuth issuer. |
MCP_REDIS_URL | Back OAuth state with Redis so it survives restarts and scales across instances. |
CUTPRO_APP_URL | Where the consent screen lives. Defaults to https://cut.pro. |
OPENAI_APPS_CHALLENGE | Domain verification token from the OpenAI plugin portal, served at /.well-known/openai-apps-challenge. |
MCP_TRANSPORT=http PORT=8787 MCP_OAUTH=1 \
MCP_PUBLIC_URL=https://mcp.cut.pro MCP_REDIS_URL=redis://127.0.0.1:6379 \ npx -y @cutpro/mcp@latest
In OAuth mode the user signs in on cut.pro and approves the app there; cut.pro creates a key for that app and workspace, and the access token maps server side to it. Clients can register dynamically (DCR) or present a Client ID Metadata Document (CIMD). Without MCP_REDIS_URL, an in-memory store is used (single instance, state lost on restart).
The tools are built from the API's own OpenAPI spec (/api/v1/openapi.json), so they always match the API reference: one tool per endpoint, named after its operationId in snake case (analyzeVideo is analyze_video, createSubmission is create_submission), with the endpoint's own parameters, descriptions and responses. A new endpoint becomes a tool within ten minutes of reaching the API, with no new release of this package.
The usual flows:
list_featured_models (or list_models for the full catalog), quote_generation for the exact price, create_generation with that price and wait, then get_generation until it is ready. A model's own fields go in options, named as in its parameters. Pass a ready image's output.image_id to animate it, or a voice's `oOnly the beginning is shown; read the rest in the repo