Figma MCP Server
A local MCP server with full Figma REST API coverage. Works with Claude Desktop, Cursor, VS Code, the Gemini CLI, and any MCP client. Available on npm and the official MCP Registry.
接入你的智能体
发布者自己的命令。不是 PlugMCP 端点。
用我们的密钥与日志托管一份副本。
npx -y [email protected]Claude Code 没有针对本地命令的安装链接。复制下方命令并在终端中运行。
FIGMA_API_KEY=<secret> claude mcp add planetabhi-figma-mcp-server -- npx -y figma-mcp-server@3.1.3在终端中运行。
{ "mcpServers": { "planetabhi-figma-mcp-server": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "FIGMA_API_KEY": "<secret>" } } }}claude_desktop_config.json
远程 URL 还是本机命令? 两种安装方式的区别
来自发布者
A local MCP server with full Figma REST API coverage. Works with Claude Desktop, Cursor, VS Code, the Gemini CLI, and any MCP client. Available on npm and the official MCP Registry.
A local Figma MCP server with full Figma REST API coverage
Each Figma REST endpoint is exposed as one self-describing MCP tool, auto-discovered at startup from tools/figma/, so adding an endpoint is just adding a file. Required parameters are validated before each call. It runs over stdio.
Requires Bun ≥ 1.2. It's Bun-native, so launch it with bunx, not npx (Node isn't supported).
Create a personal access token in Figma under Settings > Security > Personal access tokens > Generate new token. Provide it as FIGMA_API_KEY, ideally in your client config's env block (see below).
Every client uses the same server. Point command at bunx, or its absolute path (which bunx) if the client cannot find it on PATH.
{
"mcpServers": {
"figma": {
"command": "bunx",
"args": ["figma-mcp-server"],
"env": {
"FIGMA_API_KEY": "your_figma_api_key_here"
}
}
}
}
Config file locations:
claude_desktop_config.json)~/.cursor/mcp.json, or .cursor/mcp.json per project~/.gemini/settings.jsonRestart the client after editing its config.
Use .vscode/mcp.json (workspace) or your user mcp.json, with a servers key. Instead of hardcoding the token, define an input so VS Code prompts for it securely:
{
"inputs": [
{
"type": "promptString",
"id": "figma-api-key",
"description": "Figma API Key",
"password": true
}
],
"servers": {
"figma": {
"command": "bunx",
"args": ["figma-mcp-server"],
"env": {
"FIGMA_API_KEY": "${input:figma-api-key}"
}
}
}
}
${input:figma-api-key}, VS Code prompts you for the key the first time the server starts, then stores it in your OS secret storage.Full coverage of the Figma REST API (non-deprecated endpoints), 50 tools across:
Check your MCP client's tool list for the full, always-current list of tool names and parameters.
Most tools work with any plan's personal access token. These need higher tiers:
list_file_variables, get_published_variables, modify_variables): Enterprise organization.get_library_*): Organization or Enterprise plan.MIT License · By @planetabhi ⋛⋋( ⊙◊⊙)⋌⋚
A local Figma MCP server with full Figma REST API coverage
{ "mcpServers": { "planetabhi-figma-mcp-server": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "FIGMA_API_KEY": "<secret>" } } }}工具
暂无工具列表。远程服务器在首次健康检查后会获得工具列表。
常见问题
在本页复制适用于 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 配置。它使用发布者的安装方式,而不是 PlugMCP 代理。
发布者列出了以下环境变量:FIGMA_API_KEY。
Figma 通过 stdio 在本地运行。
上次检查时间:2026-10-27。 A local Figma MCP server with full Figma REST API coverage