← ClaudeAtlas

figma-automationlisted

Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas.
aiskillstore/marketplace · ★ 350 · AI & Automation · score 83
Install: claude install-skill aiskillstore/marketplace
# Figma Automation via Rube MCP Automate Figma operations through Composio's Figma toolkit via Rube MCP. ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active Figma connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `figma` - Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas ## Setup **Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. 1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `figma` 3. If connection is not ACTIVE, follow the returned auth link to complete Figma auth 4. Confirm connection status shows ACTIVE before running any workflows ## Core Workflows ### 1. Get File Data and Components **When to use**: User wants to inspect Figma design files or extract component information **Tool sequence**: 1. `FIGMA_DISCOVER_FIGMA_RESOURCES` - Extract IDs from Figma URLs [Prerequisite] 2. `FIGMA_GET_FILE_JSON` - Get file data (simplified by default) [Required] 3. `FIGMA_GET_FILE_NODES` - Get specific node data [Optional] 4. `FIGMA_GET_FILE_COMPONENTS` - List published components [Optional] 5. `FIGMA_GET_FILE_COMPONENT_SETS` - List component sets [Optional] **Key parameters**: - `file_key`: File key from URL (e.g., 'abc123XYZ' from figma.com/design/abc123XYZ/...) - `ids`: Comma-separated node IDs (NOT an array) - `depth`: Tree traversal depth (2 for p