Skip to main content
Book a demo

Connect Figma to Claude Cowork

Give Claude Cowork governed access to Figma’s 47 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude Cowork setup guide

Set up

Add Figma to Claude Cowork in four steps

Admins approve the server once. Everyone in Claude Cowork then gets it through the same governed connection.

  1. 1

    Approve Figma in Runlayer

    Add Figma from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Claude Cowork to Runlayer

    Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, Figma’s 47 tools show up in Claude Cowork’s own tool list.

    Claude Cowork setup guide
  3. 3

    Sign in to Figma

    Each user signs in to Figma with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Figma from Claude Cowork

    Figma’s approved tools appear in Claude Cowork. Every call is checked against policy and recorded.

Tools

47 Figma tools in Claude Cowork

Runlayer policy decides which of these Claude Cowork users can call. 23 read data only and 5 can change or delete data.

  • Add code connect mapping

    Map a Figma node to a code component in your codebase using Code Connect.

  • Create generative plugin

    Creates a new generative plugin in the authenticated user's account library and returns its id.

  • Create new file

    Create a new blank Figma file.

  • Create shader

    Set kind to effect for a shader that transforms the layer beneath it, or fill for a shader that generates its own pixels.

  • Download assets

    Download assets from a Figma file for a single node: an exported render, the original source images, and SVGs of the vector layers.

  • Export video

    Export a Figma timeline node as an MP4 video.

  • Generate diagram

    Create a flowchart, decision tree, gantt chart, sequence diagram, state diagram, or entity relationship diagram in FigJam, using Mermaid.js.

  • Generate Figma design

    Capture a live web page by URL into an existing Figma design file.

See all 47 Figma tools

Control

What Runlayer can see and stop in Claude Cowork

Some controls apply to every client at the gateway. Others depend on what Claude Cowork exposes to Runlayer.

  • Gateway policy (available)

    Every Figma call from Claude Cowork passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude Cowork as the client, the tool, and the policy and scanner decisions.

  • Anthropic inference hooks (available)

    Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.

  • OTLP telemetry (available)

    Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude Cowork prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.

In Claude Cowork

  • Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.

Frequently asked questions

Connect more

Find another combination