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)
Draws rigged game gun models in Blender from parameters, checked against the real gun
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.
MODELLAB_BLENDER, MODELLAB_OUT, MODELLAB_WAIT_FORYou 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": {
"modellab": {
"command": "uvx",
"args": [
"modellab-mcp"
],
"env": {
"MODELLAB_BLENDER": "your-value",
"MODELLAB_OUT": "your-value",
"MODELLAB_WAIT_FOR": "your-value"
}
}
}
}Run this in your terminal
claude mcp add modellab --env MODELLAB_BLENDER=your-value --env MODELLAB_OUT=your-value --env MODELLAB_WAIT_FOR=your-value -- uvx modellab-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"modellab": {
"command": "uvx",
"args": [
"modellab-mcp"
],
"env": {
"MODELLAB_BLENDER": "your-value",
"MODELLAB_OUT": "your-value",
"MODELLAB_WAIT_FOR": "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": {
"modellab": {
"type": "stdio",
"command": "uvx",
"args": [
"modellab-mcp"
],
"env": {
"MODELLAB_BLENDER": "your-value",
"MODELLAB_OUT": "your-value",
"MODELLAB_WAIT_FOR": "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.
MODELLAB_BLENDER envMODELLAB_OUT envMODELLAB_WAIT_FOR envThese 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 hpdkhoa, 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.2.0) reached the registry 23 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) 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.
Model Lab
Game gun models drawn in Blender from parameters, rigged and checked against the real gun.
An MCP server that draws game gun models in Blender from a few parameters. Each build has real parts at real proportions, one bone a moving part, its clips, and the facts a game needs. Every build checks itself, and a second check measures its outline against a photo of the real gun.
Ask for "an M4A1 with a red dot and a light on the right rail" and Model Lab writes a rigged FBX, an FBX for each attachment, a .blend, a sheet of pictures and a facts.json with every mark in gun space. It tells you which checks failed, if any. It makes game models only: outside shapes and moving parts. It draws no working internals and writes no fabrication data.
| You get | What it is |
|---|---|
SK_ _Rig.fbx | the gun on its rig: Bolt, ChargingHandle, DustCover, BoltCatch, MagRelease, Selector, Trigger, ForwardAssist, Magazine, MagRound, Stock, each with its real pivot and travel |
SM_ _Magazine.fbx | the magazine alone, its origin on the feed lips, for the hand |
| one FBX an attachment | its origin on its recoil lug; SK_ when it has moving parts (folding sights, flip caps, a flip magnifier) |
.blend | everything, with the moving parts' cycle as an action |
facts.json | the marks (chamber, port, magazine well, feed lips, grip, support hand, muzzle, sights), the rails and their slots, the attachments and their sockets, the parts table, every check |
sheet.png | labelled views: both sides, the top, the front, close views, the open action, the sight picture |
Gun space: centimetres, +X the gun's left, +Y forward, +Z up. The origin is the bolt face at rest on the bore.
Model Lab needs Python 3.10 or later and Blender 4.2 or later.
uvx modellab-mcp
or
pip install modellab-mcp
Add it to your MCP client (Claude Code, Claude Desktop, or any client that runs stdio servers):
{
"mcpServers": { "modellab": { "command": "uvx", "args": ["modellab-mcp"], "env": { "MODELLAB_BLENDER": "C:/Program Files/Blender Foundation/Blender 4.2/blender.exe" } } } }
| Setting | What it does |
|---|---|
MODELLAB_BLENDER | Blender's executable. Leave it out when Blender is on the PATH or in its usual install folder. |
MODELLAB_OUT | The only folder Model Lab writes to. Defaults to ~/.modellab. |
MODELLAB_WAIT_FOR | Optional process names that hold the machine, such as UnrealEditor.exe,blender.exe. A build refuses to start while one runs. Off by default. |
MODELLAB_IDLE_OK | With MODELLAB_WAIT_FOR: parts of a command line that mark a long-lived worker (default poselab_mcp). Such a worker counts only while it is busy. |
| Tool | What it does |
|---|---|
list_presets | The ready guns: M4A1, M16A2, AR15, M4A1_Kitted, AR15_Optic. |
list_platforms, describe_params | The gun families and every parameter: its range or choices, its unit, its meaning, and the sources of the real numbers. |
list_attachments | Nine attachment classes for the rails and M-LOK slots. |
build_gun | Builds a gun from a preset or a platform, with any parameter changed. motion=true adds GIFs of the cycle. |
build_gun_clips | The gun's own clips on a build's rig, measured, one FBX and one GIF each. |
list_references, compare_to_reference | The real-gun check: a build's outline against a photo. |
list_builds, read_build | The builds so far and their facts. |
The same calls run from a shell: modellab presets, modellab build M4A1 stock_pos=2 name=MyM4, modellab clips , modellab compare. Run modellab help for the list.
A build reports each check with its value. The checks:
parts_complete). The parts table lists each part a person sees on the real gun and the features that make it read as that part: the charging handle's swept wings, finger hooks, latch and roll pin; the bolt catch's serrations; the castle nut's notches; the front sight base's bayonet lug, swivel and taper pins; and so on. A missing feature fails the build. Marks such as rail numbers are listed as texture, not shape.compare_to_reference draws the build's side outline at a reference photo's own scale. It lines the build up on the muzzle and the bore, measures both outlines column by column, and names the parts where they differ. The overlay shows the model in see-through red over the photo: dark photo showing through is real gun the model misses.
This check found the faults the self-checks could not: the lower 1.55 cm too far back, the front sight base 2.4 cm back and the wrong shape, the stock's outline, the magazine's curve, and the rail's height. Now no stretch of the gun's outline over 1.75 cm long is more than 1 cm off. Attachments are classes, not the photo's exact models, so the check keeps their outline apart.
The reference ships with the package: a photo of an M4A1 carbine from PEO Soldier, File:M4A1-flattop.jpg on Wikimedia Commons, in the public domain as a work of the US Federal Government. The check reads its scale from the rail's teeth, 0.394 in apart.
Each rail reports its slots at the Picatinny pitch (MIL-STD-1913), slot 0 at the rear. M-LOK handguards report their slots too (32 by 7 mm, 40 mm apart). Pass attachments by name, or as {item, rail, slot, state, options}:
{"preset": "M4A1", "params": {"attachments": [{"item": "flip_rear", "state": "down"}, "red_dot", "weapon_light"]}}
The nine classes: folding rear and front sights, the M4's carry handle, a 30 mm red dot with flip caps, a holographic sight, a 3x magnifier on a flip mount, a 4x32 prism sight, a vertical grip, a weapon light. A build checks that each fits its rail, clears the gun in every state, and clears the others as shown. When one blocks another's move, the build lists it: behind a magnifier, the rear sight goes up only after the magnifier swings aside.
Every .blend holds the cycle as an action. motion=true renders it as GIFs: the charging handle drawn back, the cover springing open, the carrier flying home, the magazine out and in, then the attachments' own moves.
build_gun_clips keys the gun's clips at 60 frames a second from real timings: charge, chamber check, fire (a 75 ms cycle), the last shot (the bolt held on its catch), reload, empty reload, and the stock's positions. Each clip is measured: every part on its own axis, the full stroke, the cover open before the carrier has moved 1 cm, the magazine out of the well and seated, the bolt held until the magazine is in.
The owner, 2026-10-21: "the grip is no sharp edge, this will be the next improvement for Model Lab when read on the manual or images, make the corner round a bit, especially the places that human grab and hold, most of the time they will no sharp edge because sharp edges will hurt the hand/human, make them softer so hand can hold it".
Why it matters, measured: on a digitized M1911A1 the grip safety was a square extrusion. A hand placed on the grip had the safety's edge 0.42 cm in its palm (the palm gives 0.27 cm). Rounding the grip parts by 0.75 mm, the least MIL-STD-1472G 5.7.7.6 allows, cut that to 0.09 cm past the give. Red: before (sharp). Blue: after (rounded). Below, close-ups of the spot before and after.
describe_params lists every source and every estimate.M-LOK is a trademark of Magpul Industries. Model Lab draws M-LOK slots to their published dimensions and is not connected with Magpul. AR-15 is a trademark of Colt's Manufacturing; here it names the rifle family in its common sense. Military designations (M4A1, M16A2, M68) name the guns and parts Model Lab copies. No product is endorsed.
MIT. See LICENSE.