Figma MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Figma MCP Server?

Figma MCP Server is a TypeScript server that implements the Model Context Protocol (MCP) for the Figma API, enabling standardized context provision for large language models (LLMs).

how to use Figma MCP Server?

To use the Figma MCP Server, install the necessary packages, set up your Figma access token, and start the server. You can then interact with the server using either stdio or SSE transport methods.

key features of Figma MCP Server?

  • MCP-compliant access to Figma resources
  • Type-safe implementation using TypeScript
  • Custom URI scheme for Figma resources
  • Robust error handling and request validation
  • Support for batch operations

use cases of Figma MCP Server?

  1. Integrating LLM applications with Figma files and components.
  2. Automating resource management in Figma projects.
  3. Enabling real-time updates and notifications for Figma resources.

FAQ from Figma MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol that standardizes how context is provided to LLMs, allowing for better integration with various applications.

  • Is the Figma MCP Server free to use?

Yes! The Figma MCP Server is open-source and free to use.

  • How can I contribute to the project?

You can contribute by forking the repository, creating a feature branch, and submitting a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
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