Figma MCP Server

Created By
planetabhia year ago
A simple MCP server for Figma
Overview

what is Figma MCP Server?

Figma MCP Server is a simple server designed to facilitate communication with Figma's API, allowing users to integrate Figma functionalities into their applications.

how to use Figma MCP Server?

To use the Figma MCP Server, clone the repository, install the necessary dependencies, set your Figma API key in a .env file, and run the server using Node.js or Docker.

key features of Figma MCP Server?

  • Easy integration with Figma's API.
  • Support for running in various environments (Node.js, Docker).
  • Ability to list available tools and their parameters.

use cases of Figma MCP Server?

  1. Integrating Figma design data into applications.
  2. Automating design workflows with Figma.
  3. Enabling real-time collaboration on design projects.

FAQ from Figma MCP Server?

  • How do I set up the Figma MCP Server?

Clone the repository, install dependencies, set your API key, and run the server.

  • Can I run the server in Docker?

Yes! The server can be deployed using Docker for production environments.

  • What is the purpose of the .env file?

The .env file is used to store environment variables, including your Figma API key.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
planetabhi
Star
0
Language
JavaScript
License
View license

Recommend Servers

View All
Voyei

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.

16 hours ago