# How to integrate Figma MCP with OpenCode

```json
{
  "title": "How to integrate Figma MCP with OpenCode",
  "toolkit": "Figma",
  "toolkit_slug": "figma",
  "framework": "OpenCode",
  "framework_slug": "opencode",
  "url": "https://composio.dev/toolkits/figma/framework/opencode",
  "markdown_url": "https://composio.dev/toolkits/figma/framework/opencode.md",
  "updated_at": "2026-05-06T08:11:28.090Z"
}
```

## Introduction

### How to integrate Figma MCP with OpenCode
This guide explains how to connect Figma MCP to OpenCode using Composio Connect, which simplifies OAuth, API changes, and reliability concerns.
There are two ways to set this up:
- Via [Composio Connect MCP](https://dashboard.composio.dev/)
- Via the [Composio CLI](https://dashboard.composio.dev/)

## Also integrate Figma with

- [ChatGPT](https://composio.dev/toolkits/figma/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/figma/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/figma/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/figma/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/figma/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/figma/framework/codex)
- [Cursor](https://composio.dev/toolkits/figma/framework/cursor)
- [VS Code](https://composio.dev/toolkits/figma/framework/vscode)
- [OpenClaw](https://composio.dev/toolkits/figma/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/figma/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/figma/framework/cli)
- [Google ADK](https://composio.dev/toolkits/figma/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/figma/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/figma/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/figma/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/figma/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/figma/framework/crew-ai)

## TL;DR

### Why use Composio?
Composio provides a single MCP server or CLI tool that exposes a set of meta-tools, allowing you to:
- Connect to 1,000+ apps with on-demand tool loading, so you do not fill your LLM context window with unnecessary tool definitions.
- Use programmatic tool calling through a remote Bash tool, letting LLMs write their own code to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
- Handle large tool responses outside the LLM context to keep conversations lean.

## Connect Figma to OpenCode

### Connect Figma with OpenCode
### Option 1: Using Composio CLI
### 1. Install Composio CLI
Install the Composio CLI, authenticate, and initialize your project:

```bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Authenticate with Composio
composio login
```

## What is the Figma MCP server, and what's possible with it?

The Figma MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Figma account. It provides structured and secure access to your Figma workspace, so your agent can perform actions like commenting on designs, managing design tokens, linking developer resources, and automating collaboration workflows on your behalf.
- Automated commenting and feedback loops: Have your agent add, reply to, or delete comments on Figma files and branches to streamline design reviews and team discussions.
- Design token management and conversion: Let the agent extract, update, or convert design tokens in your files, including generating Tailwind CSS configurations for seamless dev handoff.
- Developer resource integration: Automatically attach, update, or remove dev resources linked to Figma nodes, bridging the gap between design and development with contextual documentation or code references.
- Webhook setup and automation: Enable your agent to create or delete webhooks for team events, making it easy to trigger notifications or workflows based on design activity.
- Collaborative variable management: Empower the agent to batch-create, modify, or delete variables, collections, and modes across your design system, keeping everything consistent and up to date.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `FIGMA_ADD_A_COMMENT_TO_A_FILE` | Add a comment to a file | Posts a new comment to a figma file or branch, optionally replying to an existing root comment (replies cannot be nested); `region height` and `region width` in `client meta` must be positive if defining a comment region. |
| `FIGMA_ADD_A_REACTION_TO_A_COMMENT` | Add a reaction to a comment | Posts a specified emoji reaction to an existing comment in a figma file or branch, requiring valid file key and comment id. |
| `FIGMA_CREATE_A_WEBHOOK` | Create a webhook | Creates a figma webhook for a `team id` to send post notifications for an `event type` to a publicly accessible https `endpoint`; an initial ping is sent unless `status` is `paused`. |
| `FIGMA_CREATE_DEV_RESOURCES` | Create dev resources | Creates and attaches multiple uniquely-urled development resources to specified figma nodes, up to 10 per node. |
| `FIGMA_CREATE_MODIFY_DELETE_VARIABLES` | Create, modify, or delete variables | Manages variables, collections, modes, and their values in a figma file via batch create/update/delete operations; use temporary ids to link new related items in one request and ensure `variablemodevalues` match the target variable's `resolvedtype`. |
| `FIGMA_DELETE_A_COMMENT` | Delete a comment | Deletes a specific comment from a figma file or branch, provided the authenticated user is the original author of the comment. |
| `FIGMA_DELETE_A_REACTION` | Delete a reaction | Deletes a specific emoji reaction from a comment in a figma file; the user must have originally created the reaction. |
| `FIGMA_DELETE_A_WEBHOOK` | Delete a webhook | Permanently deletes an existing webhook, identified by its unique `webhook id`; this operation is irreversible. |
| `FIGMA_DELETE_DEV_RESOURCE` | Delete dev resource | Deletes a development resource (used to link figma design elements to external developer information like code or tasks) from a specified figma file. |
| `FIGMA_DESIGN_TOKENS_TO_TAILWIND` | Design tokens to tailwind | Convert design tokens to tailwind css configuration. takes the output from extractdesigntokens and generates: - tailwind.config.ts/js with theme extensions - optional globals.css with font imports note: shadow colors can be provided in either string format (e.g., "rgba(15, 110, 110, 0.32)") or dictionary format (e.g., {"r": 0.059, "g": 0.431, "b": 0.431, "a": 0.32}). |
| `FIGMA_DETECT_BACKGROUND` | Detect background | Detect background layers for selected nodes. uses geometric analysis, z-index ordering, and visual properties to identify potential background layers. |
| `FIGMA_DISCOVER_FIGMA_RESOURCES` | Discover Figma Resources | 🔍 smart figma resource discovery - never guess ids again! 🎯 easiest method: just paste any figma url to get all ids: • file urls: https://www.figma.com/file/abc123/design → get file key • design urls: https://www.figma.com/design/abc123/design → get file key • node urls: ...?node-id=123:456 → get file key + node id • team urls: .../team/123456/... → get team id 🔄 step-by-step discovery: 1. team id → projects list (with project ids) 2. project id → files list (with file keys + thumbnails) 3. file key → nodes list (with node ids + hierarchy) 💡 common workflows: • extract from url: discoverfigmaresources(figma url="...") • browse team: discoverfigmaresources(team id="123") • list files: discoverfigmaresources(project id="proj 456") • find nodes: discoverfigmaresources(file key="abc123") ✨ get file key for getfilejson, node ids for detectbackground, etc. |
| `FIGMA_DOWNLOAD_FIGMA_IMAGES` | Download Figma Images | Download images from figma file nodes. renders specified nodes as images and downloads them using mercury's filedownloadable infrastructure. supports png, svg, jpg, and pdf formats. |
| `FIGMA_EXTRACT_DESIGN_TOKENS` | Extract design tokens | Extract design tokens from figma files. combines styles, variables, and extracted values to create a comprehensive design token system. |
| `FIGMA_EXTRACT_PROTOTYPE_INTERACTIONS` | Extract Prototype Interactions | Extract prototype interactions and animations from figma files. analyzes the prototype data to extract: - user interactions (clicks, hovers, etc.) - transition animations - component variant states - user flows and navigation |
| `FIGMA_GET_ACTIVITY_LOGS` | Get activity logs | Retrieves activity log events from figma, allowing filtering by event types, time range, and pagination. |
| `FIGMA_GET_A_WEBHOOK` | Get a webhook | Retrieves detailed information about a specific webhook by its id, provided the webhook exists and is accessible to the user. |
| `FIGMA_GET_COMMENTS_IN_A_FILE` | Get comments in a file | Retrieves all comments from an existing figma file, identified by a valid `file key`, returning details like content, author, position, and reactions, with an option for markdown formatted content. |
| `FIGMA_GET_COMPONENT` | Get component | Get component data with automatic simplification. returns clean, ai-friendly component structure. |
| `FIGMA_GET_COMPONENT_SET` | Get component set | Retrieves detailed metadata for a specific published figma component set using its unique `key`. |
| `FIGMA_GET_CURRENT_USER` | Get current user | Retrieves detailed information for the currently authenticated figma user. |
| `FIGMA_GET_DEV_RESOURCES` | Get dev resources | Retrieves development resources (e.g., jira/github links) for a figma main file, optionally filtering by specific node ids. |
| `FIGMA_GET_FILE_COMPONENTS` | Get file components | Retrieves published components from a figma file, which must be a main file (not a branch) acting as a library. |
| `FIGMA_GET_FILE_COMPONENT_SETS` | Get file component sets | Retrieves all published component sets from the specified figma main file (file key must not be for a branch). |
| `FIGMA_GET_FILE_JSON` | Get file json | Get figma file data with automatic simplification. this enhanced version automatically transforms verbose figma json into clean, ai-friendly format with: - css-like property names - deduplicated variables - removed empty values - 70%+ size reduction use simplify=false to get raw api response. |
| `FIGMA_GET_FILES_IN_A_PROJECT` | Get files in a project | Fetches a list of files in a figma project, optionally including branch metadata. |
| `FIGMA_GET_FILE_STYLES` | Get file styles | Retrieves a list of published styles (like colors, text attributes, effects, and layout grids) from a specified main figma file (not a branch). |
| `FIGMA_GET_IMAGE_FILLS` | Get image fills | Retrieves temporary (14-day expiry) download urls for all image fills in a figma file; requires `imageref` from `paint` objects to map urls. |
| `FIGMA_GET_LIBRARY_ANALYTICS_COMPONENT_ACTION_DATA` | Get library analytics component action data | Retrieves component insertion and detachment analytics for a specified figma library, groupable by 'component' or 'team' and filterable by a date range (yyyy-mm-dd). |
| `FIGMA_GET_LIBRARY_ANALYTICS_COMPONENT_USAGE_DATA` | Get library analytics component usage data | Retrieves component usage analytics for a specified figma library file (identified by `file key`), with data groupable by 'component' or 'file'. |
| `FIGMA_GET_LIBRARY_ANALYTICS_STYLE_ACTION_DATA` | Get library analytics style action data | Retrieves style usage analytics (insertions, detachments) for a figma library, grouped by 'style' or 'team'; if providing a date range, ensure end date is not before start date. |
| `FIGMA_GET_LIBRARY_ANALYTICS_STYLE_USAGE_DATA` | Get library analytics style usage data | Retrieves style usage analytics for a figma library (specified by a valid `file key`), allowing data to be grouped by 'file' or 'style'. |
| `FIGMA_GET_LIBRARY_ANALYTICS_VARIABLE_ACTION_DATA` | Get library analytics variable action data | Retrieves weekly, paginated analytics data on variable insertions and detachments for a specified figma library (identified by `file key`), groupable by 'variable' or 'team', and filterable by an optional date range. |
| `FIGMA_GET_LIBRARY_ANALYTICS_VARIABLE_USAGE_DATA` | Get library analytics variable usage data | Retrieves paginated analytics data on variable usage from a specified figma library, grouped by 'file' or 'variable', for libraries with enabled analytics. |
| `FIGMA_GET_LOCAL_VARIABLES` | Get local variables | Retrieves all local/remote variables for a figma file/branch; crucial for obtaining mode-specific values which `/v1/files/{file key}/variables/published` omits. |
| `FIGMA_GET_PAYMENTS` | Get payments | Retrieves a user's payment information for a figma plugin, widget, or community file; the authenticated identity must own the resource. |
| `FIGMA_GET_PROJECTS_IN_A_TEAM` | Get projects in a team | Retrieves projects within a specified figma team that are visible to the authenticated user. |
| `FIGMA_GET_PUBLISHED_VARIABLES` | Get published variables | Retrieves variables published from a specified figma file; this api is available only to full members of enterprise organizations. |
| `FIGMA_GET_REACTIONS_FOR_A_COMMENT` | Get reactions for a comment | Retrieves reactions for a specific comment in a figma file. |
| `FIGMA_GET_STYLE` | Get style | Retrieves detailed metadata for a specific style in figma using its unique style key. |
| `FIGMA_GET_TEAM_COMPONENTS` | Get team components | Retrieves components published in a specific figma team's library; the team must have published components, otherwise an empty list is returned. |
| `FIGMA_GET_TEAM_COMPONENT_SETS` | Get team component sets | Retrieves a paginated list of published component sets (collections of reusable ui elements) from a specified figma team's library. |
| `FIGMA_GET_TEAM_STYLES` | Get team styles | Retrieves a paginated list of published styles, such as colors or text attributes, from a specified figma team's library. |
| `FIGMA_GET_TEAM_WEBHOOKS` | Get team webhooks | Retrieves all webhooks registered for a specified figma team. |
| `FIGMA_GET_VERSIONS_OF_A_FILE` | Get versions of a file | Retrieves the version history for a figma file or branch, as specified by its `file key`. |
| `FIGMA_GET_WEBHOOK_REQUESTS` | Get webhook requests | Retrieves a history of webhook requests for a specific figma webhook subscription; data is available for requests sent within the last seven days. |
| `FIGMA_RENDER_IMAGES_OF_FILE_NODES` | Render images of file nodes | Renders specified nodes from a figma file as images (jpg, pdf, png, svg), returning a map of node ids to image urls (or `null` for failed nodes); images expire after 30 days and are capped at 32 megapixels (larger requests are scaled down). |
| `FIGMA_UPDATE_A_WEBHOOK` | Update a webhook | Updates an existing figma webhook, identified by `webhook id`, allowing modification of its event type, endpoint, passcode, status, or description. |
| `FIGMA_UPDATE_DEV_RESOURCES` | Update dev resources | Updates the name and/or url of one or more existing figma dev resources, each identified by its unique `id`. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

Once connected, OpenCode can access the Figma MCP server via Composio to run the app actions you authorize, directly from your coding workflow.

## Complete Code

None listed.

## Conclusion

### Way Forward
Now that Figma is connected, extend your setup by connecting the other apps you already use every day, so your agent can run true cross-app workflows end to end.
- Connect Calendar to turn threads into scheduled meetings automatically.
- Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
- Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
- Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.
Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single MCP endpoint, your agent can coordinate multiple tools safely and reliably in one conversation.

## How to build Figma MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/figma/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/figma/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/figma/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/figma/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/figma/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/figma/framework/codex)
- [Cursor](https://composio.dev/toolkits/figma/framework/cursor)
- [VS Code](https://composio.dev/toolkits/figma/framework/vscode)
- [OpenClaw](https://composio.dev/toolkits/figma/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/figma/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/figma/framework/cli)
- [Google ADK](https://composio.dev/toolkits/figma/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/figma/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/figma/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/figma/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/figma/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/figma/framework/crew-ai)

## Related Toolkits

- [Abyssale](https://composio.dev/toolkits/abyssale) - Abyssale is a creative automation platform for generating images, videos, GIFs, PDFs, and HTML5 content programmatically. It streamlines and scales visual content production for marketing, design, and operations teams.
- [Alttext ai](https://composio.dev/toolkits/alttext_ai) - AltText.ai is a service that generates alt text for images automatically. It helps boost accessibility and SEO for your visual content.
- [Bannerbear](https://composio.dev/toolkits/bannerbear) - Bannerbear is an API-driven platform for generating images and videos automatically at scale. It helps businesses create custom graphics, social visuals, and marketing assets using powerful templates.
- [Canva](https://composio.dev/toolkits/canva) - Canva is a drag-and-drop design suite for creating professional graphics, presentations, and marketing materials. It makes it easy for anyone to design with beautiful templates and a vast library of elements.
- [Claid ai](https://composio.dev/toolkits/claid_ai) - Claid.ai delivers AI-driven image editing APIs for tasks like background removal, upscaling, and color correction. It helps automate and enhance image workflows with powerful, developer-friendly tools.
- [Cloudinary](https://composio.dev/toolkits/cloudinary) - Cloudinary is a cloud-based platform for managing, uploading, and transforming images and videos. It streamlines media workflows and delivers optimized assets globally.
- [Cults](https://composio.dev/toolkits/cults) - Cults is a digital marketplace for 3D printing models, connecting designers and makers. It lets creators share, sell, and discover a huge variety of printable designs easily.
- [DeepImage](https://composio.dev/toolkits/deepimage) - DeepImage is an AI-powered image enhancer and upscaler. Get higher-quality images with just a few clicks.
- [Dreamstudio](https://composio.dev/toolkits/dreamstudio) - DreamStudio is Stability AI’s platform for generating and editing images with AI. It lets you easily turn ideas into stunning visuals, fast.
- [Fal.ai](https://composio.dev/toolkits/fal_ai) - Fal.ai is a generative media platform offering 600+ AI models for images, video, voice, and audio. Developers use Fal.ai for fast, scalable access to cutting-edge generative AI tools.
- [Html to image](https://composio.dev/toolkits/html_to_image) - Html to image converts HTML and CSS into images or captures web page screenshots. Instantly generate visuals from code or web content—no manual screenshots needed.
- [Imagior](https://composio.dev/toolkits/imagior) - Imagior is an AI-powered image generation platform that lets you create and customize images using dynamic templates and APIs. Perfect for businesses and creators needing fast, scalable visuals without design hassle.
- [Imejis io](https://composio.dev/toolkits/imejis_io) - Imejis io is an API-based image generation platform with powerful customization and template support. It lets you create and modify images in seconds, no manual design work required.
- [Imgix](https://composio.dev/toolkits/imgix) - Imgix is a real-time image processing and delivery service for developers. It helps you optimize, transform, and deliver images efficiently at any scale.
- [Kraken io](https://composio.dev/toolkits/kraken_io) - Kraken.io is an image optimization and compression platform. It helps you shrink image file sizes while keeping visual quality intact.
- [Logo dev](https://composio.dev/toolkits/logo_dev) - Logo.dev is an API and database for high-resolution company logos and brand metadata. Instantly fetch official logos from any domain without scraping or manual searching.
- [Miro](https://composio.dev/toolkits/miro) - Miro is a collaborative online whiteboard platform for teams to brainstorm, design, and manage projects visually. It streamlines teamwork by enabling real-time idea sharing, diagramming, and workflow planning in a single space.
- [Mural](https://composio.dev/toolkits/mural) - Mural is a digital whiteboard platform for distributed visual collaboration. It helps teams brainstorm, map ideas, and diagram together in real time.
- [Pexels](https://composio.dev/toolkits/pexels) - Pexels is a free stock library offering high-quality photos and videos via API. Instantly boost your app or website with stunning visuals for any use case.
- [Placid](https://composio.dev/toolkits/placid) - Placid is a creative automation toolkit that generates images, PDFs, and videos from custom templates via API. Effortlessly automate creative workflows and dynamic content creation at scale.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Figma MCP?

With a standalone Figma MCP server, the agents and LLMs can only access a fixed set of Figma tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Figma and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with OpenCode?

Yes, you can. OpenCode fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Figma tools.

### Can I manage the permissions and scopes for Figma while using Tool Router?

Yes, absolutely. You can configure which Figma scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Figma data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)