Figma MCP Server

Created By
moonraya year ago
An mcp server that efificiently generates a node tree and related metadata for a figma node.
Overview

what is Figma MCP Server?

Figma MCP Server is an MCP (Model Context Protocol) server designed to analyze Figma file structures and efficiently generate a node tree along with related metadata.

how to use Figma MCP Server?

To use the Figma MCP Server, install it via npm or clone the repository from GitHub. Configure your Figma API key in the environment file, then start the server to analyze Figma files through REST API or MCP protocol.

key features of Figma MCP Server?

  • Analyze Figma files to extract node hierarchies
  • Supports both REST API and MCP protocol
  • Configurable node tree depth
  • Health check and OpenAPI specification endpoints

use cases of Figma MCP Server?

  1. Extracting design components from Figma files for documentation.
  2. Integrating Figma design data into other applications.
  3. Analyzing design structures for automated testing or validation.

FAQ from Figma MCP Server?

  • What is required to run Figma MCP Server?

You need Node.js 16+, npm or yarn, and a Figma API key.

  • Can I run Figma MCP Server in a Docker container?

Yes! A Dockerfile is provided for containerized deployment.

  • How do I analyze a Figma file?

Use the POST /analyze endpoint with the Figma file URL and desired depth.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
moonray
Star
2
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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.

13 hours ago