01 · Records and state owned
Figma Design frames, components, variables, auto layout, design context, code context, Code Connect mappings, FigJam objects, Make resources, and captured live interfaces.
Figma
Figma
Figma belongs in Atlas because its MCP exposes design-system context and beta native canvas writes, connecting implementation agents with editable Design and FigJam artifacts.
Content, CMS, creative & DAMSystem of productionBYO-UI-ready platform
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Retrieve design context, component and variable metadata, layout information, FigJam or Make resources, and Code Connect mappings for code generation and implementation handoff.
03 · Actions and write paths
Create or modify native Design frames, components, variables, and auto layout; add FigJam stickies, sections, connectors, and shapes; capture live UI into editable layers.
04 · Authentication and permissions
Remote connections use OAuth and inherit each user's file permissions, plan, and seat. Only clients in Figma's MCP catalog can connect to the hosted server.
05 · Monitoring, approval, and recovery
Figma checks existing file access for each user; Enterprise managed authorization currently supports Claude through Okta, while other hosted clients rely on per-user OAuth for approved users.
06 · Limits and caveats
Read-tool quotas vary by plan and seat; View and Collab seats receive six calls monthly. Write tools are beta, and selected write operations are rate-limit exempt.
First-party MCP tool catalog
23 named MCP tools · Figma MCP tools
The named tools on Figma's first-party MCP tools-and-prompts page. The list spans the hosted remote server and the more limited desktop server; per-item availability labels identify remote-only and client-limited tools. Reviewed Jul 10, 2026. The remote server exposes the broadest feature set. Write-to-canvas operations can create or modify native Figma content, while access remains limited by the authenticated user's file permissions, seat, plan, and supported MCP client.
First-party exact listComplete list on cited pageFigma remote and desktop MCP servers
23 shown
Code Connect5
add_code_connect_mapwriteget_code_connect_mapreadget_code_connect_suggestionsreadget_context_for_code_connectreadsend_code_connect_mappingswriteFiles, diagrams, and assets5
create_new_filewritedownload_assetsreadupload_assetswritegenerate_diagramwritegenerate_figma_designwriteDesign context, libraries, and identity8
get_design_contextreadget_figjamreadget_librariesreadget_metadatareadget_screenshotreadget_variable_defsreadsearch_design_systemreadwhoamireadShader resources4
get_shader_effectreadget_shader_fillreadlist_shader_effectsreadlist_shader_fillsreadGeneral-purpose canvas access1
use_figmaread/writeNo matching catalog items
Try a broader name, group, action, or availability term.
Catalog evidence: Figma MCP server: Tools and prompts · Figma MCP server introduction
Agent access
MCP support
Official MCP serverFigma-hosted remote MCP plus desktop/local serverCurrent service; write-to-canvas capabilities in beta
Support: Official MCP server
Read scope: Read structured Design, FigJam, Make, component, variable, layout, and Code Connect context to support code generation, inspection, and handoff workflows.
Write scope: 7 of 23 reviewed named tools have a write, draft, or mixed action label, including add_code_connect_map, send_code_connect_mappings, create_new_file, upload_assets, generate_diagram, and others. Read each catalog boundary before enabling them.
Authentication: The hosted server uses per-user OAuth through an approved catalog client. The desktop server is locally enabled by users through preferences in the Figma desktop application.
Approval boundary: Require review before canvas writes become shared design-system assets; beta tools change native files, while generated code remains an implementation artifact outside Figma's approval model.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access3
UI extensibility4
Portability4
Observability3
Documentation5
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Figma ships them.
Single-platform patterns
- Design-system, creative, and handoff cockpit
- Campaign asset assembly room
- Brief-to-experience studio
- Content approval queue
Multi-platform compositions
- Figma + CRM or campaign platform: campaign asset assembly room
- Figma + work-management system + analytics or distribution platform: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
7 recorded sources
MCPRepresentative source
https://developers.figma.com/docs/figma-mcp-server/ ↗Remote and desktop deployment, design context, native canvas writes, live UI capture, and beta maturity
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 22, 2026
Figma MCP deployment and tool roles reviewed 2026-07-22
APISource inventory
https://developers.figma.com/docs/rest-api/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Developer docsSource inventory
https://developers.figma.com/ ↗First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://www.figma.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Webhooks / extensionsSource inventory
https://developers.figma.com/docs/plugins/ ↗First-party webhook, event, SDK, embedded-app, or extension documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
MCP access and limitsSource inventory
https://developers.figma.com/docs/figma-mcp-server/rate-limits-access/ ↗OAuth, catalog clients, file permissions, plan-and-seat quotas, managed authorization, and write-tool rate treatment
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 22, 2026
Figma MCP authentication, catalog eligibility, permissions, and quotas reviewed 2026-07-22
MCP tool catalogTargeted review
Figma MCP server: Tools and prompts ↗Named catalog evidence used on this profile.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party catalog review
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.