Figma MCP Server by Bao To
Enables AI agents to extract design systems, analyze components, and maintain design-code consistency from Figma files, providing intelligent component analysis and accessibility compliance.
Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
tothienbao6a0
Source: Glama
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. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
get_figma_dataWhen the nodeId cannot be obtained, obtain the layout information about the entire Figma file
download_figma_imagesDownload SVG and PNG images used in a Figma file based on the IDs of image or icon nodes
get_figma_variablesRetrieves all variables and variable collections from a Figma file. Variables are different from design tokens - they are Figma's dynamic values system that can store colors, numbers, strings, and booleans with different modes/themes.
generate_design_tokensExtracts design tokens (colors, typography, spacing, effects) from a Figma file and saves them as a JSON file.
generate_design_system_docGenerates a comprehensive set of Markdown documents detailing the design system from a Figma file into a specified directory.
compare_design_tokensCompare design tokens between two Figma files or token sets to identify changes, additions, and removals.
validate_design_systemValidate design tokens against design system best practices and rules.
check_accessibilityCheck design tokens for accessibility compliance issues (contrast, text sizes, etc.).
migrate_tokensConvert design tokens to different formats (Tailwind, CSS Variables, Style Dictionary, Figma Tokens).
check_design_code_syncCompare Figma design tokens with code tokens to identify sync issues between design and implementation.
analyze_figma_componentsAnalyzes Figma components to understand structure, variants, and relationships for intelligent AI-driven code generation. This tool helps AI agents understand component semantics, props, variants, and implementation patterns.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
js-yaml: YAML merge-key chains can force quadratic CPU consumption
JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported
FIGMA_API_KEYPORTTool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
11/11 tools missing one or more hints — get_figma_data (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); download_figma_images (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_figma_variables (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Descriptions match behaviour
1 tool describes read intent but its handler mutates — check_accessibility (line 564: fsPromises.writeFile(outputFilePath, JSON.stringify(issues, null, 2), 'utf-8'))
Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.
Tool inputs are validated
Only 1/11 tool handlers declare input schemas (9%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Tool test coverage
Only 1/11 tools referenced in tests (9%)
Write tests that reference each tool by name so every tool has at least one test.
Production dependencies are patched
0 critical, 17 high severity in production deps — @modelcontextprotocol/sdk@1.11.4 (high), @modelcontextprotocol/sdk@1.11.4 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Tool description accuracy
check_accessibility: description implies read-only but handler writes/deletes/executes
Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/tothienbao6a0/figma-context-mcp)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check