How to use Figma with Copilot Studio
You want Figma inside Copilot Studio so it can review design feedback and assign follow-up, audit design system usage across projects, prepare a design handoff, and update shared design tokens safely — without you copy-pasting between tabs. Here is the whole setup, once.
Create your Figma gateway
The gateway is the thing Copilot Studio connects to, and it is where you decide which Figma tools an agent may use. You create it once and every client reuses it.
-
Create an Arcade account
Sign up and open the dashboard. The free tier is enough to follow this through.
-
Create an MCP Gateway and select your Figma tools
In the dashboard, create a gateway and pick the Figma tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.
-
Copy your gateway URL
Every client below needs it.
https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>
Connect the gateway to Copilot Studio
Needs a Microsoft 365 subscription with access to Copilot Studio, plus an Arcade API key.
-
Add an MCP tool to your agent
In Copilot Studio, open your agent → Tools → Add a tool → Model Context Protocol → New tool.
-
Point it at your gateway
Give the server a name and description, put your gateway URL in Server URL, set Authentication to OAuth 2.0 and Type to Dynamic discovery.
-
Authorize and try it out
Saving redirects you to Arcade to approve access. Then start a conversation and use your Figma tools — Arcade authorizes each service just in time.
Full Copilot Studio guide in the docs steps verified 2026-08-13
Start with these Figma prompts
Copilot Studio can now act on your Figma account. Click a prompt to copy it.
Control file access and write permissions so an agent can inspect designs without changing variables, deleting comments, or editing linked resources. Pair it with Contextual Access policies to require approval for consequential Figma changes.