Developer · Local MCP server
Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.GLips/Figma-Context-MCP- Version
- 0.13.2
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-06-18
- Updated
- 2026-06-18
- Publisher
- GLips (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/GLips) · how
- Listed under
- Figma MCP servers
- Repository
- github.com/GLips/Figma-Context-MCP
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | figma-developer-mcp | 0.13.2 | stdio |
How to connect Figma Context MCP
Figma Context MCP runs locally from a Node.js package published to the npm registry: figma-developer-mcp version 0.13.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y figma-developer-mcp@0.13.2. It reads the environment variable FIGMA_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"figma-context-mcp": {
"command": "npx",
"args": [
"-y",
"figma-developer-mcp@0.13.2"
],
"env": {
"FIGMA_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| FetchSandboxA deterministic verification engine for agents. Proves a fix: fails on the old code, passes on new. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| FetchV2Fetch and extract web pages, discover links, and read llms.txt documentation indexes. | Local · stdio |
| Fetter MCPReal-time Python package and vulnerability data for AI coding agents. | Remote · HTTPLive check: ✓ handshake |
| FettleUptime monitoring for developers - monitors, incidents, heartbeats and status pages. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Figma MCP RustFigma MCP server in Rust: plugin bridge, no API token, no rate limits, 73 tools. | Local · stdio |
| Figma MCP RustFigma MCP server in Rust: plugin bridge, no API token, no rate limits, 73 tools. | Local · stdio |
| figma-mcpFigma to pixel-perfect code: deterministic HTML/React, then a render + pixel-diff verify loop. | Local · stdio |
| FilesSandboxed local filesystem: read, search, edit, copy, archive, and safely manage files. | Local · stdio |