The Figma connector.
Files, comments and image renders. Connect once with your own key. Every agent your team runs reads the same 5 tools under one permission model.
How access is governed
5
Read tools
Open by default. They run when called, and every call is logged with the endpoint, tool and capability.
0
Write tools
Figma exposes no write tools. Nothing it does mutates external state.
0
Destructive tools
Figma defines no destructive tools. Nothing here deletes data.
Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.
Every Figma tool
5 tools, named as the agent sees them.
- get_fileread
Get a Figma file's page/frame structure and its text content. `file_key` is the segment after /file/ or /design/ in a Figma URL. Depth defaults to 2 (pages plus their top-level frames) — raise it only when you need to go deeper into one frame, and prefer passing `ids` to scope to a single node.
- get_team_projectsread
List the projects (folders) in a Figma team. Uses the connector's configured team when `team_id` is omitted. Feed a project `id` from here into list_project_files.
- list_project_filesread
List the files inside a Figma project. Takes `project_id` from get_team_projects. The `key` of each file is what get_file, get_file_comments and get_image_renders take.
- get_file_commentsread
Read the comment threads on a Figma file — design feedback, review notes and open questions. Takes a `file_key`. Replies carry `parent_id` pointing at the comment they answer.
- get_image_rendersread
Render specific nodes of a file as images and return their URLs. Takes a `file_key` and the node `ids` you got from get_file. Rendered URLs expire after 30 days, and a null URL means that node could not be rendered.
Use it from any agent
The same Figma tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.
{
"mcpServers": {
"growth": {
"type": "http",
"url": "https://app.notara.ai/mcp/g/acme/growth",
"headers": {
"Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
}
}
}
}The URL and token are placeholders. Real endpoints are issued per group from the dashboard.
Setup
- 01
Create a Figma Personal Access Token in your Figma account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.
- 02
Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.
- 03
The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.
Connect Figma once. Use it everywhere.
Use Notara directly, or bring us the workflow that needs to be redesigned and built.