Figma Context MCP

Created By
GLipsa year ago
Overview

What is Figma Context MCP?

Figma Context MCP is a server that allows AI-powered coding tools, like Cursor, to access Figma design data, enabling accurate implementation of designs in various frameworks.

How to use Figma Context MCP?

To use the Figma Context MCP, set up the server by configuring your IDE with the necessary Figma API access token and command. Then, paste a link to a Figma file in your IDE's chat and ask the AI to implement the design.

Key features of Figma Context MCP?

  • Provides access to Figma design data for AI coding tools.
  • Simplifies and translates Figma API responses for better accuracy.
  • Supports multiple languages for documentation.

Use cases of Figma Context MCP?

  1. Implementing UI designs directly from Figma into code.
  2. Enhancing AI coding tools' performance with Figma data.
  3. Streamlining the design-to-code workflow for developers.

FAQ from Figma Context MCP?

  • What is the Model Context Protocol?

It is a protocol that allows coding agents to interact with design data effectively.

  • Do I need a Figma access token?

Yes, you need to create a Figma API access token to use this server.

  • Is there a demo available?

Yes, you can watch a demo of building a UI in Cursor with Figma design data.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
GLips
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