Connect the Figma API

• ✓ Files, projects & metadata
• ✓ Version history
• ✓ Components & styles
• ✓ Image export
• — Write operations (Figma REST has no write path for design content)
• ✓ Token refresh
• — Webhooks (Poll via the file tools)

accounts_

get · identity

projects_

list · project files

files_

get · nodes · meta · versions · image export · fills

components_

list · styles

OAuth scopes requested

• Read your Figma user identity
• Read files, projects, components and styles
• Read file metadata and version history
• Export node images and read image fills

# Add Modiva's MCP server to your agent
{
  "mcpServers": {
    "modiva": {
      "url": "https://mcp.modiva.ai",
      "headers": { "Authorization": "Bearer $MODIVA_MCP_KEY" }
    }
  }
}

# Then connect Figma and call its tools, e.g.
accounts_list(provider="figma")

How do I connect the Figma API with Modiva?

Create a Modiva account, generate an MCP key, and connect Figma from your dashboard. Modiva runs the full OAuth flow and stores the encrypted token for you — no client secrets in your code.

What can I do with the Figma API through Modiva?

Read files, projects, components, styles, metadata and version history, and export node images across your Figma files through one unified API and MCP server. You get 11 typed tools grouped by resource (accounts_, projects_, files_, components_), callable over REST or the MCP server.

Do I need to handle OAuth or token refresh myself?

No. Modiva handles the Figma OAuth handshake, token storage (envelope-encrypted) and automatic refresh. You call a single unified endpoint.

Can an AI agent use the Figma API?

Yes — that is the point. Modiva exposes Figma as Model Context Protocol (MCP) tools, so agents like Claude, Cursor or your own app can read and act on Figma through one endpoint.