Figma Bridge MCP Server
Figma design data streamed to your AI assistant without hitting API rate limits.
Data last scanned today · Reviewed today
Overview
Figma Bridge MCP Server provides a direct path between your Figma design files and AI assistants. By using a companion Figma plugin alongside the MCP server, it circumvents the restrictive 6-request-per-month limit imposed on free Figma API users, allowing for continuous design data streaming. It supports multi-file workflows by maintaining simultaneous connections to multiple Figma files, which your AI agent can query individually by fileKey. The server includes tools to fetch document trees, node details, styles, and file metadata, as well as optional write tools for direct agent-driven edits.
Our verdict
This server carries a high-risk level with a security score of 45/100, primarily because the authentication and read-only mode implementations have not yet been editorially reviewed. Given that the project includes write tools for agent-driven edits, users should exercise caution when granting it access to sensitive design files. It is best suited for developers looking to experiment with Figma-to-AI workflows in non-sensitive environments until further security audits are conducted.
- Bypasses free-tier Figma API rate limits for developers
- Supports concurrent connections across multiple active Figma files
- Zero direct dependencies reduces supply chain attack surface
- Active repository with recent commits and 11 contributors
- Authentication methods remain unreviewed for security vulnerabilities
- Lack of editorial review on the server's read-only functionality
- Community-maintained project lacking official vendor oversight
Tools
| Tool | Description | Risk |
|---|---|---|
| list_files | List all connected Figma files (supports multi-file workflows) | low |
| get_document | Get the current Figma page document tree | low |
| get_selection | Get the currently selected nodes in Figma | low |
| get_node | Get a specific Figma node by ID (colon format, e.g. 4029:12345) | low |
| get_styles | Get all local paint, text, effect, and grid styles | low |
| get_metadata | Get file name, pages, and current page info | low |
| get_design_context | Get a depth-limited tree optimized for understanding design context | low |
| get_variable_defs | Get all variable collections, modes, and values (design tokens) | low |
| get_screenshot | Export nodes as PNG/SVG/JPG/PDF (base64-encoded) | low |
| save_screenshots | Export and save screenshots directly to the local filesystem | medium |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›How does this server avoid Figma API rate limits?
This server uses a companion Figma plugin to stream live document data to your AI tools, bypassing the need for frequent calls to the standard Figma API.
›Can I use this with multiple Figma files at once?
Yes, you can open the plugin in multiple Figma files simultaneously; the bridge maintains active connections to all of them, allowing your AI agent to query specific files using their fileKey.
›Do I need to install any external binaries?
No, the MCP server runs via npx directly, so there are no binaries to download or install for the server component.
›Are there limitations to using the editing tools?
Yes, edit tools only function when the plugin is opened in the Figma design editor, as they do not work in read-only Dev Mode.
›How do I add the Figma plugin to my environment?
Download the plugin from the project's release page, then import it into Figma by navigating to Plugins > Development > Import plugin from manifest and selecting the manifest.json file.
Badge
Maintain this server? Add the live badge to your README.