Skip to main content
Book a demo

Connect Figma to Goose

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

Book a demo Goose setup guide

Set up

Add Figma to Goose in four steps

Admins approve the server once. Everyone in Goose 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 Goose to Runlayer

    Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Figma’s 47 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Goose 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 Goose

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

Tools

47 Figma tools in Goose

Runlayer policy decides which of these Goose 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 Goose

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Goose runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Goose’s model sees it.

  • Redact output in place (not available)

    Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination