Figsnap MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 11 installs a week from npm. Last commit 7 Sep 2026.
The Figma file you have open, as MCP tools. Extract, edit, and keep a saved set.
Today is the operative word: we check Figsnap MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add figsnap-mcp -- npx -y figsnap-mcp
{
"mcpServers": {
"figsnap-mcp": {
"command": "npx",
"args": [
"-y",
"figsnap-mcp"
]
}
}
}
[mcp_servers.figsnap-mcp]
command = "npx"
args = ["-y", "figsnap-mcp"]
{
"mcpServers": {
"figsnap-mcp": {
"command": "npx",
"args": [
"-y",
"figsnap-mcp"
]
}
}
}
{
"servers": {
"figsnap-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"figsnap-mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
FIGSNAP_MCP_URL (Where the figsnap-mcp daemon is listening. Default http://127.0.0.1:3058; only needed if you moved it), FIGSNAP_MCP_TOKEN (The daemon's token. Not normally set: the server reads ~/.figsnap-mcp/agent-token, which the daemon writes itself).
Figma MCP: list frames in a file and fetch one frame's JSON and image safely. 2 tools.
Let Claude create and edit fully editable vector nodes on the Figma canvas.
Read, edit and export the Figma file open in a local plugin. No REST API, no rate limits.
Local-first open-source AI media workbench with Canvas, video editor, Assets, and MCP tools.
Two-way Figma MCP: extract + verify design-to-code, or generate on-brand Figma pages from a prompt.
Read and edit a live DAG Studio canvas through its predefined WebMCP tools.
Audit your Design System and serve your Agent the rules that keep AI-written UI on-system.
MCP server for the Frame-Relay design kit: components, tokens and live Figma selections.
Answers built from our own checks of this server.