Developer · Local MCP server
figma-mcp
Figma to pixel-perfect code: deterministic HTML/React, then a render + pixel-diff verify loop.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Mehmoodqureshi/figma-mcp- Version
- 0.2.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-26
- Updated
- 2026-09-26
- Publisher
- Mehmoodqureshi (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Mehmoodqureshi) · how
- Listed under
- Figma MCP servers
- Repository
- github.com/Mehmoodqureshi/figma-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @mehmoodqureshi/figma-mcp | 0.2.1 | stdio |
How to connect figma-mcp
figma-mcp runs locally from a Node.js package published to the npm registry: @mehmoodqureshi/figma-mcp version 0.2.1. 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 @mehmoodqureshi/figma-mcp@0.2.1. It reads these environment variables: FIGMA_TOKEN (required, secret) and FIGMA_MCP_CACHE_DIR; set them 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-mcp": {
"command": "npx",
"args": [
"-y",
"@mehmoodqureshi/figma-mcp@0.2.1"
],
"env": {
"FIGMA_TOKEN": "<secret>",
"FIGMA_MCP_CACHE_DIR": "<value>"
}
}
}
}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 from Mehmoodqureshi (GitHub)
| Server | Runs |
|---|---|
| chrome-mcpDrive your real Chrome over MCP: real logins and cookies, multi-tab automation, deny-all by default. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| FettleUptime monitoring for developers - monitors, incidents, heartbeats and status pages. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Figma Context MCPGive your coding agent access to your Figma data. Implement designs in any framework in one-shot. | Local · stdio |
| 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 |
| FilesSandboxed local filesystem: read, search, edit, copy, archive, and safely manage files. | Local · stdio |
| Files ComManage files, users, and automated workflows across cloud storage and protocols. | Local · stdio |
| FilesiftLocal file search for AI agents - semantic + keyword indexing over your codebase. | Local · stdio |
| FillTrust security questionnaire corpusGuidance for answering vendor security questionnaires. Every result carries the page it came from. | Remote · HTTPLive check: ✓ handshake |