Figma connectorMCP-first

A public Figma connector with a real plugin runtime

Scout's Figma connector pairs with a plugin-backed runtime so agents can inspect and mutate live files, components, variables, and exports through MCP.

pairselectcomposeexport

See connector reference Browse connectors

The live design bridge

Multiplayer design energy: colored handles, component nodes, variable rails, and a plugin handoff that feels native to Figma's culture of live collaboration.

A plugin-backed bridge between design intent and agent action: live selection, pages, variables, components, and export surfaces held in one collaborative runtime.

Identity

Figma is not a file importer. It is a live creative runtime paired through a plugin.

The Figma connector deserves its own page because the integration is a living partnership between Scout and the Figma canvas. A plugin sits inside the design tool and keeps the agent connected to the active document.

That means the agent can reason about pages, selection, components, variables, and exports while the designer's actual workspace remains the source of truth.

State

live document

Signal

selection and variables

Loop

pair, inspect, mutate

Plugin-backed runtime

Paired with a live Figma plugin

Figma is not a small side integration. The public connector pairs with a Scout Figma plugin so MCP calls can operate on the live document, active page, selection, variables, and export surfaces inside Figma itself.

Open the Scout Figma plugin in the file you want to expose.

After pairing, your MCP client can call the hosted Figma connector against that live plugin-backed runtime.

Best for

Working against a live Figma file instead of static exports or screenshots.

Reading and mutating nodes, components, variables, tokens, and page structure in place.

Design-system cleanup, asset export, and plugin-runtime workflows controlled through MCP.

Runtime model

Operates through a paired plugin runtime inside Figma rather than through an offline export pipeline.

Keeps page, selection, viewport, and document context live while MCP calls run.

Makes Figma a first-class design connector with its own execution surface, not just a browser page to scrape.

Auth model

Pairing starts inside the plugin and finishes through Scout's browser handoff at /figma/connect.

MCP clients use the hosted Figma endpoint after that paired runtime is available, instead of copying browser-style connector configs into the plugin itself.

Capability atlas

A compact map of what this connector can do.

Figma exposes 71 commands across 6 capability groups. The full reference stays close, while this page keeps the connector's runtime shape easy to understand.

Content

Inspect and mutate nodes, components, layout, typography, fills, effects, geometry, and document structure.

figma-ancestorsfigma-auto_layoutfigma-blendfigma-boolean_opfigma-boundsfigma-childrenfigma-clonefigma-code_block+42 more

Navigation

Move between pages, focus the viewport, and manage the active selection in a live document.

figma-create_pagefigma-delete_pagefigma-focusfigma-pagefigma-pagesfigma-selectfigma-selectionfigma-switch_page+1 more

Management

Manage variable collections, variables, tokens, and dev-status metadata.

figma-create_variablefigma-create_variable_collectionfigma-dev_statusfigma-list_variable_collectionsfigma-list_variablesfigma-tokenfigma-variable

Interaction

Use the plugin runtime for toasts and history control.

figma-notifyfigma-undo

Storage

Read and write plugin-scoped storage surfaces.

figma-plugin_datafigma-shared_plugin_data

Media

Export nodes and assets from the current Figma document.

figma-export

Connection

Add the connector deliberately.

Add the hosted connector endpoint your MCP client needs. Each public connector stays separate so agent permissions and runtime boundaries remain explicit.

SnippetJSON

{
  "mcpServers": {
    "scout-figma": {
      "type": "http",
      "url": "https://mcp.scout.i.ng/figma"
    }
  }
}

Keep connector boundaries intentional

Dedicated connector pages should make capability boundaries memorable before the agent ever receives tools.

Browse all connectors Back to docs reference