Figma MCP Server

Created By
karthiks3000a year ago
Claude MCP Server to work with figma
Overview

What is Figma MCP Server?

Figma MCP Server is a Model Context Protocol (MCP) server designed for interacting with Figma designs, allowing Claude AI to extract and manipulate design information from Figma files.

How to use Figma MCP Server?

To use the Figma MCP Server, clone the repository, install the dependencies, and start the server. Ensure you have a Figma account and the MCP plugin installed in the Figma desktop app for write operations.

Key features of Figma MCP Server?

  • Readonly Mode: Extract design information from Figma files using a URL link.
  • Write Mode: Create or update designs through the Figma plugin.
  • Comprehensive API: Access a wide range of Figma features through a unified API.
  • Unit and Integration Testing: Includes tests to verify server functionality and design flow.

Use cases of Figma MCP Server?

  1. Extracting design details for analysis or documentation.
  2. Automating design updates in Figma based on external inputs.
  3. Facilitating collaboration between AI and design teams.

FAQ from Figma MCP Server?

  • What are the prerequisites for using the server?

You need Node.js 18 or higher, a Figma account, and the Figma MCP plugin installed.

  • Can I use the server without the Figma plugin?

No, the write mode requires the Figma MCP plugin to function.

  • Is there documentation available?

Yes, detailed usage instructions can be found in the documentation provided in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
karthiks3000
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago