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 a paste-ready embed for a floating 3D avatar chatbot on any website.
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.
THREE_WS_BASEYou 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": {
"assistant-widget": {
"command": "npx",
"args": [
"-y",
"@three-ws/assistant-mcp"
],
"env": {
"THREE_WS_BASE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add assistant-widget --env THREE_WS_BASE=your-value -- npx -y @three-ws/assistant-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"assistant-widget": {
"command": "npx",
"args": [
"-y",
"@three-ws/assistant-mcp"
],
"env": {
"THREE_WS_BASE": "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": {
"assistant-widget": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@three-ws/assistant-mcp"
],
"env": {
"THREE_WS_BASE": "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.
THREE_WS_BASE 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 nirholas, 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.2) reached the registry 26 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.
@three-ws/assistant-mcp
Generate a paste-ready three.ws assistant widget, a floating 3D avatar chatbot for any website, from any AI agent.
A Model Context Protocol server that lets any AI assistant build a paste-ready embed for the three.ws assistant widget over stdio. Describe how you want the assistant to look and behave and
build_assistant_widgetreturns a ready-to-pastetag, a standalone frame URL forembedding, and an equivalentThreeAssistant.init({...})JavaScript-API snippet, a floating 3D avatar chatbot that lives in the corner of any site.list_assistant_optionsenumerates every built-in avatar, background preset, interaction mode, chat lane, anddata-*attribute you can set.
Both tools are pure and offline: building an embed is deterministic string logic over local validators. Every field is validated and clamped, so a bad or hostile value falls back to a safe default and the generated HTML is always well-formed. No API key, no signer, no payment, no network call. Point THREE_WS_BASE at a deployment (or leave the default) and go.
npm install @three-ws/assistant-mcp
Or run with npx (no install):
npx -y @three-ws/assistant-mcp
Claude Code, one line:
claude mcp add assistant -- npx -y @three-ws/assistant-mcp
Claude Desktop / Cursor (claude_desktop_config.json or mcp.json):
{
"mcpServers": { "assistant": { "command": "npx", "args": ["-y", "@three-ws/assistant-mcp"] } } }
Inspect the surface with the MCP Inspector:
npx -y @modelcontextprotocol/inspector npx @three-ws/assistant-mcp
| Tool | Type | What it does |
|---|---|---|
build_assistant_widget | read-only | A config → a paste-ready embed (non-default settings as data-*), a frame URL, a ThreeAssistant.init() snippet, and the normalized config. |
list_assistant_options | read-only | Enumerate every built-in avatar, background preset and grammar, interaction mode, chat lane, and the full data-* attribute reference. |
build_assistant_widget is a pure function: the same config always yields the same embed, and it never touches the network. The generated tag carries only the settings that differ from their defaults, so a minimal config yields a minimal tag. The frame_url carries every resolved value (including defaults) so the standalone frame renders deterministically when dropped into an .
`build_assistant_widget`, all optional:
| Field | Type / values | Default | |||
|---|---|---|---|---|---|
avatar | avatar id, /avatars/*.glb path, or GLB URL | mannequin | |||
agent | a three.ws agent id (alternative to avatar) | (none) | |||
background | transparent \ | #hex \ | ember/ocean/violet/forest/dusk/slate \ | gradient:#a,#b[,angle] | transparent |
mode | chat \ | speak \ | both | both | |
name | string (≤ 60) | (none) | |||
greeting | string (≤ 200) | (none) | |||
context | string (≤ 500), what the assistant should know about the site | (none) | |||
accent | #hex | #f97316 | |||
position | right \ | left | right | ||
voice | boolean, start with voice on/off | on | |||
badge | boolean, show the three.ws attribution badge | on |
Any value that fails validation (a bad hex, an unknown background, an over-long string) falls back to its default rather than being rejected, so you always get a working embed.
`list_assistant_options`, filter (optional: avatars \| backgrounds \| modes \| chat_lanes \| attributes). Omit to get everything.
// build_assistant_widget
{
"avatar": "/avatars/selfie-girl.glb", "background": "ocean", "mode": "both", "name": "Aria", "greeting": "Hi! Ask me anything about the site.", "accent": "#00c2ff", "position": "left" } { "ok": true, "snippet": " ", "frame_url": "https://three.ws/assistant-frame?avatar=%2Favatars%2Fselfie-girl.glb&bg=ocean&mode=both&name=Aria&greeting=Hi%21+Ask+me+anything+about+the+site.&accent=%2300c2ff", "js_api": "ThreeAssistant.init({\n \"bg\": \"ocean\",\n \"mode\": \"both\",\n \"accent\": \"#00c2ff\",\n \"position\": \"left\",\n \"avatar\": \"/avatars/selfie-girl.glb\",\n \"name\": \"Aria\",\n \"greeting\": \"Hi! Ask me anything about the site.\"\n});", "builder_url": "https://three.ws/assistant", "config": { "bg": "ocean", "mode": "both", "accent": "#00c2ff", "position": "left", "avatar": "/avatars/selfie-girl.glb", "name": "Aria", "greeting": "Hi! Ask me anything about the site." }, "notes": "Chat runs on the free three.ws LLM chain by default (no key). Visitors can paste their own Groq or OpenRouter key in the widget settings for a private lane; that key stays in their browser." }
Paste the snippet before on any page, or drop the frame_url into an . Design it visually first at three.ws/assistant.
THREE_WS_BASE only sets the origin baked into the generated URLs.| Variable | Required | Default |
|---|---|---|
THREE_WS_BASE | no | https://three.ws |
The package entry point exports `TOOLS` (every tool definition: name, title, description, inputSchema, annotations, handler) and `buildServer()`, which returns a fully-registered McpServer with no transport attached. Both tools are pure and offline, so you can call them directly as a widget-builder library with no MCP client involved.
// run from a checkout: node this-file.mjs
import { TOOLS, buildServer } from '@three-ws/assistant-mcp';
const build = TOOLS.find((t) => t.name === 'build_assistant_widget'); const { snippet } = await build.handler({ avatar: '/avatars/michelle.glb', background: 'dusk' }); console.log(snippet);
// Or hand the whole registered server to your own MCP transport. buildServer();
<script src="https://three.ws/assistant/v1.js" async data-avatar="/avatars/michelle.glb" data-bg="dusk"></script>
Part of the three.ws SDK suite, 3D AI agents, on-chain identity, and agent payments.
Website · Changelog · GitHub