How to integrate Figma MCP with Kimi Code

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Figma logo
Kimi Code logo
divider

How to integrate Figma MCP with Kimi Code

Kimi Code is Moonshot AI's open-source coding agent, powered by Kimi K2.6. It runs in your terminal, reads and edits code, executes shell commands, and plans multi-step tasks, with native MCP support for extending it to outside tools.

In this guide, I will explain the easiest and most secure way to connect your Figma account to Kimi Code via Composio Connect, so it can add a comment to this Figma file, convert design tokens to Tailwind CSS, delete a reaction from a comment, and more without ever putting your account credentials at risk.

Also integrate Figma with

Why use Composio?

Composio provides:

  • Access to 1,000+ managed apps from a single MCP endpoint. This makes it convenient for agents to run cross-app workflows.
  • Managed OAuth. You do not have to worry about authentication and authorization flows for every app.
  • Programmatic tool calling. Allows LLMs to write code in a remote workbench to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Large tool response handling outside the LLM context. This minimizes context bloat from large tool responses.
  • Dynamic just-in-time access to thousands of tools across hundreds of apps. Composio loads the tools your agent needs, so LLMs are not overwhelmed by tools they do not need.

Connect Figma to Kimi Code

Kimi Code is a TypeScript agent distributed through npm. It acts as an MCP client and reads server definitions from an mcp.json file, and it can also add and authenticate servers conversationally through /mcp-config. Composio is a remote HTTP server that authenticates with OAuth, so no API key is stored anywhere.

1. Install Kimi Code

The quickest way is the official install script, which requires no pre-installed Node.js and places the kimi executable on your PATH.

bash
# macOS or Linux
curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash

# Windows PowerShell
irm https://code.kimi.com/kimi-code/install.ps1 | iex

# Confirm the installation
kimi --version

2. Log in

Start Kimi Code in your project directory, then sign in from the interactive UI:

bash
kimi

Run /login and choose Kimi Code OAuth using the device-code flow, or use a Moonshot API key.

3. Add Composio with /mcp-config

In current versions of Kimi Code, MCP servers are managed inside the app, not with a shell subcommand. From the interactive UI, run:

bash
/mcp-config
Kimi Code MCP config flow for adding the Composio MCP server

Tell it the server name and URL in plain language. For example:

Server name is Composio, and here is the server URL: https://connect.composio.dev/mcp

Kimi Code asks whether to add it globally, at ~/.kimi-code/mcp.json, or project-local for the current checkout, then writes the entry for you:

bash
{
  "mcpServers": {
    "Composio": {
      "url": "https://connect.composio.dev/mcp"
    }
  }
}

There is no transport field to set. Kimi Code infers HTTP from the url.

4. Restart the session

The new server is picked up on a fresh session, not the current one. Start a new session:

bash
/new

On the new session, Kimi Code detects that the server needs authorization and prompts you to run:

bash
/mcp-config login Composio

5. Authorize with OAuth

Run the command Kimi suggests:

bash
/mcp-config login composio

Kimi Code opens Composio's authorization page or surfaces a URL. Approve access, then return to the session. You should see confirmation that the Composio MCP server is connected.

Composio authorization page for Kimi Code MCP setup

Check the connection status any time with /mcp. Composio should appear as connected with its tools listed.

Kimi Code showing Composio connected after OAuth authorization

Connect your Figma account

Back in a Kimi Code session, ask the agent to connect to Figma or give it any Figma-related task.

For example, ask it to:

  • "Add a comment to this Figma file"
  • "Convert design tokens to Tailwind CSS"
  • "Delete a reaction from a comment"

It will prompt you to authenticate and authorize access to Figma.

That is it. Composio tools are now available in Kimi Code, and your Figma account is ready to use.

Supported Tools & Triggers

