Figwright — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track Figma API and design-operation compatibility as the tool surface changes

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Two-way Figma inspection/editing workflows for coding agents

What we know

Community Figma MCP paired with a Figma plugin, exposing design inspection and two-way interaction.

Maintenance / activity evidence

Observed Oct 3, 2026 (UTC)chore(deps): update all non-major dependencies ( 266)

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Connected Figma document/plugin context. Complete write authority is not verified.
Authentication not yet verified.
Sensitive access: Figma documents

Connected design files may be sensitive and the project is described as two-way; verify exact mutation tools before broad deployment.

Security source · repository notice ↗Security source · policy file ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

976 repository stars

Stars observed Oct 6, 2026.

30-day package downloads intentionally left null because the package-stats provider ran out of credits during Batch 3 QA.

All limitations / Review context

Which Figma operations and client setup are currently documented?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

Connected design files may be sensitive and the project is described as two-way; verify exact mutation tools before broad deployment.
Connected Figma document/plugin context.
Design content passes through the plugin/server bridge.
Sensitive access: Figma documents
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
Exact write tools
Authentication
Exact write/tool scope is not fully established in this audit.
Auth model not documented.

Original activity observations

2026-10-03T18:12:42Z: chore(deps): update all non-major dependencies ( 266)

Technical identity

github.com/awdr74100/figwright

Exact implementation source: https://github.com/awdr74100/figwright ↗
Reviewed resource type: MCP Server
Repository identity: awdr74100/figwright
Package identity: npm:@figwright/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
awdr74100/figwright
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 12, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Register `npx -y @figwright/mcp@latest` in your client and install/open the Figwright Figma plugin; both components are required. Node.js 20.19+ or 22.12+.
Advanced configuration · mcp stdio launcher or diagnostic
mcp stdio launcher or diagnostic · Review before use
npx -y @figwright/mcp@latest
Configure / authenticate
Publisher instructions
Install the Figwright Figma plugin and open/connect it in Figma separately from the MCP server. The Node server requires Node 20.19+ or 22.12+ and is configured in your client as npx -y @figwright/mcp@latest; for offline/pinned environments prefer an explicitly installed executable.
Advanced configuration · claude desktop json
{ "mcpServers": { "figwright": { "args": [ "-y", "@figwright/mcp@latest" ], "command": "npx" } } }
Check connection
Suggested check
With Figma plugin open, inspect the Figwright MCP tools and run a ping or approved read-only inspection. If plugin remains Waiting, check whether the client spawned the server and whether the plugin-to-local-relay connection is working.
Remove / uninstall / revoke
Remove only the `figwright` entry from the MCP client and close/disable the Figwright plugin in Figma if no longer needed. Both components have independent lifecycle. In the MCP client settings remove only the `mcpServers.figwright` entry and restart/reload. This is a concrete client disconnect, separate from uninstalling the local package.

Official Documentation & Sources

What it does

Community Figma MCP paired with a Figma plugin, exposing design inspection and two-way interaction.

Capability: Design & Creative
Resource type: MCP Server
Best fit: Two-way Figma inspection/editing workflows for coding agents

Representative uses

Inspect selections/nodes
Read styles/typography
Take screenshots
Operate through plugin bridge

Limitations

Exact write/tool scope is not fully established in this audit.
Auth model not documented.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Connected Figma document/plugin context.
Data handling: Design content passes through the plugin/server bridge.
Cost: unknown
Risk and cautions: Connected design files may be sensitive and the project is described as two-way; verify exact mutation tools before broad deployment.

Access scope and cautions

Write actions: Not verified
Sensitive access: Figma documents
Risk level: moderate

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Inspect selections/nodes; Read styles/typography; Take screenshots; Operate through plugin bridge.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Connected Figma document/plugin context.

What data-handling boundary should I consider?

Design content passes through the plugin/server bridge. Recorded sensitive-access context: Figma documents.

What limitations and risks should I check before use?

Connected design files may be sensitive and the project is described as two-way; verify exact mutation tools before broad deployment. Exact write/tool scope is not fully established in this audit. Auth model not documented. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

awdr74100 is listed as Community implementation in MCP100’s current evidence.