Back to MCP Trust Indexm8ven
39
/ 100
14 days ago
glama

Figma Native MCP

A local MCP server that lets MCP clients inspect and edit the Figma document currently open in the Figma desktop app using a local bridge and development plugin.

→ tomasmarekk/native-figma-mcp· listed on glama
Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 6 credentials: FIGMA_ACCESS_TOKEN, FIGMA_MCP_BRIDGE_TOKEN, FIGMA_OAUTH_TOKEN, FIGMA_PERSONAL_ACCESS_TOKEN, FIGMA_TEST_FILE_KEY, FIGMA_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
🔐 secretFIGMA_ACCESS_TOKEN— , FIGMA_PERSONAL_ACCESS_TOKEN, FIGMA_TOKEN empty Figma personal-token aliases
configFIGMA_API_BASE_URL
configFIGMA_MCP_ASSET_HOSTS— empty Comma-separated exact HTTPS hostnames for remote images
configFIGMA_MCP_ASSET_ROOTS— empty Allowed local asset roots, separated by the OS path delimiter
configFIGMA_MCP_BRIDGE_HOST— 127.0.0.1 Loopback host; only 127.0.0.1, localhost, or ::1
configFIGMA_MCP_BRIDGE_ONLY— 0 Run HTTP bridge without MCP stdio
configFIGMA_MCP_BRIDGE_PORT— 3845 Bridge port; the development manifest permits 3845
🔐 secretFIGMA_MCP_BRIDGE_TOKEN— $env: = (npm run --silent generate-token).Trim()
configFIGMA_MCP_ENABLE_PLUGIN_EVAL— 0 Enable arbitrary plugin-context JavaScript
configFIGMA_MCP_ENABLE_REST— 0 Expose optional Figma REST tools
configFIGMA_MCP_MAX_ASSET_BYTES— 10485760 Maximum image size
configFIGMA_MCP_MAX_REST_RESPONSE_BYTES— 26214400 Maximum buffered Figma REST response
configFIGMA_MCP_PLUGIN_CLIENT_STALE_MS— 60000 Plugin client staleness threshold
configFIGMA_MCP_PLUGIN_TIMEOUT_MS— 30000 Plugin command timeout
configFIGMA_MCP_TIMEOUT_MS— 30000 REST and asset timeout
configFIGMA_MCP_WATCH_FORCE_ACTIVE
configFIGMA_MCP_WATCH_INACTIVE_GRACE_MS— 4000 Delay before owned bridge shutdown
configFIGMA_MCP_WATCH_LOG_BACKUPS
configFIGMA_MCP_WATCH_LOG_MAX_BYTES
configFIGMA_MCP_WATCH_POLL_MS— 2000 Watcher poll interval
configFIGMA_MCP_WATCH_PROCESS_NAMES— Figma.exe Windows watcher process list
🔐 secretFIGMA_OAUTH_TOKEN— empty Figma OAuth bearer token
🔐 secretFIGMA_PERSONAL_ACCESS_TOKEN— FIGMA_ACCESS_TOKEN, , FIGMA_TOKEN empty Figma personal-token aliases
🔐 secretFIGMA_TEST_FILE_KEY— "SYNTHETIC_FILE_KEY" \
configFIGMA_TEST_NODE_ID
configFIGMA_TEST_URL
🔐 secretFIGMA_TOKEN— FIGMA_ACCESS_TOKEN, FIGMA_PERSONAL_ACCESS_TOKEN, empty Figma personal-token aliases
configFIGMA_VERIFY_MUTATION_PREFIX
configFIGMA_VERIFY_PLUGIN_TIMEOUT_MS
configFIGMA_VERIFY_REST_DEPTH
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/tomasmarekk-native-figma-mcp-5y339i)](https://m8ven.ai/mcp/tomasmarekk-native-figma-mcp-5y339i)
commit: 9b4bf1dc7294739dc8e7d7c68253591190d74ed6
code hash: 15cfe42efd512d0ae748a20f715ae29db5c651e043ec51afc4611f688a554a7a
verified: 7/17/2026, 8:28:39 AM
view raw JSON →