Tools
Add a comment to a filePosts 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.
Add a reaction to a commentPosts a specified emoji reaction to an existing comment in a Figma file or branch, requiring valid file_key and comment_id.
Create a webhookCreates a Figma webhook to receive POST notifications when specific events occur.
Create dev resourcesCreates and attaches multiple uniquely-URLed development resources to specified Figma nodes, up to 10 per node.
Create, modify, or delete variablesManages 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`.
Delete a commentDeletes a specific comment from a Figma file or branch, provided the authenticated user is the original author of the comment.
Delete a reactionDeletes a specific emoji reaction from a comment in a Figma file; the user must have originally created the reaction.
Delete a webhookPermanently deletes an existing webhook, identified by its unique `webhook_id`; this operation is irreversible.
Delete dev resourceDeletes a development resource (used to link Figma design elements to external developer information like code or tasks) from a specified Figma file.
Design tokens to tailwindConvert design tokens to Tailwind CSS configuration.
Detect Background LayersDetect background layers for selected nodes in a Figma file.
Discover Figma ResourcesSmart Figma resource discovery - extract IDs from any Figma URL.
Download Figma ImagesDownload images from Figma file nodes.
Extract design tokensExtract design tokens from Figma files by combining styles, variables, and node-extracted values.
Extract Prototype InteractionsExtract prototype interactions and animations from Figma files.
Get activity logsRetrieves activity log events from Figma, allowing filtering by event types, time range, and pagination.
Get a webhookRetrieves detailed information about a specific webhook by its ID, provided the webhook exists and is accessible to the user.
Get comments in a fileRetrieves 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.
Get componentFetches metadata for a specific component using its unique identifier.
Get component setRetrieves detailed metadata for a specific published Figma component set using its unique `key`.
Get current userRetrieves detailed information for the currently authenticated Figma user.
Get dev resourcesRetrieves development resources (e.
Get file componentsRetrieves published components from a Figma file, which must be a main file (not a branch) acting as a library.
Get file component setsRetrieves all published component sets from the specified Figma main file (file_key must not be for a branch).
Get file jsonGet Figma Design file data with automatic simplification.
Get file metadataGet Figma file metadata including name, creator, last modification details, thumbnail, and access information.
Get file nodesFetch JSON for specific node IDs from a Figma file to avoid full-file payload limits.
Get files in a projectFetches a list of files in a Figma project, optionally including branch metadata.
Get file stylesRetrieves a list of published styles (like colors, text attributes, effects, and layout grids) from a specified main Figma file (not a branch).
Get image fillsRetrieves temporary (14-day expiry) download URLs for all image fills in a Figma file; requires `imageRef` from `Paint` objects to map URLs.
Get library analytics component action dataRetrieves component insertion and detachment analytics for a specified Figma library, groupable by 'component' or 'team' and filterable by a date range (YYYY-MM-DD).
Get library analytics component usage dataRetrieves component usage analytics for a specified Figma library file (identified by `file_key`), with data groupable by 'component' or 'file'.
Get library analytics style action dataRetrieves 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.
Get library analytics style usage dataRetrieves style usage analytics for a published Figma library.
Get library analytics variable action dataRetrieves 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.
Get library analytics variable usage dataRetrieves paginated analytics data on variable usage from a specified Figma library, grouped by 'file' or 'variable', for libraries with enabled analytics.
Get local variablesRetrieves all local/remote variables for a Figma file/branch; crucial for obtaining mode-specific values which `/v1/files/{file_key}/variables/published` omits.
Get paymentsRetrieves a user's payment information for a Figma plugin, widget, or Community file; the authenticated identity must own the resource.
Get projects in a teamRetrieves projects within a specified Figma team that are visible to the authenticated user.
Get published variablesRetrieves variables published from a specified Figma file; this API is available only to full members of Enterprise organizations.
Get reactions for a commentRetrieves reactions for a specific comment in a Figma file.
Get SCIM service provider configGet Figma's SCIM service provider configuration.
Get styleRetrieves detailed metadata for a specific style in Figma using its unique style key.
Get team componentsRetrieves components published in a specific Figma team's library; the team must have published components, otherwise an empty list is returned.
Get team component setsRetrieves a paginated list of published component sets (collections of reusable UI elements) from a specified Figma team's library.
Get team stylesRetrieves a paginated list of published styles (fill colors, text styles, effects, grids) from a specified Figma team's library.
Get webhooksRetrieves all webhooks registered for a specified Figma context (team, project, or file).
Get versions of a fileRetrieves the version history for a Figma file or branch, as specified by its `file_key`.
Get webhook requestsRetrieves a history of webhook requests for a specific Figma webhook subscription; data is available for requests sent within the last seven days.
Render images of file nodesRender Figma nodes as images (PNG, JPG, SVG, PDF).
Update a webhookUpdates an existing Figma webhook, identified by `webhook_id`, allowing modification of its event type, endpoint, passcode, status, or description.
Update dev resourcesUpdates the name and/or URL of one or more existing Figma Dev Resources, each identified by its unique `id`.

Conclusion

You have successfully connected Figma to Kimi Code using Composio Connect. Your agent can now manage Figma from the terminal with natural language, without exposing credentials in prompts or local scripts.

Since the same Composio endpoint exposes 1,000+ apps, you can add Slack, Calendar, Linear, and more to the same server and chain them into cross-app workflows.

How to build Figma MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Figma MCP with ChatGPT

Antigravity logo

Antigravity

Use Figma MCP with Antigravity

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Figma MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Figma MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Figma MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Figma MCP with Claude Cowork

Codex logo

Codex

Use Figma MCP with Codex

Cursor logo

Cursor

Use Figma MCP with Cursor

VS Code logo

VS Code

Use Figma MCP with VS Code

OpenCode logo

OpenCode

Use Figma MCP with OpenCode

OpenClaw logo

OpenClaw

Use Figma MCP with OpenClaw

Hermes logo

Hermes

Use Figma MCP with Hermes

CLI logo

CLI

Use Figma MCP with CLI

Google ADK logo

Google ADK

Use Figma MCP with Google ADK

LangChain logo

LangChain

Use Figma MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Figma MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Figma MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Figma MCP with LlamaIndex

CrewAI logo

CrewAI

Use Figma MCP with CrewAI

FAQ

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 Kimi Code?

Yes, you can. Kimi Code 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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