Framelink Figma MCP Server

Created By
GLipsa year ago
MCP server to provide Figma layout information to AI coding agents like Cursor
Overview

What is Figma MCP Server?

Figma MCP Server is a server designed to provide Figma layout information to AI coding agents like Cursor, enhancing their ability to implement designs accurately.

How to use Figma MCP Server?

To use the Figma MCP Server, clone the repository, install dependencies, set up your Figma API access token, and connect it to Cursor. Once connected, you can paste links to Figma files in Cursor's composer to interact with the design data.

Key features of Figma MCP Server?

  • Provides Figma design data to AI coding agents.
  • Simplifies and translates Figma API responses for better accuracy.
  • Supports fetching specific file and node information from Figma.

Use cases of Figma MCP Server?

  1. Implementing UI designs directly from Figma files.
  2. Enhancing AI coding agents' accuracy in design implementation.
  3. Streamlining the design-to-code workflow for developers.

FAQ from Figma MCP Server?

  • Can I use Figma MCP Server with any AI coding agent?

The server is specifically designed for use with Cursor.

  • Is there a cost associated with using Figma MCP Server?

No, it is free to use.

  • What kind of access do I need for the Figma API?

Only read access is required for the Figma API.

Server Config

{
  "mcpServers": {
    "figma-developer-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "figma-developer-mcp",
        "--stdio"
      ],
      "env": {
        "FIGMA_API_KEY": "<your-figma-api-key>"
      }
    }
  }
}
Project Info
Featured
Created At
a year ago
Updated At
a year ago
Author Name
GLips
Star
7674
Language
TypeScript
License
MIT license

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago