Talk to Figma MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow Figma API and tool-permission changes affecting design automation

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

Best fit

Reading and programmatically modifying Figma documents through an AI client.

What we know

Talk to Figma MCP connects AI clients to Figma through an MCP server, a Figma plugin and a WebSocket bridge.

Maintenance / activity evidence

Observed Jul 26, 2026 (UTC)feat: add set image fill, rename node, create section and set parent …

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

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Can inspect and modify Figma document state through the plugin bridge. Writes: Modify design nodes; Replace text.
Authentication not yet verified.
Sensitive access: Private Figma design content

The integration can read and alter live Figma documents; use it only in intended files and review generated edits.

Security source · repository notice ↗

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

Popularity

7,047 repository stars · 4.1k package downloads / 30 days

Stars observed Oct 6, 2026. Downloads observed Oct 6, 2026.

All limitations / Review context

Which Figma read and write operations are still exposed through the MCP integration?

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.

The integration can read and alter live Figma documents; use it only in intended files and review generated edits.
Can inspect and modify Figma document state through the plugin bridge.
Figma document content is passed through the local bridge.
Reviewed write actions: Modify design nodes; Replace text
Sensitive access: Private Figma design content
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
This is not an official Figma integration.
The bridge can modify live design documents.

Original activity observations

2026-07-26T07:14:26Z: feat: add set image fill, rename node, create section and set parent …

Technical identity

github.com/grab/cursor-talk-to-figma-mcp

Exact implementation source: https://github.com/grab/cursor-talk-to-figma-mcp ↗
Reviewed resource type: MCP Server
Repository identity: grab/cursor-talk-to-figma-mcp
Package identity: npm:cursor-talk-to-figma-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 ↗
grab/cursor-talk-to-figma-mcp
Recorded repository material and project history.
Package registry ↗
cursor-talk-to-figma-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 13, 2026.

Additional setup details required — see the specific gaps below.

Warning

MCP tools may edit Figma; do not use live design as smoke.
Exact vendor-specific credential revoke procedure not established from checked official Setup documentation; may be external or not applicable. Do not invent.
Requires review of install side effects, credentials, remote scripts, or privileged application/database access before execution. Multiple publisher-documented README steps combined as an ordered excerpt; not a verbatim single publisher code block.
Renderer target is the known JSON syntax path; do not label as the primary CLI host.
Keep Figma documents and the original design files.
MCP100 client-scope note: this Claude Code CLI example applies only to that client and the exact registered name in the command. Desktop, Cursor and other clients use their own configuration; do not run it for a differently named entry.

Install / connect
Publisher instructions
Publisher-specific setup path. Follow prerequisites, then register or connect to your MCP host.
publisher documented install or connect · Publisher instructions · Review before use
```
bun setup
bun socket
```
Configure / authenticate
Publisher instructions
From cloned grab/cursor-talk-to-figma-mcp repository; bun setup configures MCP, then install/link Figma plugin and start websocket.
Advanced configuration · Cursor · Publisher instructions
Cursor · Publisher instructions
{ "mcpServers": { "TalkToFigma": { "args": [ "cursor-talk-to-figma-mcp@latest" ], "command": "bunx" } } }
Check connection
Suggested check
Connect Figma plugin to websocket and verify read-only design inspection from the client.
Remove / uninstall / revoke
MCP100 setup guide
Remove `TalkToFigma` MCP config and unlink/disable the Figma plugin; terminate websocket server.
MCP100 client-scope guidance: each CLI removal example targets only its named client and exact registered entry. Package names, Desktop/Cursor configuration keys and Codex/Claude registration names may differ; use the entry you actually registered. Client removal does not revoke provider credentials.
claude mcp remove TalkToFigma

Official Documentation & Sources

What it does

Talk to Figma MCP connects AI clients to Figma through an MCP server, a Figma plugin and a WebSocket bridge.

Capability: Design & Creative
Resource type: MCP Server
Best fit: Reading and programmatically modifying Figma documents through an AI client.

Representative uses

Read Figma document and selection state
Inspect specific nodes
Programmatically modify designs
Perform bulk text replacements

Limitations

This is not an official Figma integration.
The bridge can modify live design documents.

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: Can inspect and modify Figma document state through the plugin bridge.
Data handling: Figma document content is passed through the local bridge.
Cost: free
Risk and cautions: The integration can read and alter live Figma documents; use it only in intended files and review generated edits.

Access scope and cautions

Write actions: Modify design nodes Replace text
Sensitive access: Private Figma design content
Risk level: high

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: Read Figma document and selection state; Inspect specific nodes; Programmatically modify designs; Perform bulk text replacements.

What setup information is documented?

Recorded installation/entrypoint step: bun setup. Recorded transport: websocket. Prerequisites: Bun; Figma plugin access. These are the documented setup details, not a claim that installation or client compatibility was independently tested.

Can it modify data or perform write operations?

Documented write actions include: Modify design nodes; Replace text. Recorded permission boundary: Can inspect and modify Figma document state through the plugin bridge.

What data-handling boundary should I consider?

Figma document content is passed through the local bridge. Recorded sensitive-access context: Private Figma design content.

What limitations and risks should I check before use?

The integration can read and alter live Figma documents; use it only in intended files and review generated edits. This is not an official Figma integration. The bridge can modify live design documents. A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.

Is this an official MCP?

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