# How to connect Figma to Muse

```json
{
  "title": "How to connect Figma to Muse",
  "toolkit": "Figma",
  "toolkit_slug": "figma",
  "framework": "Muse",
  "framework_slug": "muse",
  "url": "https://composio.dev/toolkits/figma/framework/muse",
  "markdown_url": "https://composio.dev/toolkits/figma/framework/muse.md",
  "updated_at": "2026-10-04T16:38:32.620Z"
}
```

## Introduction

Muse is Meta's AI assistant. It can connect to outside tools through custom connectors, which use the Model Context Protocol (MCP).
This guide explains how to connect Figma to Muse using Composio Connect, which handles OAuth, token refresh, and reliability so you do not have to. You add Composio as a custom connector once, then ask Muse to work with Figma in plain language.

## Also integrate Figma with

- [Claude Code](https://composio.dev/toolkits/figma/framework/claude-code)
- [Cursor](https://composio.dev/toolkits/figma/framework/cursor)
- [ChatGPT](https://composio.dev/toolkits/figma/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/figma/framework/claude-cowork)
- [Antigravity](https://composio.dev/toolkits/figma/framework/antigravity)
- [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)
- [Grok Bot](https://composio.dev/toolkits/figma/framework/grok-bot)
- [Codex](https://composio.dev/toolkits/figma/framework/codex)
- [Kimi Code](https://composio.dev/toolkits/figma/framework/kimi)
- [Grok Build](https://composio.dev/toolkits/figma/framework/grok-build)
- [VS Code](https://composio.dev/toolkits/figma/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/figma/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/figma/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/figma/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/figma/framework/atomic-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)
- [Pydantic AI](https://composio.dev/toolkits/figma/framework/pydantic-ai)
- [AutoGen](https://composio.dev/toolkits/figma/framework/autogen)

## TL;DR

- Cross-app workflows across 1,500+ apps from a single plugin layer.
- On-demand tool loading so Muse only loads the tools needed for the current task.
- Programmatic tool calling through a remote workbench for complex, multi-step workflows.
- Multi-account support so users can connect and switch between multiple accounts for the same app.
- Shared account access so teams or agents can work through common business accounts and service connections.
- Managed authentication with OAuth handling, credential storage, and token refresh managed by Composio.
- Safer credential handling so app credentials stay outside the model context and tool responses.
- User-level account isolation so actions run against the correct connected account instead of mixing user access.

## Connect Figma to Muse

### Connecting Figma to Muse
You add Composio to Muse once as a custom connector, then connect Figma from the chat.

## 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 projects, files, components, variables, and prototypes, so your agent can explore designs, inspect file details, extract design tokens, review interactions, and download images on your behalf.
- Project and file discovery: Have your agent list visible team projects, find files within a project, and retrieve file names, creators, modification details, thumbnails, and access information.
- Focused design inspection: Direct your agent to examine a complete design file or selected layers, detect background layers, and return only the design details needed for the task.
- Design token extraction: Let the agent collect styles, variables, and values from your designs, then convert those tokens into a Tailwind CSS configuration.
- Component and library review: Instruct your agent to retrieve published components, component sets, and detailed metadata for a specific component in a Figma library.
- Prototype and asset handoff: Have your agent review prototype interactions and animations, then download images from selected design layers for implementation.

## 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 to receive POST notifications when specific events occur. Webhooks can monitor events at three scopes: - Team level: monitors all files in a team (requires team admin permissions) - Project level: monitors all files in a project (requires edit access) - File level: monitors a specific file (requires edit access) Upon creation, Figma sends an initial PING event to verify your endpoint (unless status is PAUSED). IMPORTANT: team_id, project_id, and file_key cannot be discovered programmatically. Extract them from Figma URLs or use FIGMA_DISCOVER_FIGMA_RESOURCES to parse URLs. |
| `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. TWO-STEP WORKFLOW: 1. First, call FIGMA_EXTRACT_DESIGN_TOKENS with a Figma file_key to extract design tokens 2. Then, pass the returned DesignTokens object to this action's 'tokens' parameter This action 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 Layers | Detect background layers for selected nodes in a Figma file. This action analyzes the Figma document structure and identifies potential background elements for the given target nodes. It uses: - Geometric analysis (bounding box overlap/containment) - Z-index ordering (nodes earlier in the layer stack are behind later ones) - Visual properties (fills, node types) - Naming conventions (nodes named 'background', 'bg', etc.) Returns background candidates with confidence scores (0-1) and explanations. |
| `FIGMA_DISCOVER_FIGMA_RESOURCES` | Discover Figma Resources | Smart Figma resource discovery - extract IDs from any Figma URL. Supports all URL formats: /file/, /design/, /board/, /proto/, /slides/ Example: figma.com/board/ABC123/Name → file_key=ABC123 Discovery workflow: team_id → projects → files → nodes Use extracted IDs with GetFileJson, DetectBackground, etc. |
| `FIGMA_DOWNLOAD_FIGMA_IMAGES` | Download Figma Images | Download images from Figma file nodes. Renders specified nodes as images and downloads them. Supports PNG, SVG, JPG, and PDF formats. REQUIRED PARAMETERS: - file_key (string): The Figma file key from the URL - images (array): List of objects, each containing: - node_id (string, required): The node ID to export (e.g., "1:2") - file_name (string, required): Output filename with extension (e.g., "logo.png") - format (string, optional): One of 'png', 'svg', 'jpg', 'pdf'. Defaults to 'png' Example usage: { "file_key": "abc123XYZ", "images": [ {"node_id": "1:2", "file_name": "logo.png", "format": "png"} ] } To find node IDs, use FIGMA_GET_FILE_JSON or look in Figma URLs after 'node-id='. NOTE: Returned image URLs expire shortly after generation — download them immediately. |
| `FIGMA_EXTRACT_DESIGN_TOKENS` | Extract design tokens | Extract design tokens from Figma files by combining styles, variables, and node-extracted values. Only values defined as Figma styles or variables are captured — any design values not encoded as styles/variables are silently omitted. Requires `file_variables:read` scope and a Figma plan that supports variables for full output; if variables return empty, supplement with FIGMA_GET_LOCAL_VARIABLES. |
| `FIGMA_EXTRACT_PROTOTYPE_INTERACTIONS` | Extract Prototype Interactions | Extract prototype interactions and animations from Figma files. Required parameter: - file_key: The Figma file key extracted from a URL like 'https://www.figma.com/file/ABC123xyz/MyFile' (the 'ABC123xyz' part) 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_COMPONENT2` | Get component | Fetches metadata for a specific component using its unique identifier. Use when you need to retrieve published component details from a team library. |
| `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 Design file data with automatic simplification. IMPORTANT: Only supports Design files (figma.com/design/{file_key}). FigJam board files (figma.com/board/{file_key}) and Slides files (figma.com/slides/{file_key}) are NOT supported and will return a 400 error: "File type not supported by this endpoint". 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_FILE_METADATA` | Get file metadata | Get Figma file metadata including name, creator, last modification details, thumbnail, and access information. Use when you need quick file overview without the full document tree. |
| `FIGMA_GET_FILE_NODES` | Get file nodes | Fetch JSON for specific node IDs from a Figma file to avoid full-file payload limits. Use when you already know target node IDs (from shallow file fetch or component listings) or when full-file JSON has hit payload limits. Prefer depth=1 for fast discovery. |
| `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 published Figma library. Returns data about how styles (colors, text styles, effects, grids) from the library are being used across your organization. Requires Enterprise plan and library_analytics:read scope. Group results by 'style' to see per-style metrics or by 'file' to see which files use the library's styles. |
| `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. Note: Requires Enterprise plan and library_analytics:read scope. |
| `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_SCIM_SERVICE_PROVIDER_CONFIG` | Get SCIM service provider config | Get Figma's SCIM service provider configuration. Returns configuration details including which SCIM operations are supported (patch, bulk, filter, etc.), authentication schemes, and service capabilities. |
| `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 (fill colors, text styles, effects, grids) from a specified Figma team's library. Note: The team must have published styles in its library for this endpoint to return data. Teams without published styles will return an empty list. |
| `FIGMA_GET_TEAM_WEBHOOKS` | Get webhooks | Retrieves all webhooks registered for a specified Figma context (team, project, or file). Uses the Figma Webhooks V2 API endpoint (GET /v2/webhooks) with context and context_id query parameters. This is the recommended approach as the legacy path-based endpoint (/v2/teams/{team_id}/webhooks) is deprecated. Note: team_id, project_id, and file_key cannot be discovered programmatically via the API. Extract them from Figma URLs or use FIGMA_DISCOVER_FIGMA_RESOURCES to parse URLs. |
| `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 | Render Figma nodes as images (PNG, JPG, SVG, PDF). Returns a map of node IDs to temporary image URLs (valid for 30 days). Images are capped at 32 megapixels; larger requests are automatically scaled down. REQUIRED PARAMETERS: - file_key: Figma file key from URL (e.g., 'abc123XYZ' from figma.com/design/abc123XYZ/...) - ids: Comma-separated node IDs to render (e.g., '1:2' or '1:2,1:3,1:4') NODE IDs: Found in Figma URLs after 'node-id=' or from FIGMA_GET_FILE_JSON response. FORMATS: - png/jpg: Raster images with optional scale (0.01-4.0) - svg: Vector graphics with text outline options - pdf: Document format COMMON ISSUES: - null value in images map = node failed to render (invalid ID, invisible, 0% opacity) - 404 error = file_key not found or no access - 429 error = rate limit exceeded, wait and retry |
| `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.

## Troubleshooting

### 1. Why doesn't Muse show a button to add my API key?

Muse shows the button only when you ask it to open the secure credentials store.
- Start a new chat.
- Send the message from step 1 exactly as written.
- If Muse asks for the key in the chat, do not paste it. Ask Muse to open the secure credentials store.

### 2. Why does the Composio connection fail after I add my API key?

The key or the connector settings are not correct.
- Copy the full key from the Composio dashboard. It starts with ck_.
- Make sure the URL is https://connect.composio.dev/mcp and the header is x-consumer-api-key.
- Remove the Composio connector in Muse settings, then do steps 1 to 3 again.

### 3. Why doesn't Muse use the Composio tools for Figma?

Muse may not pick the Composio connector for the request.
- Ask Muse to list its Composio tools.
- Name Composio and Figma in your request, for example: Use Composio to connect to Figma.
- If it still does not work, start a new chat and try again.

### 4. Why does Muse ask me to connect Figma again?

Your Figma connection expired or was removed.
- Open the link Muse gives you and sign in to Figma again.
- Check that the Figma connection shows as ACTIVE in the Composio dashboard.

### 5. What do I do if I pasted my API key into the chat?

Treat the key as exposed.
- Create a new API key in the Composio dashboard and delete the old one.
- Add the new key in Muse's secure credentials store, not in the chat.

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

Once connected, Muse can access the Figma MCP server through Composio to run the actions you authorize, using plain language in the chat.

## 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 Muse 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 connection, Muse can coordinate multiple tools safely and reliably in one conversation.

## How to build Figma MCP Agent with another framework

- [Claude Code](https://composio.dev/toolkits/figma/framework/claude-code)
- [Cursor](https://composio.dev/toolkits/figma/framework/cursor)
- [ChatGPT](https://composio.dev/toolkits/figma/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/figma/framework/claude-cowork)
- [Antigravity](https://composio.dev/toolkits/figma/framework/antigravity)
- [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)
- [Grok Bot](https://composio.dev/toolkits/figma/framework/grok-bot)
- [Codex](https://composio.dev/toolkits/figma/framework/codex)
- [Kimi Code](https://composio.dev/toolkits/figma/framework/kimi)
- [Grok Build](https://composio.dev/toolkits/figma/framework/grok-build)
- [VS Code](https://composio.dev/toolkits/figma/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/figma/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/figma/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/figma/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/figma/framework/atomic-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)
- [Pydantic AI](https://composio.dev/toolkits/figma/framework/pydantic-ai)
- [AutoGen](https://composio.dev/toolkits/figma/framework/autogen)

## 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.
- [Are.na](https://composio.dev/toolkits/arena) - Are.na is a creative research platform for collecting images, links, notes, and ideas in channels. Use it to organize inspiration, build knowledge maps, and connect research across projects.
- [Bannerbite](https://composio.dev/toolkits/bannerbite) - Bannerbite is a creative automation platform for generating images and videos from reusable projects and templates. It helps teams produce on-brand visual assets faster without rebuilding designs from scratch.
- [BeatAPI](https://composio.dev/toolkits/beatapi) - BeatAPI is an asynchronous API platform for AI image, video, and music workflows. It enables scalable generation, video analysis, uploads, and ecommerce video pipelines.
- [Builder.io](https://composio.dev/toolkits/builder_io) - Builder.io is a visual development platform for managing content, models, assets, and Space configuration. Use it to ship editable digital experiences faster without waiting on every code change.
- [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.
- [Contentdrips](https://composio.dev/toolkits/contentdrips) - Contentdrips is an asynchronous rendering API for branded graphics and carousels. It turns reusable templates into on-brand social visuals at scale.
- [Creatomate](https://composio.dev/toolkits/creatomate) - Creatomate is an API for generating automated videos, images, GIFs, and reusable media templates. Use it to turn structured data into polished visual content at scale.
- [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.
- [Dribbble](https://composio.dev/toolkits/dribbble) - Dribbble is a design community and publishing platform for managing shots, projects, and attachments. Use it to showcase work, collect feedback, and organize creative designs.
- [Dynamic Mockups](https://composio.dev/toolkits/dynamic_mockups) - Dynamic Mockups is an API platform for generating product mockups, rendering templates, and managing visual asset catalogs. Use it to automate high-quality product visuals, AI images, and motion assets at scale.
- [Dynapictures](https://composio.dev/toolkits/dynapictures) - Dynapictures is a cloud-based platform for generating personalized images at scale. Instantly create hundreds of custom visuals using your data sources, like Google Sheets.
- [Excalidraw MCP](https://composio.dev/toolkits/excalidraw_mcp) - Excalidraw MCP is a no-auth MCP server for creating hand-drawn style diagrams in Excalidraw. Use it to generate visual sketches with viewport camera control and fullscreen editing.
- [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.
- [Gamma](https://composio.dev/toolkits/gamma) - Gamma is an AI-powered platform for making beautiful, interactive presentations and documents. It lets anyone create and share engaging decks with minimal effort.

## Frequently Asked Questions

### Does Muse support MCP?

Yes. Muse supports custom connectors that use the Model Context Protocol (MCP). Composio connects as one custom connector over remote streamable HTTP at https://connect.composio.dev/mcp, and gives Muse access to Figma and 1,500+ other apps.

### Where do I get the API key for the Composio connector?

Copy it from the Composio dashboard. It starts with ck_. Enter it only in Muse's secure credentials store, never in the chat.

### Can I connect more than one Figma account to Muse?

Yes. Composio supports multiple connected accounts for the same app. Give each Figma connection a name, such as work or personal, and tell Muse which one to use.

### How safe is my Figma data with Composio?

Tokens, keys, and configuration are encrypted at rest and in transit. Your Composio API key stays in Muse's secure credentials store, not in the chat or the model context. Composio is SOC 2 Type 2 compliant.

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