yasuda-figma-mcp
A read-only Figma MCP server for GitHub Copilot that renders screenshots locally inside Figma via exportAsync, avoiding any public S3 URLs or outbound HTTP. It provides 9 tools to inspect Figma files, components, variables, and FigJam boards through a private tunnel.
Caution. Specific findings reduced this grade. They are listed on the page. 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
Rikuto-des
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.
yfigma_get_screenshotRender the current selection or a specific node in the user's running Figma app as a PNG/JPG — exactly like right-click -> Copy as PNG. The image is produced locally and returned inline; it is never uploaded to S3 or any public URL.
yfigma_get_metadataReturn a compact tree of the selection or a node: id, name, type, position and size for each node and its descendants. Use this first to discover node ids cheaply before requesting heavier context.
yfigma_get_design_contextReturn a deep, structured representation of the selection or a node for implementing it as code: layout (auto-layout, constraints, padding, spacing), styles (fills, strokes, effects, corner radius, opacity), typography, text content, component/instance info and bound design-token variables. This is …
yfigma_get_variable_defsReturn design-token variables (with values resolved per mode) and their collections. Scope to a node/selection to get only the variables it binds, or use scope=all for every local variable in the file.
yfigma_search_design_systemSearch components, component sets and styles (paint/text/effect) in the current file by name substring. Returns matching names with their node ids and published keys where available.
yfigma_get_librariesList design-system libraries available to this file. Note: the Figma plugin API only exposes team-library VARIABLE collections, so component-library enumeration is limited compared to the official MCP. Returns what the local API can see plus a note.
yfigma_get_figjamSerialize a FigJam board: sticky notes, shapes-with-text, text, sections, tables and connectors with their text and geometry. Operates on the selection or the whole current page.
yfigma_get_document_infoReturn high-level context about the open file: file name, editor type, list of pages, the current page, and a summary of the current selection (ids, names, types).
yfigma_whoamiReturn the current Figma user (id, name) as reported by the running app, plus the open file and page. Useful to confirm the plugin is connected to the expected account/document.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
ws: Memory exhaustion DoS from tiny fragments and data chunks
ws: Uninitialized memory disclosure
BRIDGE_CHANNEL"": "default"BRIDGE_EMBED1 makes the MCP host the bridge in-process, so there's no separate bridge to start. (Local VS Code, no Codespaces secret? Add "BRIDGE_TOKEN": "<your-token>" to this env block instead.)BRIDGE_PORT"": "3055",BRIDGE_TOKEN…or via CLI: gh secret set --user --app codespaces (paste the value when prompted)BRIDGE_URL"": "ws://127.0.0.1:3055",FIGMA_EXPORT_DIRREQUEST_TIMEOUT_MSTool 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
9/9 tools missing one or more hints — yfigma_get_screenshot (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); yfigma_get_metadata (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); yfigma_get_design_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 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.
Tool inputs are validated
5/9 tool handlers declare input schemas (56%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Tests exist
No test files found
Add tests that exercise each declared tool.
Production dependencies are patched
0 critical, 1 high severity in production deps — ws@8.18.0 (high), ws@8.18.0 (low)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
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/rikuto-des/yasuda-figma-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