Figma

Live

OAUTH 2.0

DESIGN

Design

Every design file, component, and prototype your team builds lives in Figma. Figma MCP gives your agent authenticated access to design assets scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the Figma account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
Figma
agent · Acme Q3
Run
List all components in our design system library and flag any without descriptions.
S
figma_components_list
88ms
Design agent
42 components in design system. 8 missing descriptions: Button/Primary, Modal/Alert, Input/Error, Badge/Status, Icon/Arrow, Card/Feature, Tag/Category, Divider/Section.
Sources: 42 components, design system library
figmamcp
42 components
18:29
Message Claude...

Tools your design agent reaches for on Figma, scoped per user.

CALL ANY TOOL
Retrieve files and nodes, list components, manage comments, and export design assets.
figma_me_get
Me get
Returns the authenticated user's information including name, email, and profile image URL.
Parameters
Name
Type
Required
Description
No parameters required
figma_webhooks_list
Webhooks list
figma_file_get
File get
figma_webhook_create
Webhook create
figma_team_get
Team get
figma_webhook_delete
Webhook delete
figma_style_get
Style get
figma_webhook_update
Webhook update
figma_oembed_get
Oembed get
figma_file_styles_list
File styles list
figma_webhook_get
Webhook get
figma_team_styles_list
Team styles list
figma_payments_get
Payments get
figma_folder_files_list
Folder files list
figma_component_get
Component get
figma_team_folders_list
Team folders list
figma_file_meta_get
File meta get
figma_activity_logs_list
Activity logs list
figma_file_nodes_get
File nodes get
figma_dev_resources_list
Dev resources list
figma_folder_meta_get
Folder meta get
figma_file_comments_list
File comments list
figma_project_meta_get
Project meta get
figma_file_images_render
File images render
figma_component_set_get
Component set get
figma_file_versions_list
File versions list
figma_dev_resource_create
Dev resource create
figma_project_files_list
Project files list
figma_dev_resource_delete
Dev resource delete
figma_team_projects_list
Team projects list
Build your Agent
Drop the toolkit in, point it at the user, and your design agent can use Figma from the first run.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["figma"], toolNames: ["figma_file_get", "figma_files_list", "figma_components_list"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["figma"], toolNames: ["figma_file_get", "figma_files_list", "figma_components_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["figma"], toolNames: ["figma_file_get", "figma_files_list", "figma_components_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/figma",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start using Figma.
Search & recall
Copy the prompt
Copied
List all files in [project name].
Copy the prompt
Copied
Get the components in [file name].
Copy the prompt
Copied
Find all comments on [file name].
Copy the prompt
Copied
List all frames in [page name] of [file].
Action & collaboration
Copy the prompt
Copied
Post a comment on [file]: [text].
Copy the prompt
Copied
Export [node name] as PNG.
Copy the prompt
Copied
List all published components in [team name].
Copy the prompt
Copied
Get the node structure of [frame name].
Audits & reporting
Copy the prompt
Copied
Which components are missing descriptions?
Copy the prompt
Copied
List all files updated this week.
Copy the prompt
Copied
Find duplicate component names in [library].
Copy the prompt
Copied
Export all icons from [file] as SVG.
SEE HOW AUTH WORKS
Users authorize Figma once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Figma
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Figma
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Figma
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Figma
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
Same per-user auth pattern across other design agents and MCP connectors. Working code, live demos, fork what fits.
Engineering Teams
DevOps assistant agent
Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.
Engineering Teams
Engineering standup agent
Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.
Engineering Teams
Auto release notes agent
Reads merged GitHub PRs, groups them into structured release notes, publishes the page to Notion, and announces the release in Slack. Every call runs on the engineer's own delegated OAuth.
Engineering Teams
Slack triage
Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.
Test other agents
Same per-user auth pattern across other design agents and MCP connectors. Working code, live demos, fork what fits.
ENGINEERING
Engineering standup agent
Pull commits from GitHub and GitLab, track Jira issue movement, and post a per-engineer standup brief to Slack.
ENGINEERING
DevOps assistant agent
Poll GitHub for failing checks and stale pull requests, open Linear issues for the ones that need work, and digest to Slack.
ENGINEERING
Auto-release notes agent
Group merged GitHub PRs into structured release notes, publish the page to Notion, and announce the release in Slack.
ENGINEERING
Slack triage agent
Classify new Slack messages as bugs or support requests, file the GitHub issue or Zendesk ticket, and reply in the thread.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.
// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Figma today. Others tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Figma as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.
Where is the Figma oauth 2.0 stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.
Can I limit what the agent is allowed to do in Figma?
Yes. Pass a tool name filter to listScopedTools so the design agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Figma.
What happens when a user revokes Figma access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Can the agent read files in projects the user hasn't joined?
No. File access inherits the authorizing user's Figma OAuth scope. Projects and files the user has no access to are not returned. Organization-level permissions carry over at every call.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""figma"": {
""url"": ""https://mcp.scalekit.com/figma"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.figma]
url = ""https://mcp.scalekit.com/figma""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""figma"": {
""url"": ""https://mcp.scalekit.com/figma"",
""type"": ""http""
}
}
}