Figma Vector MCP
NPM · FIGMA-VECTOR-MCP
Let Claude create and edit fully editable vector nodes on the Figma canvas.
Available components
Last scanned (1 hour ago)
Scores higher than 36% of npm servers
Category Design and Media
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects uuid 10.0.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 94 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3967 tokens (~68/item across 58 items; 58 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 68% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_node" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 58 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 46
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Analysed npm/figma-vector-mcp@0.3.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Deprecated | 1 |
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
set_layout_grid ~41
Apply column, row, or uniform grid guides to a frame.
| Name | Type | Req | Description |
|---|---|---|---|
| grids | array | yes | – |
| nodeId | string | yes | Figma node ID |
No output schema declared.
No examples provided.
set_opacity ~47
Set the opacity of a Figma node (0 = invisible, 1 = fully opaque).
| Name | Type | Req | Description |
|---|---|---|---|
| nodeId | string | yes | Figma node ID |
| opacity | number | yes | – |
No output schema declared.
No examples provided.
set_stroke ~111
Set comprehensive stroke properties on a node: color, weight, position, dash pattern, line cap, and line join.
| Name | Type | Req | Description |
|---|---|---|---|
| color | object | – | Stroke color |
| dashPattern | array | – | Dash pattern e.g. [8, 4] for dashed |
| lineCap | string | – | – |
| lineJoin | string | – | – |
| nodeId | string | yes | Figma node ID |
| position | string | – | Stroke alignment |
| weight | number | – | Stroke width in pixels |
No output schema declared.
No examples provided.
set_stroke_color ~87
Set the stroke color (and optional weight) of a Figma node.
| Name | Type | Req | Description |
|---|---|---|---|
| a | number | – | – |
| b | number | yes | Blue 0–1 |
| g | number | yes | Green 0–1 |
| nodeId | string | yes | Figma node ID |
| r | number | yes | Red 0–1 |
| weight | number | – | – |
No output schema declared.
No examples provided.
set_text_style ~159
Modify typographic properties of an existing text node without replacing its content. Also use to set or update text box width and wrapping.
| Name | Type | Req | Description |
|---|---|---|---|
| fillColor | object | – | – |
| fontFamily | string | – | – |
| fontSize | number | – | – |
| fontStyle | string | – | e.g. Regular, Bold, Italic |
| height | number | – | Fix height in px (clips content) |
| letterSpacing | number | – | Letter spacing in pixels |
| lineHeight | – | – | Line height in pixels or 'AUTO' |
| nodeId | string | yes | Figma node ID |
| textAlign | string | – | – |
| textAutoResize | string | – | – |
| width | number | – | Fix column width in px to enable wrapping |
No output schema declared.
No examples provided.
set_visibility ~42
Show or hide a Figma node.
| Name | Type | Req | Description |
|---|---|---|---|
| nodeId | string | yes | Figma node ID |
| visible | boolean | yes | true = visible, false = hidden |
No output schema declared.
No examples provided.
switch_page ~50
Switch to a different page in the Figma document by ID or name.
| Name | Type | Req | Description |
|---|---|---|---|
| pageId | string | – | Page ID |
| pageName | string | – | Page name (used if pageId not provided) |
No output schema declared.
No examples provided.
ungroup_nodes ~34
Ungroup a group node, returning its children to the parent.
| Name | Type | Req | Description |
|---|---|---|---|
| nodeId | string | yes | Figma node ID |
No output schema declared.
No examples provided.
How do I install the Figma Vector MCP server?
Figma Vector MCP runs locally as an npm package, launched with npx -y figma-vector-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · figma-vector-mcp
claude mcp add workingmodel-figma-vector-mcp -- npx -y figma-vector-mcp
What is the Figma Vector MCP server?
Figma Vector MCP is listed in the public MCP registry as io.github.workingmodel/figma-vector-mcp. Let Claude create and edit fully editable vector nodes on the Figma canvas. This page covers its npm package (figma-vector-mcp).
Is the Figma Vector MCP server safe to use?
Figma Vector MCP scores 62 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 24 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Figma Vector MCP server expose?
Figma Vector MCP exposes 58 tools: join_channel, health_check, create_vector_from_svg, create_path, create_polyline, and 53 more. Their descriptions and schemas cost roughly 3,967 tokens of context every time the server is loaded.
Is the Figma Vector MCP server still maintained?
Figma Vector MCP is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Figma Vector MCP server under?
Figma Vector MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.