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)
Reads a boat's Signal K data and helps an AI assistant design and install KIP dashboards.
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.
SIGNALK_HOST, SIGNALK_PORT, SIGNALK_TLS, SIGNALK_TOKEN, SIGNALK_USER, SIGNALK_PASSWORD, KIP_URLValues 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 …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"kip": {
"command": "npx",
"args": [
"-y",
"kip-mcp-server"
],
"env": {
"SIGNALK_HOST": "your-value",
"SIGNALK_PORT": "your-value",
"SIGNALK_TLS": "your-value",
"SIGNALK_TOKEN": "your-value",
"SIGNALK_USER": "your-value",
"SIGNALK_PASSWORD": "your-value",
"KIP_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add kip --env SIGNALK_HOST=your-value --env SIGNALK_PORT=your-value --env SIGNALK_TLS=your-value --env SIGNALK_TOKEN=your-value --env SIGNALK_USER=your-value --env SIGNALK_PASSWORD=your-value --env KIP_URL=your-value -- npx -y kip-mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"kip": {
"command": "npx",
"args": [
"-y",
"kip-mcp-server"
],
"env": {
"SIGNALK_HOST": "your-value",
"SIGNALK_PORT": "your-value",
"SIGNALK_TLS": "your-value",
"SIGNALK_TOKEN": "your-value",
"SIGNALK_USER": "your-value",
"SIGNALK_PASSWORD": "your-value",
"KIP_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": {
"kip": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"kip-mcp-server"
],
"env": {
"SIGNALK_HOST": "your-value",
"SIGNALK_PORT": "your-value",
"SIGNALK_TLS": "your-value",
"SIGNALK_TOKEN": "your-value",
"SIGNALK_USER": "your-value",
"SIGNALK_PASSWORD": "your-value",
"KIP_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.
SIGNALK_HOST envSIGNALK_PORT envSIGNALK_TLS envSIGNALK_USER envKIP_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 7, 2026
The registry name was verified with the GitHub account dillan, 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.
You need to fill in: SIGNALK_TOKEN, SIGNALK_PASSWORD
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 (1.12.0) reached the registry 5 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.
An MCP server that lets an AI assistant (such as Claude, Codex, or Gemini) look at your boat's Signal K data and help you design and install KIP dashboards — the gauges and panels you see on your chartplotter or tablet.
You stay in control: the assistant shows you a picture of each dashboard first, and it only saves anything to your boat after you say yes.
A short session with an AI assistant, after pointing it at your boat:
You: Look at my boat's data and suggest some KIP dashboards.
→ analyze_signalk_data 142 paths · speed, wind, depth, battery, engine → recommend_dashboard_set 6 dashboards the data supports
Assistant: Your boat reports navigation, wind, depth, electrical and engine data, so I can build these. Here's the "Sailing" one — a preview, nothing saved yet:
┌─────────────┬─────────────┬───────────────────────────┐ │ SOG 6.2 kn │ AWS 14 kn │ │ ├─────────────┼─────────────┤ wind steering │ │ DPT 8.4 m │ AWA 42° │ │ └─────────────┴─────────────┴───────────────────────────┘
You: Looks good — install the sailing and anchor ones.
→ apply_kip_config (dry run) 2 dashboards → KipConfig (global) Assistant: This will add "Sailing" and "Anchor" to KIP. Go ahead? You: Yes. → apply_kip_config written ✓ — open KIP to see them.
The assistant always shows a preview first and asks before writing anything to your boat.
You need a Signal K server running on your boat (or on your network), with KIP installed.
http://your-boat:3000. Note the host name (or IP) and port.npx (which comes with Node.js 24 or newer): npx -y kip-mcp-server
The next step wires this command into your assistant. (Prefer to build from source? See Develop below.)
KipConfig.json file to import from KIP's Settings instead.The server reads a few settings from its environment:
| Setting | What it is | Default |
|---|---|---|
SIGNALK_HOST | Your Signal K host name or IP | localhost |
SIGNALK_PORT | Your Signal K port | 3000 |
SIGNALK_TLS | Set to true if your server uses https | false |
SIGNALK_TOKEN | A Signal K login token, needed to write dashboards | (none) |
SIGNALK_USER | A Signal K username — used with SIGNALK_PASSWORD instead of a token | (none) |
SIGNALK_PASSWORD | The matching Signal K password | (none) |
KIP_URL | Override where KIP is served, if it's not the default | (derived) |
Reading your data needs no login. Writing dashboards to the server needs either a token or a username and password; you can always use the file-export option instead, which needs nothing extra. For how to get a token (or why a username/password is simpler), see Signal K authentication.
By default the server talks over stdio — the assistant runs it as a local subprocess. There is also an optional HTTP mode (kip-mcp-http) for hosting the server so a remote assistant (such as Claude.ai) can reach it over the network. It is opt-in and meant for a single operator behind a reverse proxy that adds TLS.
# Behind a TLS-terminating reverse proxy that forwards to 127.0.0.1:3017
MCP_BEARER_TOKEN=a-long-random-secret \ MCP_PUBLIC_URL=https://boat.example.com/mcp \ npx kip-mcp-http
| Setting | What it is | Default |
|---|---|---|
HTTP_HOST | Address to bind | 127.0.0.1 (loopback) |
HTTP_PORT | Port to listen on | 3017 |
HTTP_PATH | URL path for the MCP endpoint | /mcp |
MCP_BEARER_TOKEN | One or more (comma-separated) bearer tokens that callers must present | (none) |
MCP_PUBLIC_URL | The public URL clients reach, used for the Host allowlist and metadata | (derived) |
MCP_ALLOWED_ORIGINS | Comma-separated browser origins to accept (off by default) | (none) |
MCP_ALLOWED_HOSTS | Override the Host allowlist | (derived) |
MCP_ALLOW_INSECURE | Set to true to start anyway in an unsafe setup | (unset) |
Every request must present a valid Authorization: Bearer and pass a Host/Origin allowlist before it reaches the MCP layer. The server refuses to start if it would bind to a non-loopback address or run without a bearer token, unless you set MCP_ALLOW_INSECURE=true. It uses one Signal K login for all sessions, so treat it as a single-tenant deployment; the same SIGNALK_* settings above apply.
The server gives the assistant a set of tools, grouped by job:
review_dashboard prompt drives it, backed by a deterministic check_dashboard_ux lint.--doctor check.A few terms, in plain words:
navigation.speedOverGround (speed over ground).This project uses Node.js 24 (LTS). Common commands:
npm install # install dependencies
npm run typecheck # check types npm run lint # check code style npm test # run the tests npm run build # compile to dist/ npm run smoke # start the built server and check it answers npm run ci # run the full set of checks
For a full guide to running and testing the server locally during development — pointing an AI client or the MCP Inspector at a local build, running the HTTP transport, and testing against Signal K (or offline) — see docs/development.md.
Commits follow Conventional Commits; releases and version numbers are produced automatically from those commit messages.
MIT — see LICENSE.