Figma Mcp Bridge (maxisoft) MCP Server

@maxisoft/figma-mcp-bridge npm v0.12.1

Published by @maxisoft — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server that bridges Figma plugin data to AI tools without hitting API rate limits

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 81

Each tool and what it can reach — statically extracted from the published source.

  • get_dev_jsonreads sensitive data
  • list_filesreads sensitive data
  • analyze_node_against_designno sensitive capability
  • apply_aria_labelsno sensitive capability
  • apply_design_systemno sensitive capability
  • apply_style_presetno sensitive capability
  • batch_mutationno sensitive capability
  • bulk_renameno sensitive capability
  • bulk_swap_textno sensitive capability
  • create_componentno sensitive capability
Show 71 more tools ↓
  • create_design_token_aliasno sensitive capability
  • create_effect_styleno sensitive capability
  • create_frameno sensitive capability
  • create_grid_styleno sensitive capability
  • create_imageno sensitive capability
  • create_instanceno sensitive capability
  • create_paint_styleno sensitive capability
  • create_shapeno sensitive capability
  • create_styles_tableno sensitive capability
  • create_textno sensitive capability
  • create_text_styleno sensitive capability
  • create_variableno sensitive capability
  • create_variable_collectionno sensitive capability
  • delete_nodesno sensitive capability
  • diff_layoutsno sensitive capability
  • duplicate_nodesno sensitive capability
  • export_design_tokensno sensitive capability
  • export_icon_spriteno sensitive capability
  • extract_design_systemno sensitive capability
  • figma_inspectno sensitive capability
  • find_nodes_by_variableno sensitive capability
  • generate_codeno sensitive capability
  • generate_component_from_descriptionno sensitive capability
  • get_component_variantsno sensitive capability
  • get_constraintsno sensitive capability
  • get_design_contextno sensitive capability
  • get_dev_cssno sensitive capability
  • get_dev_htmlno sensitive capability
  • get_dev_imageno sensitive capability
  • get_dev_svgno sensitive capability
  • get_documentno sensitive capability
  • get_imageno sensitive capability
  • get_layout_measurementsno sensitive capability
  • get_metadatano sensitive capability
  • get_nodeno sensitive capability
  • get_node_metadatano sensitive capability
  • get_screenshotno sensitive capability
  • get_selectionno sensitive capability
  • get_selection_chainno sensitive capability
  • get_set_property_valueno sensitive capability
  • get_stylesno sensitive capability
  • get_variable_defsno sensitive capability
  • go_to_nodeno sensitive capability
  • import_design_tokensno sensitive capability
  • inspect_nodeno sensitive capability
  • inspect_variablesno sensitive capability
  • lint_stylesno sensitive capability
  • list_componentsno sensitive capability
  • manage_manifestsno sensitive capability
  • manage_snapshotsno sensitive capability
  • normalize_layersno sensitive capability
  • normalize_spacingno sensitive capability
  • reparent_nodesno sensitive capability
  • save_node_jsonno sensitive capability
  • save_screenshotsno sensitive capability
  • set_constraintsno sensitive capability
  • set_effectsno sensitive capability
  • set_gradient_fillno sensitive capability
  • set_instance_propertiesno sensitive capability
  • set_node_metadatano sensitive capability
  • set_node_propertiesno sensitive capability
  • set_node_visibilityno sensitive capability
  • set_strokeno sensitive capability
  • set_text_contentno sensitive capability
  • set_text_propertiesno sensitive capability
  • set_z_index_strategyno sensitive capability
  • spec_importno sensitive capability
  • storybook_importno sensitive capability
  • switch_themeno sensitive capability
  • update_component_instancesno sensitive capability
  • visualize_layoutno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.12.1 latest A 96/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/maxisoft-figma-mcp-bridge/badge.svg)](https://mcptrustchecker.com/registry/maxisoft-figma-mcp-bridge)
HTML
<a href="https://mcptrustchecker.com/registry/maxisoft-figma-mcp-bridge"><img src="https://mcptrustchecker.com/registry/maxisoft-figma-mcp-bridge/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/maxisoft-figma-mcp-bridge/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @maxisoft/figma-mcp-bridge --online

Use the free API → How scoring works

Other implementations of Figma Mcp Bridge 4

Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →

More in Design & Media