Figma MCP Server

Created By
thirdstrandstudioa year ago
Figma MCP Server with full API functionality
Overview

what is Figma MCP Server?

Figma MCP Server is a server designed to interact with the Figma API, providing a complete set of API methods through the Model Context Protocol.

how to use Figma MCP Server?

To use the Figma MCP Server, you need to set up your Figma API token and install the server via npm or Smithery. You can then call various API methods to interact with Figma files and components.

key features of Figma MCP Server?

  • Full API functionality for Figma
  • Methods for user, file, comment, team, project, component, style, and webhook management
  • Easy installation and setup with Node.js

use cases of Figma MCP Server?

  1. Retrieve Figma files and their components programmatically.
  2. Manage comments and reactions on Figma files.
  3. Create webhooks for real-time updates on file changes.

FAQ from Figma MCP Server?

  • What is required to run the Figma MCP Server?

You need Node.js (v16 or later) and a valid Figma API token.

  • Is the Figma MCP Server free to use?

Yes! The server is open-source and licensed under the MIT License.

  • Can I use this server for large Figma files?

Yes, but you may need to adjust the depth parameter for large files.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
thirdstrandstudio
Star
16
Language
TypeScript
License
MIT 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)

a day ago