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)
CreationLoop design partners: company overview, partner offer, FAQ, and apply.
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.
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": {
"partnerloop": {
"command": "npx",
"args": [
"-y",
"@reneturcios/partnerloop",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add partnerloop -- npx -y @reneturcios/partnerloop mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"partnerloop": {
"command": "npx",
"args": [
"-y",
"@reneturcios/partnerloop",
"mcp"
]
}
}
}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": {
"partnerloop": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/partnerloop",
"mcp"
]
}
}
}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 6, 2026
The registry name was verified with the GitHub account CloudCorpRecords, 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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 (0.1.0) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker 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.
partnerloop connects to CreationLoop's hosted MCP endpoint and exposes its public design-partner surface: the canonical company overview, the design-partner program offer, the FAQ, and a way to submit a design-partner application. One binary serves a command-line interface and a stdio MCP server; both simply forward each call upstream, so the text you get back is CreationLoop's own canonical copy, never a local paraphrase.
No API key or account is needed. The endpoint can be overridden with CREATIONLOOP_MCP_URL; when it is not set, calls go to https://creationloop.ai/api/mcp.
npx @reneturcios/partnerloop overview
Or run the container image:
docker run -i ghcr.io/cloudcorprecords/partnerloop
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
partnerloop overview
partnerloop offer partnerloop faq partnerloop apply --email founder@example.com --website https://example.com \ --name Ada --company Example --message "Scaling content."
partnerloop --version
The three read commands print the upstream text exactly as the hosted server returns it. apply prints the upstream confirmation. Exit codes: 0 on success, 1 when a call fails (a validation problem, an upstream error, or a rate limit), 2 for usage errors.
Applications are checked locally before anything is sent: email (a valid address, 3–320 characters) and website (1–500 characters) are required; name and company may be up to 200 characters each and message up to 2000. Unknown fields are rejected. A failed check exits 1 with the problem named, and no request is made.
One bin serves both faces. The mcp subcommand starts a stdio MCP server:
npx -y @reneturcios/partnerloop mcp
MCP client configuration:
{
"mcpServers": { "partnerloop": { "command": "npx", "args": ["-y", "@reneturcios/partnerloop", "mcp"] } } }
To point the server at a different CreationLoop-compatible host, add CREATIONLOOP_MCP_URL to the client's env for this server.
| Tool | Input | What it returns |
|---|---|---|
get_company_overview | (none) | CreationLoop's canonical company information, verbatim from upstream. |
get_design_partner_offer | (none) | The design-partner program description, verbatim from upstream. |
get_faq | (none) | Frequently asked questions and answers, verbatim from upstream. |
submit_design_partner_application | email, website (required); name, company, message (optional) | The upstream confirmation that the application was received. |
Upstream errors — including the endpoint's rate limits (30 requests/minute overall, 5 submissions/minute for applications) — come back as error results carrying the upstream message.
npm install
npm run build # tsc -> dist/ npm test # node test runner over test/*.test.ts, no network (fake fetch fixtures) npm run dev # run the CLI from source via tsx
MIT — see LICENSE.