Figma MCP Server

Created By
thirdstrandstudioa year ago
Figma MCP Server with full API functionality
Overview

what is Figma MCP Server?

Figma MCP Server is a server designed to interact with the Figma API, providing a complete set of API methods through the Model Context Protocol.

how to use Figma MCP Server?

To use the Figma MCP Server, you need to set up your Figma API token and install the server via npm or Smithery. You can then call various API methods to interact with Figma files and components.

key features of Figma MCP Server?

  • Full API functionality for Figma
  • Methods for user, file, comment, team, project, component, style, and webhook management
  • Easy installation and setup with Node.js

use cases of Figma MCP Server?

  1. Retrieve Figma files and their components programmatically.
  2. Manage comments and reactions on Figma files.
  3. Create webhooks for real-time updates on file changes.

FAQ from Figma MCP Server?

  • What is required to run the Figma MCP Server?

You need Node.js (v16 or later) and a valid Figma API token.

  • Is the Figma MCP Server free to use?

Yes! The server is open-source and licensed under the MIT License.

  • Can I use this server for large Figma files?

Yes, but you may need to adjust the depth parameter for large files.

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

Recommend Servers

View All
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.

8 hours ago