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)
Author, ROM-validate, and render 3D human movement (.posecode) with a shareable playground link.
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.
POSECODE_BASE_URLYou 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": {
"posecode": {
"command": "npx",
"args": [
"-y",
"posecode-mcp"
],
"env": {
"POSECODE_BASE_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add posecode --env POSECODE_BASE_URL=your-value -- npx -y posecode-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"posecode": {
"command": "npx",
"args": [
"-y",
"posecode-mcp"
],
"env": {
"POSECODE_BASE_URL": "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": {
"posecode": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"posecode-mcp"
],
"env": {
"POSECODE_BASE_URL": "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.
POSECODE_BASE_URL 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 6, 2026
The registry name was verified with the GitHub account posecode-dev, 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.5.0) reached the registry 2 months 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.
Posecode
Kinematic motion as text.
An inspectable, editable movement format for animation tools, LLMs, and web products.
Like Mermaid for movement: small text documents for describing, validating, and rendering
deterministic human motion without hiding the source inside a black box.
Live Playground · Movement Library · Language Specification (SPEC.md) · LLM Authoring Guide · Examples · MCP Server
Animation clips and generated trajectories can show movement, but they often hide the semantic decisions that produced it.
Posecode keeps those decisions in readable source. A human can write the document, an animation tool can emit it, or an LLM can draft it. Parsing, validation, editing, and rendering do not require an AI model.
One .posecode document — shoulders: abduct 160 , hips: abduct 30 , repeat 12 — rendered live in the browser.
For example:
Bend your knees, move your hips backward, and keep your chest upright.
A human may understand that instruction, but a renderer cannot reliably determine:
Humans, tools, and language models all need a shared syntax for expressing movement in a renderable and testable form.
Posecode provides that missing representation.
From readable movement source to validated 3D rendering, MCP tools, and a one-script web embed.
▶ Watch the 28-second builder demo
Plain text in. Smooth, programmable 3D motion out.
pelvis: hinge — deadlift
knees: flex 95 — squat
shoulders: abduct 90 — lateral raise
Neural text-to-motion systems can generate impressive movement, but they introduce problems for lightweight, programmable applications.
Many systems require large models and GPU-backed inference, making real-time consumer deployment expensive.
They usually produce coordinate trajectories rather than editable semantic instructions.
It is difficult to request a precise change such as:
Reduce knee flexion by 10 degrees during the second phase.
Black-box trajectories do not naturally expose readable joint rules, phase definitions, or range-of-motion limits.
When a movement looks wrong, developers may not know which semantic instruction caused the problem.
Posecode uses a lightweight, text-driven pipeline.
.posecode documents.A .posecode file describes movement as timed phases with targeted joint actions.
1. Write .posecode | 2. Render the movement |
|---|
| `posecode` exercise "Body-weight squat" `rig` humanoid `pose` start = standing
`step` "Descend" 1.6s settle: hips: flex 80 knees: flex 95 ankles: dorsiflex 14 ground-lock: feet cue "Sit the hips back"
`step` "Drive up" 1.2s drive: hips: flex 0 knees: flex 0 ankles: dorsiflex 0 ground-lock: feet
`repeat` 8 | |
OpenAI Build Week 2026: Posecode existed before the hackathon. During Build Week, the project was extended using Codex — running on GPT-5.6 — as the primary engineering tool for a real batch of shipped work: motion/grounding quality, language contract diagnostics, licensing restructuring, release automation, and product-facing pages. The sections below distinguish previous work from Build Week work using actual commit history, not a roadmap.
Before Build Week, Posecode already included:
.posecode domain-specific language,This original version was developed primarily with Claude as an AI-assisted engineering tool.
That prior work provides the foundation for the project, but it is not presented as the new hackathon contribution.
Every item below is a merged, dated pull request built with Codex (GPT-5.6) — see Build Week Evidence for direct links.
drive/settle/flow/snap), a parser validation CLI, and embed compatibility metadata (#62)./for-products page documenting the web component, parser, renderer, and MCP server for integrators (#82, #74).During Build Week, Codex sessions ran on GPT-5.6 (GPT-5.6 Terra), which is the model that powers Codex for this event. GPT-5.6 is the reasoning engine behind every Build Week change listed above: reading the existing monorepo, proposing the ROM-constrained IK and contact-surface design in #76, designing the language/IR v0.3 diagnostics in #92, and drafting the licensing boundary in #84.
A GPT-5.6-powered natural-language-to-Posecode generation feature (describe a movement in plain English, get a validated .posecode document back) is a natural next step given the existing posecode_authoring_guide MCP tool, but it is not yet built — it is not claimed as shipped functionality here.
Codex is the primary engineering tool used for the Build Week extension.
During the hackathon period, Codex was used to:
Only the beginning is shown; read the rest in the repo